Bug 1406826

Summary: Duplicate nova hypervisors show up in nova hypervisor-list post 10 -> 11 upgrade
Product: Red Hat OpenStack Reporter: Marius Cornea <mcornea>
Component: openstack-tripleo-heat-templatesAssignee: Marios Andreou <mandreou>
Status: CLOSED ERRATA QA Contact: Marius Cornea <mcornea>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 11.0 (Ocata)CC: emacchi, jcoufal, jjoyce, jschluet, jstransk, mandreou, markmc, mburns, mcornea, ohochman, rhel-osp-director-maint, sathlang, sclewis, tvignaud
Target Milestone: rcKeywords: TestOnly, Triaged
Target Release: 11.0 (Ocata)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1365789 Environment:
Last Closed: 2017-05-17 19:51:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 1 Marius Cornea 2016-12-21 15:12:30 UTC
In OSP11 ComputeHostnameFormat is set to '%stackname%-novacompute-%index% so we'll most probably hit the same issue with it as in the past:

[stack@undercloud-0 ~]$ grep -A3 Compute /usr/share/openstack-tripleo-heat-templates/roles_data.yaml  | grep HostnameFormatDefault
  HostnameFormatDefault: '%stackname%-novacompute-%index%'

[stack@undercloud-0 ~]$ rpm -qa | grep tripleo-heat-templates
openstack-tripleo-heat-templates-6.0.0-0.20161130195427.9cd0c5a.el7ost.noarch

Comment 6 Marius Cornea 2017-02-23 14:39:14 UTC
*** Bug 1425472 has been marked as a duplicate of this bug. ***

Comment 7 Sofer Athlan-Guyot 2017-03-21 18:25:19 UTC
Putting this back to POST as it landed downstream.

Marius can you confirm that it has been release in latest puddle and is not an issue anymore.

Thanks,

Comment 8 Marius Cornea 2017-03-22 11:19:59 UTC
Yes, this is fixed in the latest puddle.

Comment 10 errata-xmlrpc 2017-05-17 19:51:55 UTC
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/RHEA-2017:1245