Bug 1283203 - After upgrading from juno to kilo neutron-openvswitch-agent service fails to start
Summary: After upgrading from juno to kilo neutron-openvswitch-agent service fails to ...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 7.0 (Kilo)
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: 8.0 (Liberty)
Assignee: lpeer
QA Contact: Ofer Blaut
URL:
Whiteboard:
: 1283200 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-18 12:49 UTC by Anand Nande
Modified: 2023-09-14 03:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-01 00:44:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 2 Assaf Muller 2015-12-16 23:50:02 UTC
*** Bug 1283200 has been marked as a duplicate of this bug. ***

Comment 4 Ihar Hrachyshka 2015-12-17 10:40:16 UTC
One note on upgrade procedure: I don't think we support upgrade from OSP5 directly to OSP7, we don't support skipping releases. So it would be great if we check that the same issue occurs if we do properly staged upgrade through OSP6.

Comment 5 Ihar Hrachyshka 2015-12-17 10:54:12 UTC
In the log snippet in comment#1, I see that daemon mode for rootwrap is triggered. This is expected because we enabled the mode by default in Kilo: https://review.gerrithub.io/#/c/234352/

The UnboundLocalError error that we see in the traceback just indicates that rootwrap daemon process failed to start (in latest versions of oslo.rootwrap it should not fail with this specific type of the exception since I fixed the traceback: https://review.openstack.org/#/c/191895/ Nevertheless, the backport of the patch would not fix the culprit of the failure for you.)

Sadly, rootwrap daemon mode does not provide good logging capabilities if something goes wrong because it interacts through stdout/stderr only, so from here we can only make assumptions.

Note that rootwrap daemon mode requires a new entry in sudoers file shipped with Neutron package: https://review.gerrithub.io/#/c/235911/ I don't see you mention anywhere that you updated your configuration files to merge any changes from .rpmnew files created in /etc/. Please make sure the line is present in your /etc/sudoers.d/neutron file. If it's not there, it will explain why daemon fails to start: because sudo does allow it in the first place. In that case, you should probably see access denied logs in syslog for failed sudo attempts.

Comment 6 Assaf Muller 2016-01-12 15:02:03 UTC
Ping.

Comment 7 Assaf Muller 2016-06-01 00:44:12 UTC
Please re-open if needed. Ihar sent a needinfo for more information in 2015.

Comment 8 Red Hat Bugzilla 2023-09-14 03:13:17 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.