controller nova services do not get proper domain name/ip

[Tim Rozet]

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-controller-0 internal enabled up 2016-07-19T14:21:02.000000
2 nova-consoleauth overcloud-controller-0 internal enabled up 2016-07-19T14:21:05.000000
5 nova-scheduler overcloud-controller-0 internal enabled up 2016-07-19T14:21:03.000000
6 nova-conductor overcloud-controller-0 internal enabled up 2016-07-19T14:21:06.000000
7 nova-compute overcloud-novacompute-0.opnfvapex.com nova enabled up 2016-07-19T14:21:04.000000
8 nova-compute overcloud-novacompute-1.opnfvapex.com nova enabled up 2016-07-19T14:21:05.000000
----------------------------------------------------------------------------------------------------------------------+

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-controller-0 internal enabled down 2016-07-20T10:03:40.000000
2 nova-consoleauth overcloud-controller-0 internal enabled down 2016-07-20T10:03:38.000000
5 nova-scheduler overcloud-controller-0 internal enabled down 2016-07-20T10:03:39.000000
6 nova-conductor overcloud-controller-0 internal enabled down 2016-07-20T10:03:41.000000
7 nova-compute overcloud-novacompute-0.opnfvapex.com nova enabled down 2016-07-20T10:06:51.000000
8 nova-compute overcloud-novacompute-1.opnfvapex.com nova enabled down 2016-07-20T10:06:51.000000
9 nova-scheduler overcloud-controller-0.opnfvapex.com internal enabled up 2016-07-20T10:08:43.000000
10 nova-cert overcloud-controller-0.opnfvapex.com internal enabled up 2016-07-20T10:08:44.000000
11 nova-conductor overcloud-controller-0.opnfvapex.com internal enabled up 2016-07-20T10:08:44.000000
13 nova-consoleauth overcloud-controller-0.opnfvapex.com internal enabled up 2016-07-20T10:08:44.000000
----------------------------------------------------------------------------------------------------------------------+

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_compute.pp has the nova_config entry for setting myip and host, but controller puppet files do not.

[Tim Rozet (trozet)]

Originally found in OPNFV: https://jira.opnfv.org/browse/APEX-182

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/344969

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/304858
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=056ce2374851e4e96dd3fd822de9da76b35e1eb7
Submitter: Jenkins
Branch: master

commit 056ce2374851e4e96dd3fd822de9da76b35e1eb7
Author: Ben Nemec <email address hidden>
Date: Tue Apr 12 15:44:49 2016 -0500

    Explicitly set nova and neutron host on controllers

    In I7d07c57b7276815c72d08acaa86f673e43eb0498 we set this for compute
    nodes, but we also need it for controllers. Otherwise when a
    controller reboots it may come back up with a different host value,
    which seems to break networking for anything that was created before
    the reboot. In my case, it changes from the short hostname (without
    domain name) to the fqdn. Since we set it to fqdn for the compute
    nodes, let's do the same for controllers.

    This moves all of the host setting to the base yaml of the nova
    and neutron profiles.

    Change-Id: Ieb793b9e9fd2dfc98584691412f9991aa99e0b47
    Closes-Bug: 1604907

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/344969
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=5bb7a725c70a313b6081d54429d06037617c2590
Submitter: Jenkins
Branch: stable/mitaka

commit 5bb7a725c70a313b6081d54429d06037617c2590
Author: Tim Rozet <email address hidden>
Date: Wed Jul 20 14:07:58 2016 -0400

    Fixes nova host configuration on control nodes

    Closes-Bug: 1604907

    nova.conf and neutron.conf is not being configured with host,
    resulting in lack of fqdn in host for nova services on the control
    nodes. Upon reboot duplicate instances of nova services are found
    with correct fqdn on their hostname. This fixes nova and neutron
    conf to set the host value in controller manifests, similar to how
    it is done in compute manifest.

    This is a backport of Ieb793b9e9fd2dfc98584691412f9991aa99e0b47

    Change-Id: Ie11b39de35194c020a8a09b57fdb11e882c5ec7b
    Signed-off-by: Tim Rozet <email address hidden>

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/tripleo-heat-templates 2.1.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 5.0.0.0b3 development milestone.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 2.1.0 release.