{"push_id":1342774390,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"f4ff45c3a064ee743ca4741e1b91a9bac379c897","before":"ea1791edf07d71d7b0963060e3e4dd3fbff674c1","commits":[{"sha":"f4ff45c3a064ee743ca4741e1b91a9bac379c897","author":{"name":"Jenkins","email":"61eb39d4445155efb6068840385577c11776cd20@review.openstack.org"},"message":"Updated openstack/openstack\nProject: openstack/nova  0ceb0a712a94b12ca1e09571af9d4422578579d5\n\nDon't attempt to escalate nova-manage privileges\n\nRemove code which allowed nova-manage to attempt to escalate\nprivileges so that configuration files can be read by users who\nnormally wouldn't have access, but do have sudo access.\n\nThe privilege escalation came into nova-manage with commit e9fd01e\nto solve bug 805695. That bug report didn't describe a faulty behavior\nbut a change request.\n\nNOTE: This is related to change I03063d2 from Kiall Mac Innes who did\nthis for the \"designate\" project. I'm reusing the change-id from his\nchange to make it clear that they are related to each other.\n\nNOTE: I removed the try-except block completely, as it doesn't make\nsense to continue when we cannot read the config file (due to a wrong\npath or permission errors). That's the same approach we used in the\nrecent \"nova/cmd/policy_check\" module.\nhttps://github.com/openstack/nova/blob/master/nova/cmd/policy_check.py#L158\n\nCo-Authored-By: Kiall Mac Innes <kiall@macinnes.ie>\nCloses-Bug: 1611171\nChange-Id: I03063d2af14015e6506f1b6e958f5ff219aa4a87","distinct":true,"url":"https://api.github.com/repos/openstack/openstack/commits/f4ff45c3a064ee743ca4741e1b91a9bac379c897"}]}
{"actor":{"display_login":"openstack-gerrit"}}