hudson-openstack not working for python-novaclient

[Christian Berendt]

Not sure if this is a bug or it's intended.

I opened a bug report affecting several client projects at https://bugs.launchpad.net/python-novaclient/+bug/1326471 and opened 5 review requests. hudson-openstack assigned 4 of 5 review requests to the corresponding projects in the referred bug report. The review request of python-novaclient is not yet assigned. The review request for python-novaclient is available at https://review.openstack.org/#/c/97870/.

[Christian Berendt (berendt)]

After several hours the mentioned review request of python-novaclient is still not connected with the mentioned bug report.

[Clark Boylan (cboylan)]

Pretty sure that the nova-bugs team is missing the Openstack infra (hudson-openstack) account and if that account is added to the team this will work as expected. I have added the python-novaclient to this bug so that someone on the nova side can add the account to the bug driver team.

[Jeremy Stanley (fungi)]

Agreed, python-novaclient has configured https://launchpad.net/~nova-bugs/+members as its bug supervisor, which does not appear to include the https://launchpad.net/~hudson-openstack user. In fact, this is the same bug team that openstack/nova uses so they should in theory be experiencing similar issues.

Removing openstack-ci as this is working as designed.

[melanie witt (melwitt)]

FWIW, I have seen issues where if the review is pushed to gerrit "too soon" after opening the launchpad bug, it will not be able to link it to the bug with the patch proposed message and In Progress status. If you look at https://bugs.launchpad.net/python-novaclient/+bug/1326471/comments/5 the bug was able to be updated by hudson-openstack when the patch was merged.

[Jeremy Stanley (fungi)]

It boils down to whether the Gerrit hook script needs to reassign the bug. If the bug is already assigned to the change owner, the account the script is using has sufficient privileges for the tasks it wants to perform (comment in the bug and change its status). However, if the event happens in a situation where the script wants to assign/reassign the bug, it needs membership in the bug supervisor group to accomplish that. If it *lacks* that then its bug update API call is rejected with an insufficient permission response from Launchpad and nothing happens.

[melanie witt (melwitt)]

@fungi I finally understand now! Thank you for the detailed explanation. I'll post to the ML to ask how hudson-openstack can be added to the nova-bugs team.

[melanie witt (melwitt)]

This should be fixed, hudson-openstack was added to the nova-bugs team [1] after ML request [2].

[1] https://launchpad.net/~nova-bugs
[2] http://lists.openstack.org/pipermail/openstack-dev/2014-July/040250.html