Bug 1767160
| Summary: | Overcloud deployment for spine/leaf stack fails setting firewall rules | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Alistair Tonner <atonner> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Giulio Fidente <gfidente> |
| Status: | CLOSED ERRATA | QA Contact: | Yogev Rabl <yrabl> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 14.0 (Rocky) | CC: | cjeanner, dhill, gcharot, gfidente, jfrancoa, jjoyce, jschluet, lbezdick, lmiccini, mburns, michele, rszmigie, slinaber, tvignaud |
| Target Milestone: | z4 | Keywords: | Triaged, ZStream |
| Target Release: | 14.0 (Rocky) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-heat-templates-9.3.1-0.20190513171772.el7ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-12-20 16:49:31 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1770345 | ||
|
Description
Alistair Tonner
2019-10-30 19:48:29 UTC
Hello Alistair, I tried to find the log line you mention in order to get some more context, but.... nothing in stack home, and apparently nothing matches that in /var/log directory. Care to provide some more info? Thank you! Cheers, C. Cedric:
This can be seen in var/lib/mistral/overcloud/ansible.log
A full block for one of the OC nodes is:
"<192.168.24.23> (1, '\\n{\"msg\": \"ERROR: Exception caught: org.fedoraproject.FirewallD1.Exception: INVALID_ADDR: 172.120.3.0/24,172.117.3.0/24,172.118.3.0/24,172.119.3.0/24 Permanent and Non-Permanent(immediate) operation\", \"failed\": true, \"exception\": \" File \\\\\"/tmp/ansible_g8NKeT/ansible_modlib.zip/ansible/module_utils/firewalld.py\\\\\", line 103, in action_handler\\\\n return action_func(*action_func_args)\\\\n File \\\\\"/tmp/ansible_g8NKeT/ansible_module_firewalld.py\\\\\", line 464, in set_enabled_permanent\\\\n self.update_fw_settings(fw_zone, fw_settings)\\\\n File \\\\\"/tmp/ansible_g8NKeT/ansible_modlib.zip/ansible/module_utils/firewalld.py\\\\\", line 134, in update_fw_settings\\\\n fw_zone.update(fw_settings)\\\\n File \\\\\"<string>\\\\\", line 2, in update\\\\n File \\\\\"/usr/lib/python2.7/site-packages/slip/dbus/polkit.py\\\\\", line 103, in _enable_proxy\\\\n return func(*p, **k)\\\\n File \\\\\"<string>\\\\\", line 2, in update\\\\n File \\\\\"/usr/lib/python2.7/site-packages/firewall/client.py\\\\\", line 53, in handle_exceptions\\\\n return func(*args, **kwargs)\\\\n File \\\\\"/usr/lib/python2.7/site-packages/firewall/client.py\\\\\", line 441, in update\\\\n self.fw_zone.update(tuple(settings.settings))\\\\n File \\\\\"/usr/lib/python2.7/site-packages/slip/dbus/proxies.py\\\\\", line 50, in __call__\\\\n return dbus.proxies._ProxyMethod.__call__(self, *args, **kwargs)\\\\n File \\\\\"/usr/lib64/python2.7/site-packages/dbus/proxies.py\\\\\", line 145, in __call__\\\\n **keywords)\\\\n File \\\\\"/usr/lib64/python2.7/site-packages/dbus/connection.py\\\\\", line 651, in call_blocking\\\\n message, timeout)\\\\n\", \"invocation\": {\"module_args\": {\"service\": \"ceph\", \"zone\": \"public\", \"masquerade\": null, \"immediate\": true, \"source\": \"172.120.3.0/24,172.117.3.0/24,172.118.3.0/24,172.119.3.0/24\", \"state\": \"enabled\", \"permanent\": true, \"timeout\": 0, \"interface\": null, \"offline\": null, \"port\": null, \"rich_rule\": null}}}\\n', '')",
Hello Alistair, Ah, damn, it didn't show up with my `grep -r'... Thank you! Will investigate deeper, but it might be related to ceph-ansible. Stay tuned! C. *** Bug 1777318 has been marked as a duplicate of this bug. *** *** Bug 1777773 has been marked as a duplicate of this bug. *** *** Bug 1783522 has been marked as a duplicate of this bug. *** Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:4339 |