Bug 1093150 - [Openstack-Staypuft]: Deployment Wizard expect the user to enter IP for the host-groups parameters, before the user actually saw the IPs of the discovered hosts.
Summary: [Openstack-Staypuft]: Deployment Wizard expect the user to enter IP for the h...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rubygem-staypuft
Version: 4.0
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: ga
: Installer
Assignee: Mike Burns
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks: 1071241 1098232
TreeView+ depends on / blocked
 
Reported: 2014-04-30 17:58 UTC by Omri Hochman
Modified: 2016-04-26 15:06 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-21 18:04:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1090 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2014-08-22 15:28:08 UTC

Description Omri Hochman 2014-04-30 17:58:09 UTC
[Openstack-Staypuft]: Deployment Wizard Step #2 is expecting the user to enter  IP for the host-groups parameters, before the user actually saw the IPs of the discovered hosts.


Description: 
-------------
At the first page of new deployment wizard - the user enter deployment name and chooses the deployment layout, on the second page the user expect to modify the host groups parameters and to provide the IP of the controller machine (where the QPID/MYSQL is running on) - in this stage the user cannot know the IP of the controller, because the associating the discovered hosts with host-groups is happening only on the third page in the wirzard  

The user (on page #2) is expected to open another tab of the browser and to look at the discovered hosts and to remember the MAC address + IP of one of the hosts, only then he can enter IP at the host groups parameters (page 2)  and associate the correct discovered host with the controller host group (on step 3) by remembering the discovered host mac address.  

Environment (Havana A4 puddle 2014-04-25.2):
---------------------------------------------
ruby193-rubygem-staypuft-0.0.11-5.el6ost.noarch
openstack-foreman-installer-1.0.6-2.el6ost.noarch
ruby193-rubygem-foreman_openstack_simplify-0.0.6-6.el6ost.noarch
openstack-puppet-modules-2013.2-9.el6ost.noarch
puppet-3.3.2-2.el6.noarch
puppet-server-3.3.2-2.el6.noarch
katello-installer-0.0.33-1.el6sat.noarch

Comment 4 Omri Hochman 2014-05-01 08:23:53 UTC
the bug still remain as a pain-point in the flow, there's something wrong in the description the new-deployment-wizrad step #3 is to configure the hosts-groups parameters and only then the user associate the discovered-hosts with the hosts-groups, but still it's a relevant point.

Comment 15 Ami Jeain 2014-08-07 13:00:43 UTC
this scenario doesn't happen in the latest staypuft deployment

Comment 17 errata-xmlrpc 2014-08-21 18:04:06 UTC
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.

http://rhn.redhat.com/errata/RHBA-2014-1090.html


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