Hi all, We upgraded our LAVA master to 2019.11 (2019.11 + stretch) version , but when queried devices owned by current user , it listed all devices hooked to this master, can anybody help check it? Regards, Su Chuan
Hello,
There was a major refactoring of LAVA authorization system in 2019.09 release as you can see here on the announcement mailing list https://lists.lavasoftware.org/pipermail/lava-announce/2019-September/000090... Now there were some known issues with data migration between 2019.08 and 2019.09 releases which we experienced in our production system but none match the issue you described. Can you share a bit more information about your problem (admin setup etc)?
You can also find more information regarding object visibility and authorization here: https://docs.lavasoftware.org/lava/authorization.html
HTH,
On 11/18/19 3:20 AM, 宿川 wrote:
Hi all, We upgraded our LAVA master to 2019.11 (2019.11 + stretch) version , but when queried devices owned by current user , it listed all devices hooked Best regardsto this master, can anybody help check it? Regards, Su Chuan
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Hi , Stevan
When I query devices owned by myself , it lists all device as below：
but this device fsl-imx6ull-evk-linux-sh01 highlighted in the picture above is none of my business , for detail as below ：
This is different from previous version , I'm not sure it's just a new strategy to determine device owner or new bug. BTW
my master is 2019.11+stretch , as below:
I'm not sure if you can view pictures inline , if not , I attach all above four pictures to this reply , thanks for your help! Regards, Su Chuan
At 2019-11-18 16:42:10, "Stevan Radaković" stevan.radakovic@linaro.org wrote: Hello,
There was a major refactoring of LAVA authorization system in 2019.09 release as you can see here on the announcement mailing list https://lists.lavasoftware.org/pipermail/lava-announce/2019-September/000090... Now there were some known issues with data migration between 2019.08 and 2019.09 releases which we experienced in our production system but none match the issue you described. Can you share a bit more information about your problem (admin setup etc)?
You can also find more information regarding object visibility and authorization here: https://docs.lavasoftware.org/lava/authorization.html
HTH,
On 11/18/19 3:20 AM, 宿川 wrote:
Hi all, We upgraded our LAVA master to 2019.11 (2019.11 + stretch) version , but when queried devices owned by current user , it listed all devices hooked Best regardsto this master, can anybody help check it? Regards, Su Chuan
_______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.orghttps://lists.lavasoftware.org/mailman/listinfo/lava-users
Since the authorization update in 2019.09, the original Device' "owner" field is removed. So in the 'My devices' page we display all the devices that the user has 'change_device' permission over. The 'physical owner' field is just for the admin reference it is not really used anywhere. I'm sorry if this is a bit confusing, I'll make sure it's documented properly in the future.
Cheers,
On 11/19/19 12:24 PM, 宿川 wrote:
Hi , Stevan
When I query devices owned by myself , it lists all device as below：
but this device fsl-imx6ull-evk-linux-sh01 highlighted in the picture above is none of my business , for detail as below ：
This is different from previous version , I'm not sure it's just a new strategy to determine device owner or new bug. BTW
my master is 2019.11+stretch , as below: I'm not sure if you can view pictures inline , if not , I attach all above four pictures to this reply , thanks for your help! Regards, Su Chuan
At 2019-11-18 16:42:10, "Stevan Radaković" stevan.radakovic@linaro.org wrote:
Hello, There was a major refactoring of LAVA authorization system in 2019.09 release as you can see here on the announcement mailing list https://lists.lavasoftware.org/pipermail/lava-announce/2019-September/000090.html Now there were some known issues with data migration between 2019.08 and 2019.09 releases which we experienced in our production system but none match the issue you described. Can you share a bit more information about your problem (admin setup etc)? You can also find more information regarding object visibility and authorization here: https://docs.lavasoftware.org/lava/authorization.html HTH, On 11/18/19 3:20 AM, 宿川 wrote:Hi all, We upgraded our LAVA master to 2019.11 (2019.11 + stretch) version , but when queried devices owned by current user , it listed all devices hooked Best regardsto this master, can anybody help check it? Regards, Su Chuan _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users-- Stevan Radaković | LAVA Engineer Linaro.org <www.linaro.org> │ Open source software for ARM SoCs
lava-users@lists.lavasoftware.org
-
Stevan Radaković -
宿川