Hide Forgot
Description of problem: In an ipv6 environment on Ubuntu, if all.yml for ansible playbook is configured with radosgw_interface: <interface>, then after the successful completion of ansible playbook, the ceph.conf generated for the rgw node is incorrect Instead of IPv6 address of rgw node, it contains port=[0.0.0.0]:8080 Version-Release number of selected component (if applicable): ansible 2.6.5-2redhat1 ceph-ansible 3.2.0~rc5-2redhat1 ceph version 12.2.8-39redhat1xenial How reproducible: Always Steps to Reproduce: 1.Install rgw node using ansible playbook with all.yml containing radosgw_interface: <interface> 2.Check the ceph.conf on rgw node Actual results: The ceph.conf for rgw node contains [0.0.0.0]:8080 instead of actual IPv6 address of rgw node Expected results: The ceph.conf for rgw node should contain IPv6 address of rgw node Additional info: The ceph.conf is generated correctly when radosgw_address parameter is used instead of radosgw_interface parameter in all.yml
potential fix here, but haven't been able to test it. waiting on a review / CI to run https://github.com/ceph/ceph-ansible/pull/3404
@Thomas thanks, i was thinking it just needed to be merged. in the future, should the ticket not go into POST until after the fix is in a tag?
(In reply to Noah Watkins from comment #8) > @Thomas thanks, i was thinking it just needed to be merged. in the future, > should the ticket not go into POST until after the fix is in a tag? No, as long as there's an upstream fix somewhere, leaving the BZ in POST is fine. Thomas
https://github.com/ceph/ceph-ansible/releases/tag/v3.2.0rc7
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:0020