Ask Your Question
0

Error neutron-gateway in Openstack on LXD

asked 2019-04-22 19:11:52 -0600

Cosme gravatar image

Hi.
I am deploying Openstack Rocky following OpenStack on LXD (https://docs.openstack.org/charm-guide/latest/openstack-on-lxd.html (https://docs.openstack.org/charm-guid...)) on Ubuntu 18.04 updated. And when creating the neutron-gateway container it stays in hook failed: "config-changed" state.
With juju debug-log the following error appears:

unit-neutron-gateway-0: 23:46:24 INFO unit.neutron-gateway/0.juju-log Check command not found: check_systemd.py
unit-neutron-gateway-0: 23:46:25 INFO unit.neutron-gateway/0.juju-log Check command not found: check_systemd.py
unit-neutron-gateway-0: 23:46:25 INFO unit.neutron-gateway/0.juju-log Check command not found: check_systemd.py
unit-neutron-gateway-0: 23:46:25 INFO unit.neutron-gateway/0.juju-log Check command not found: check_systemd.py
unit-neutron-gateway-0: 23:46:25 INFO unit.neutron-gateway/0.juju-log Check command not found: check_systemd.py
unit-neutron-gateway-0: 23:46:25 INFO unit.neutron-gateway/0.juju-log Check command not found: check_systemd.py
unit-neutron-gateway-0: 23:46:25 INFO unit.neutron-gateway/0.juju-log Check command not found: check_systemd.py
unit-neutron-gateway-0: 23:46:25 INFO unit.neutron-gateway/0.juju-log Check command not found: check_status_file.py
unit-neutron-gateway-0: 23:46:25 INFO unit.neutron-gateway/0.juju-log Nagios user not set up, nrpe checks not updated
unit-neutron-gateway-0: 23:46:25 DEBUG unit.neutron-gateway/0.juju-log Updating sysctl_file: /etc/sysctl.d/50-quantum-gateway.conf values: {'net.ipv4.neigh.default.gc_thresh1': 128, 'net.ipv4.neigh.default.gc_thresh2': 28672, 'net.ipv4.neigh.default.gc_thresh3': 32768, 'net.ipv6.neigh.default.gc_thresh1': 128, 'net.ipv6.neigh.default.gc_thresh2': 28672, 'net.ipv6.neigh.default.gc_thresh3': 32768, 'net.nf_conntrack_max': 1000000, 'net.netfilter.nf_conntrack_buckets': 204800, 'net.netfilter.nf_conntrack_max': 1000000}
unit-neutron-gateway-0: 23:46:25 DEBUG unit.neutron-gateway/0.config-changed sysctl: cannot stat /proc/sys/net/ipv4/neigh/default/gc_thresh1: No such file or directory
unit-neutron-gateway-0: 23:46:25 DEBUG unit.neutron-gateway/0.config-changed sysctl: cannot stat /proc/sys/net/ipv4/neigh/default/gc_thresh2: No such file or directory
unit-neutron-gateway-0: 23:46:25 DEBUG unit.neutron-gateway/0.config-changed sysctl: cannot stat /proc/sys/net/ipv4/neigh/default/gc_thresh3: No such file or directory
unit-neutron-gateway-0: 23:46:25 DEBUG unit.neutron-gateway/0.config-changed sysctl: cannot stat /proc/sys/net/ipv6/neigh/default/gc_thresh1: No such file or directory
unit-neutron-gateway-0: 23:46:25 DEBUG unit.neutron-gateway/0.config-changed sysctl: cannot stat /proc/sys/net/ipv6/neigh/default/gc_thresh2: No such file or directory
unit-neutron-gateway-0: 23:46:25 DEBUG unit.neutron-gateway/0.config-changed sysctl: cannot stat /proc/sys/net/ipv6/neigh/default/gc_thresh3: No such file or directory
unit-neutron-gateway-0: 23:46:25 DEBUG unit.neutron-gateway/0.config-changed sysctl: cannot stat /proc/sys/net/nf_conntrack_max: No such file or directory
unit-neutron-gateway-0: 23:46:25 DEBUG unit.neutron-gateway/0.config-changed sysctl: setting key "net.netfilter.nf_conntrack_buckets": No such file or directory
unit-neutron-gateway-0: 23:46:25 DEBUG unit.neutron-gateway/0.config-changed net.netfilter.nf_conntrack_max = 1000000
unit-neutron-gateway-0: 23:46:25 DEBUG unit.neutron-gateway/0.config-changed Traceback (most recent call last):
unit-neutron-gateway-0: 23:46:25 DEBUG unit.neutron-gateway/0.config-changed   File "/var/lib/juju/agents/unit-neutron-gateway-0/charm/hooks/config-changed", line 362, in <module>
unit-neutron-gateway-0: 23:46:25 DEBUG unit.neutron-gateway/0.config-changed     hooks.execute(sys.argv)
unit-neutron-gateway-0: 23:46 ...
(more)
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
1

answered 2019-04-23 09:38:14 -0600

mjboniface1 gravatar image

updated 2019-04-24 07:32:56 -0600

We started experiencing the same issue last week for different combinations including xenial-ocata and bionic-rocky after rebuilding our stack. For some reason variables such as net.ipv4.neigh.default don't exist within LXC containers anymore created under the juju-profile or any other profile for that matter. Would welcome any insight into the issue as it's puzzling us too

Initial investigation shows that this is an issue resulting from a recent bug fix with the neutron gateway charm

https://bugs.launchpad.net/charm-nova-compute/+bug/1780348 (https://bugs.launchpad.net/charm-nova...)

You can see in the following commit that defaults were added recently that may work for bare metal deployments but don't for LXD containers as the neigh.default variables are not available within the guest container.

https://opendev.org/openstack/charm-neutron-gateway/commit/53b58388d37a3b2b2674989e09c216a (https://opendev.org/openstack/charm-n...)

Removing the default sysctl values and then resolving fixes this for now.

juju config neutron-gateway sysctl= juju resolve neutron-gateway/0

edit flag offensive delete link more

Comments

Thank you very much!.

Cosme gravatar imageCosme ( 2019-04-25 06:16:51 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

2 followers

Stats

Asked: 2019-04-22 19:10:21 -0600

Seen: 237 times

Last updated: Apr 24