nodename list disregards network
Bug #1628521 reported by
Juan Antonio Osorio Robles
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Juan Antonio Osorio Robles |
Bug Description
not all services are listening on the internal_api network. And it seems that when generating the node_names for each service, we disregard which network they're using. So, in the end, configurations that use these names do not use the one appropriate for the network.
An example of the output is this:
$ hiera rabbitmq_node_names
["overcloud-
$ hiera gnocchi_
["overcloud-
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: composable-roles |
Changed in tripleo: | |
assignee: | Steven Hardy (shardy) → Juan Antonio Osorio Robles (juan-osorio-robles) |
Changed in tripleo: | |
assignee: | Juan Antonio Osorio Robles (juan-osorio-robles) → Steven Hardy (shardy) |
Changed in tripleo: | |
milestone: | none → newton-rc3 |
tags: | added: newton-backport-potential |
Changed in tripleo: | |
assignee: | Steven Hardy (shardy) → Juan Antonio Osorio Robles (juan-osorio-robles) |
Changed in tripleo: | |
milestone: | newton-rc3 → ocata-1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/378764
Review: https:/