Description of problem: undercloud GUI- Image field is mandatory when setting VM for deploy overcloud. When deploying overcloud via cli and verifying it in GUI it's looks like VM configured with "unknown" image. Version-Release number of selected component (if applicable): RHEL-OSP director puddle 7.0 RC puddle 2015-06-26-3 [stack@instack images]$ rpm -qa |grep tuskar python-tuskarclient-0.1.18-3.el7ost.noarch openstack-tuskar-0.4.18-3.el7ost.noarch openstack-tuskar-ui-extras-0.0.4-1.el7ost.noarch openstack-tuskar-ui-0.3.0-6.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy undercloud 2. Log in to the undercloud UI dashboard 3. Go to deployment roles 4. you can see that image shown as "unknown" Actual results: Expected results: Additional info:
I deploy overcloud via CLI its worked well.Verified it in GUI checked how it looks like in GUI. Then I undeploy it via GUI and tried to run again deploy via GUI and got errors : https://bugzilla.redhat.com/show_bug.cgi?id=1237044
So to clarify a bit further, the issue here is that if you deploy an overcloud via the CLI and then log into the GUI, the Roles page doesn't display associated images. The cause is that the GUI expects to find the image UUID in the Tuskar plan parameter, but this parameter contains the image name. I am not sure if the parameter should contain the image UUID or the image name. If it should contain the image UUID, then this bug is on the Tuskar side - we need to make Tuskar save the UUID into the plan parameter instead of the name. If the parameter should contain the name, then this bug is on the GUI side and we need to make sure the GUI expects the name and not the UUID. Jay, could you please clarify if the UUID or the name should be saved to the plan paramter.
Yes , Ana Krivokapic you right this is exactly what happens
The plan should use the image name.
*** Bug 1233623 has been marked as a duplicate of this bug. ***
Upstream patch: https://review.openstack.org/#/c/198464/
Verified on Virt env. openstack-tuskar-ui-0.4.0-3.el7ost.noarch
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/RHSA-2015:1862