Bug 1382577 - Missnamed nodes when using scheduler_hints_env.yaml
Summary: Missnamed nodes when using scheduler_hints_env.yaml
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 8.0 (Liberty)
Hardware: All
OS: Linux
high
high
Target Milestone: ---
: 8.0 (Liberty)
Assignee: Angus Thomas
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-07 05:15 UTC by VIKRANT
Modified: 2019-12-16 07:01 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-02 20:33:53 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description VIKRANT 2016-10-07 05:15:22 UTC
Description of problem:

Missnamed nodes when using scheduler_hints_env.yaml

Cu has used scheduling hints to control node placement as per the instructions here https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/paged/director-installation-and-usage/63-controlling-node-placement

Unfortunately they have encountered an issue where two nodes have been assigned the same name as two other nodes.

The issue only seems to be affecting the deployed instances, and not anything shown in nova list on the undercloud.

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

How reproducible:


Steps to Reproduce:
1. Deploy the setup by specifying scheduler_hints_env.yaml file. 
2. Some nodes are taking duplicate hostname. 
3.

Actual results:
overcloud nodes not picking the correct hostname.

Expected results:
overcloud nodes should pick the correct hostname. 

Additional info:
Issue is **not** similar to one mentioned in [1]

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1353920

Comment 2 Zane Bitter 2016-10-07 14:10:23 UTC
This is inexplicable to me. Heat uses the HostnameMap to select the 'name' property to pass to Nova, which appears to be working based on the output of nova list. The actual hostname on the box should be the one given to it by Nova - it's not specified in any other way - so I have no idea how this mismatch could occur.

Comment 4 Steve Baker 2018-04-02 20:33:53 UTC
This bug is quite old now. Please repoen if this is still an issue.


Note You need to log in before you can comment on or make changes to this bug.