[focal-wallaby] Services not running that should be: neutron-openvswitch-agent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Neutron Gateway Charm |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack Neutron Open vSwitch Charm |
Invalid
|
Undecided
|
Unassigned | ||
neutron |
Fix Released
|
High
|
Unassigned | ||
neutron (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
When deploying focal-wallaby, the neutron-
systemd[1]: Starting OpenStack Neutron OVS cleanup...
sudo[190474]: pam_unix(
sudo[190474]: pam_unix(
sudo[190474]: pam_unix(
sudo[190474]: neutron : command not allowed ; TTY=unknown ; PWD=/var/
systemd[1]: neutron-
systemd[1]: neutron-
systemd[1]: Failed to start OpenStack Neutron OVS cleanup.
Indeed /etc/securetty got removed in focal [0][1]. Maybe Neutron just started doing something in Wallaby that requires this file?
This is visible in our OSCI test gate. [2][3]
[0] https:/
[1] https:/
[2] https:/
[3] https:/
description: | updated |
description: | updated |
Changed in neutron (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Critical |
Changed in neutron: | |
status: | In Progress → Triaged |
importance: | Undecided → High |
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential |
Problem:
$ sudo systemctl restart neutron-ovs-cleanup # fails
Workaround:
$ neutron-ovs-cleanup # succeeds and seems to unblock something, because now... openvswitch- agent # succeeds
$ sudo systemctl restart neutron-ovs-cleanup # succeeds
$ sudo systemctl restart neutron-