controller nova services do not get proper domain name/ip
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Ben Nemec | ||
Liberty |
Won't Fix
|
Undecided
|
Unassigned | ||
Mitaka |
Fix Released
|
Undecided
|
Tim Rozet |
Bug Description
The problem is nova services on the controller lack host name in their host config. When doing nova service-list for the overcloud:
[stack@undercloud ~]$ nova service-list
-------
Id Binary Host Zone Status State Updated_at Disabled Reason
-------
1 nova-cert overcloud-
2 nova-consoleauth overcloud-
5 nova-scheduler overcloud-
6 nova-conductor overcloud-
7 nova-compute overcloud-
8 nova-compute overcloud-
-------
Upon rebooting, duplicate instances of the nova services start now with the correct domain name:
[stack@undercloud ~]$ nova service-list
-------
Id Binary Host Zone Status State Updated_at Disabled Reason
-------
1 nova-cert overcloud-
2 nova-consoleauth overcloud-
5 nova-scheduler overcloud-
6 nova-conductor overcloud-
7 nova-compute overcloud-
8 nova-compute overcloud-
9 nova-scheduler overcloud-
10 nova-cert overcloud-
11 nova-conductor overcloud-
13 nova-consoleauth overcloud-
-------
After this a user is not able to start any nova instances. In puppet-nova on master, a user is able to set nova::host to set the hostname of the node, but in stable/mitaka this option does not exist. overcloud_
description: | updated |
Changed in tripleo: | |
assignee: | Tim Rozet (trozet) → Ben Nemec (bnemec) |
Changed in tripleo: | |
importance: | Undecided → High |
milestone: | none → newton-3 |
Originally found in OPNFV: https:/ /jira.opnfv. org/browse/ APEX-182