Red Hat Bugzilla – Bug 1209908
[RFE] [RDO-Manager] [GUI] Add ability to create images in the GUI
Last modified: 2015-12-01 15:15:05 EST
Description of problem: GUI doesn't allow user to create/upload images. It would be nice to allow user to do this. Version-Release number of selected component (if applicable): Latest master. How reproducible: 100 % Steps to Reproduce: 1. Install RDO-Manager GUI through Instack 2. Log into the GUI 3. Go to images tab Actual results: No possibility to upload images. Expected results: Button to click and get modal window where I can create an image.
Ana, would you be able to describe, how to test this? We might also need docs?
This feature consist of a horizon change[1] and a tuskar-ui change[2]. [1] adds Kernel and Ramdisk fields to the create image form in horizon, which enables a user to associate a kernel and a ramdisk to a glance image during image creation. Expected change is that the kernel and ramdisk fields are now present in the create image form, and that picking a kernel and/or ramdisk should result in a creation of an image with the kernel/ramdisk associated. You can verify that they got associated by accessing the image detail page and checking for associated kernel and ramdisk. [2] simply exposes horizon's create image form (with the newly added capability to set kernel and ramdisk) in the tuskar-ui. On the images page, there should now be a "create image" button which allows the user to create an image. [1] https://review.openstack.org/#/c/179833/ [2] https://review.openstack.org/#/c/178235/
Verified: Environment: python-django-horizon-2015.1.1-2.el7ost.noarch The "+Create Image" button exists now under "Provisioning Images" tab and it allows creating new images. Tested the ability to create a new image - works.
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/RHBA-2015:1874