Deploying neutron-gateway fails if ipv6 is disabled on the host or instance
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Neutron Gateway Charm |
Triaged
|
Medium
|
Unassigned |
Bug Description
When deploying cs:openstack-base, if ipv6 is disabled on the target nodes at the kernel level, neutron-gateway will fail with the following message in the logs, and the hook will exit 1, instead of 0, causing the unit to go into 'error' state:
2020-06-05 18:38:13 DEBUG config-changed net.ipv4.
2020-06-05 18:38:13 DEBUG config-changed net.ipv4.
2020-06-05 18:38:13 DEBUG config-changed net.ipv4.
2020-06-05 18:38:13 DEBUG config-changed sysctl: cannot stat /proc/sys/
2020-06-05 18:38:13 DEBUG config-changed sysctl: cannot stat /proc/sys/
2020-06-05 18:38:13 DEBUG config-changed sysctl: cannot stat /proc/sys/
2020-06-05 18:38:13 DEBUG config-changed net.nf_
2020-06-05 18:38:13 DEBUG config-changed net.netfilter.
2020-06-05 18:38:13 DEBUG config-changed net.netfilter.
2020-06-05 18:38:13 DEBUG config-changed none
2020-06-05 18:38:13 DEBUG config-changed Traceback (most recent call last):
2020-06-05 18:38:13 DEBUG config-changed File "/var/lib/
2020-06-05 18:38:13 DEBUG config-changed main()
2020-06-05 18:38:13 DEBUG config-changed File "/var/lib/
2020-06-05 18:38:13 DEBUG config-changed hooks.execute(
2020-06-05 18:38:13 DEBUG config-changed File "/var/lib/
2020-06-05 18:38:13 DEBUG config-changed self._hooks[
2020-06-05 18:38:13 DEBUG config-changed File "/var/lib/
2020-06-05 18:38:13 DEBUG config-changed stopstart, restart_functions)
2020-06-05 18:38:13 DEBUG config-changed File "/var/lib/
2020-06-05 18:38:13 DEBUG config-changed r = lambda_f()
2020-06-05 18:38:13 DEBUG config-changed File "/var/lib/
2020-06-05 18:38:13 DEBUG config-changed (lambda: f(*args, **kwargs)), __restart_
2020-06-05 18:38:13 DEBUG config-changed File "/var/lib/
2020-06-05 18:38:13 DEBUG config-changed return f(*args, **kwargs)
2020-06-05 18:38:13 DEBUG config-changed File "/var/lib/
2020-06-05 18:38:13 DEBUG config-changed '/etc/sysctl.
2020-06-05 18:38:13 DEBUG config-changed File "/var/lib/
2020-06-05 18:38:13 DEBUG config-changed raise e
2020-06-05 18:38:13 DEBUG config-changed File "/var/lib/
2020-06-05 18:38:13 DEBUG config-changed check_call(call)
2020-06-05 18:38:13 DEBUG config-changed File "/usr/lib/
2020-06-05 18:38:13 DEBUG config-changed raise CalledProcessEr
2020-06-05 18:38:13 DEBUG config-changed subprocess.
2020-06-05 18:38:13 ERROR juju.worker.
The machine in this case, is maas-provisioned, and contains the kernel arg 'ipv6.disable=1', among others, which is inherited by the machines, VMs and units that maas and juju deploy.
Removing this arg from the neutron-gateway/0 node, re-running 'update-grub' and rebooting that node, allows the charm hooks to continue without error (after 'juju resolved neutron-gateway/0' of course).
Ideally, if ipv6 is disabled, the ipv6-specific tunables should be excluded from the hook, and only the ipv4 tunables applied.
Changed in charm-neutron-gateway: | |
status: | New → Triaged |
importance: | Undecided → Medium |
I also ran into this issue while trying to deploy OpenStack Ussuri with Kolla Ansible.