Bug in hash network_metadata wrong node_key_name

Bug #1557417 reported by Andrey Kirilochkin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
High
Fuel Library (Deprecated)

Bug Description

What we have:
1. FUEL9
2. Fuel-library - master

What i do:
I have changed the HOST NAME of one node to Contr1, configured env and started the deployment process.

What should be happen:

Successful installation.

What we have instead:
At the deployment stage have this error message:

Node node-1 is not defined in the network_metadata hash structure at /etc/puppet/modules/osnailyfacter/modular/globals/globals.pp:24 on node contr1.domain.tld

This is my network_metadata hash: http://paste.openstack.org/show/490460/

And as you can see the from the manifest globals.pp it calls function get_node_key_name(https://github.com/openstack/fuel-library/blob/master/deployment/puppet/osnailyfacter/lib/puppet/parser/functions/get_node_key_name.rb) that search for node-$ instead of changed hostname.

Changed in fuel:
milestone: none → 9.0
importance: Undecided → High
status: New → Confirmed
assignee: nobody → Fuel Library Team (fuel-library)
tags: added: area-library
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.