Bug 997023

Summary: Duplicate entries on "Hypervisor" screen.
Product: [Community] RDO Reporter: Stephen Gordon <sgordon>
Component: openstack-novaAssignee: RHOS Maint <rhos-maint>
Status: CLOSED WONTFIX QA Contact: Ami Jeain <ajeain>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: lars, ndipanov, rbryant, sgordon, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-15 15:15:36 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:
Attachments:
Description Flags
Answer File none

Description Stephen Gordon 2013-08-14 13:53:18 UTC 
Description of problem:

I installed an all in one setup using packstack and noticed that when I access the "Hypervisors" screen on the dashboard there are two hosts listed (hostname redacted slightly to protect the innocent)

Hypervisors
Hostname 	Type 	VCPUs (total) 	VCPUs (used) 	RAM (total) 	RAM (used) 	Storage (total) 	Storage (used) 	Instances
unused-10-WW-XX-105.ZZ.com	QEMU	2	0	3830 MB	512 MB	18 GB	0 GB	0
unused-10-WW-XX-104.ZZ.com	QEMU	2	0	3830 MB	512 MB	18 GB	0 GB	0

There is only one host in my environment but based on the hostnames listed (and the associated IPs) I believe the "two hosts" are actually the two NICs of the same host. The command line tools indicate the same:

# nova host-list
+------------------------------------+-------------+----------+
| host_name                          | service     | zone     |
+------------------------------------+-------------+----------+
| unused-10-WW-XX-104.ZZ.com         | cert        | internal |
| unused-10-WW-XX-104.ZZ.com         | compute     | nova     |
| unused-10-WW-XX-104.ZZ.com         | conductor   | internal |
| unused-10-WW-XX-104.ZZ.com         | consoleauth | internal |
| unused-10-WW-XX-104.ZZ.com         | scheduler   | internal |
| unused-10-WW-XX-105.ZZ.com         | cert        | internal |
| unused-10-WW-XX-105.ZZ.com         | compute     | nova     |
| unused-10-WW-XX-105.ZZ.com         | conductor   | internal |
| unused-10-WW-XX-105.ZZ.com         | consoleauth | internal |
| unused-10-WW-XX-105.ZZ.com         | scheduler   | internal |
+------------------------------------+-------------+----------+


Version-Release number of selected component (if applicable):

python-django-horizon-2013.2-0.5b2.el6.noarch
openstack-packstack.2013.2.1-0.2.dev702.el6.noarch
python-novaclient-2.13.0-1.el6.noarch
openstack-nova-api-2013.2-0.8.b2.el6.noarch
openstack-nova-conductor-2013.2-0.8.b2.el6.noarch
openstack-nova-common-2013.2-0.8.b2.el6.noarch
openstack-nova-novncproxy-2013.2-0.8.b2.el6.noarch
openstack-nova-cert-2013.2-0.8.b2.el6.noarch
openstack-nova-compute-2013.2-0.8.b2.el6.noarch
openstack-nova-console-2013.2-0.8.b2.el6.noarch
python-nova-2013.2-0.8.b2.el6.noarch
openstack-nova-scheduler-2013.2-0.8.b2.el6.noarch
Comment 1 Stephen Gordon 2013-08-14 14:38:22 UTC 
Created attachment 786557 [details]
Answer File

Attached answer file, sanitized with the IP address from eth1 replaced with 10.11.5.19 (example.com) - the IP address for eth0 didn't appear anywhere in the file.

The file was generated with the --gen-answer-file directive and the only detail I changed was the admin password.
Comment 3 Lars Kellogg-Stedman 2014-01-15 15:06:13 UTC 
We're in the process of validating RDO bug reports.  Are you still experiencing this issue with the current RDO packages?
Comment 4 Stephen Gordon 2014-01-15 15:15:36 UTC 
Who knows, it's been 4 months and an entire release... :P