-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
0
-
False
-
-
False
-
?
-
rhos-ops-day1day2-edpm
-
None
-
-
-
-
Moderate
To Reproduce Steps to reproduce the behavior:
- Deploy control plane
- Deploy RHEL 9.4 on compute nodes
- Disable ipv6 on the compute node by running:
grubby --update-kernel=ALL --args="ipv6.disable=1" - Reboot compute node
- Deploy data plane as instructed in section 5.3 here
- Deployment fails as ipv6 cannot be configured:
TASK [osp.edpm.edpm_iscsid : Generate a unique IQN] **************************** task path: /usr/share/ansible/collections/ansible_collections/osp/edpm/roles/edpm_iscsid/tasks/configure.yml:33 fatal: [rhoso-lab-m4cdw-compute-0]: FAILED! => {"changed": false, "msg": "Container iscsid_config exited with code 126 when runed", "stderr": "Error: netavark: Sysctl error: no such sysctl: net.ipv6.conf.all.forwarding\n", "stderr_lines": ["Error: netavark: Sysctl error: no such sysctl: net.ipv6.conf.all.forwarding"], "stdout": "", "stdout_lines": []}
Expected behavior
- DataPlane is deployed successfully
Bug impact
- This bug blocks deployment of RHOSO at the customer, unless manually worked around
Known workaround
- Manually edit /usr/share/ansible/collections/ansible_collections/osp/edpm/roles/edpm_podman/templates/podman_network_config.j2, removing the ipv6 subnet from the list, and also changing ipv6_enabled to False.
Additional context
- Problem seems to come from podman_network_config.j2
- Extended details on the case attached