rabbitmq ipv6 requires resolution uniqueness
Bug #1848452 reported by
Radosław Piliszek
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Fix Released
|
Medium
|
Radosław Piliszek | ||
Train |
Fix Released
|
Medium
|
Radosław Piliszek | ||
Ussuri |
Fix Released
|
Medium
|
Radosław Piliszek |
Bug Description
RabbitMQ may fail to bind to IPv6 if hostname resolves also to IPv4. This is due to old RabbitMQ versions available in images. IPv4 is preferred by default and may fail in the IPv6-only scenario. This should be no problem in real life as IPv6-only is indeed IPv6-only. Also, when new RabbitMQ (3.7.16/3.8+) makes it into images, this will no longer be relevant as we supply all the necessary config. See: https:/
Changed in kolla: | |
status: | New → Triaged |
milestone: | none → 10.0.0 |
Changed in kolla-ansible: | |
milestone: | none → 10.0.0 |
Changed in kolla: | |
importance: | Undecided → Medium |
Changed in kolla: | |
assignee: | nobody → Dincer Celik (osmanlicilegi) |
status: | Triaged → In Progress |
Changed in kolla-ansible: | |
assignee: | nobody → Dincer Celik (osmanlicilegi) |
Changed in kolla-ansible: | |
assignee: | Dincer Celik (osmanlicilegi) → Radosław Piliszek (yoctozepto) |
status: | Triaged → In Progress |
To post a comment you must log in.
Don't close on k-a side until it is confirmed to be fixed though.