Bug 1379670

Summary: ramidsk not configured when registering nodes from the GUI
Product: Red Hat OpenStack Reporter: Udi Kalifon <ukalifon>
Component: rhosp-director-uiAssignee: Jason E. Rist <jrist>
Status: CLOSED WONTFIX QA Contact: Ola Pavlenko <opavlenk>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 9.0 (Mitaka)CC: dtrainor, flfuchs, rhel-osp-director-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-01 15:40:12 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:

Description Udi Kalifon 2016-09-27 12:14:09 UTC 
Description of problem:
If you register the nodes via the GUI and then try to deploy via the CLI you see the following error repeated for each node you have:

Node uuid=c26b9301-1168-4d6e-b725-67150d853fe4 has an incorrectly configured driver_info/deploy_ramdisk. Expected "0effa981-ca43-459b-9399-2f62b2e27e99" but got "None".


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


How reproducible:
100%


Steps to Reproduce:
1. Install OSP9+UI
2. Register nodes from the GUI
3. Introspect and provide nodes
4. Try to deploy via the CLI
=> Deployment fails right at the beginning and doesn't let you continue until you fix the issue.


Additional info:
The command "openstack baremetal configure boot" is the missing step in this flow.
Comment 2 Florian Fuchs 2016-09-30 07:21:26 UTC 
Fixed in the playbook by using tripleo-common release 5.1.0 as a base instead of master.
Comment 3 Udi Kalifon 2017-02-01 15:39:31 UTC 
This is covered by the automation and doesn't happen any more in 10.