Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1187815

Summary: Add an indicator to Assigned Hosts table to show when networks have been configured
Product: Red Hat OpenStack Reporter: Matt Reid <mreid>
Component: ruby193-rubygem-staypuftAssignee: Jason E. Rist <jrist>
Status: CLOSED ERRATA QA Contact: Alexander Chuzhoy <sasha>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0 (Juno)CC: aberezin, ajeain, dmacpher, mburns, rhos-maint, sasha, sseago, yeylon
Target Milestone: z2Keywords: UserExperience, ZStream
Target Release: Installer   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ruby193-rubygem-staypuft-0.5.0-20.el7ost Doc Type: Enhancement
Doc Text:
This fix adds an indicator on the UI to show when a NIC is configured. This is due to the UI giving no indication of what hosts were and were not configured. The UI shows after a page refresh the hosts that have NICs configured and what subnet is configured on that NIC.
 Story Points: ---
Clone Of:
: 1202530 (view as bug list) Environment:
Last Closed: 2015-04-07 15:08:04 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1202530    
Attachments:
Description Flags
One of these has been configured, the other hasn't none

Description Matt Reid 2015-01-30 21:58:56 UTC 
Description of problem:
When deploying a HA OSP environment, you're setting up at least 5 nodes, and possibly more. If you have to go through and configure the networks for each of them individually, or even in smaller groups (or by node type?), it would be nice to see from the table view which ones you've already looked at and edited. Currently you have to click down into each one, set it, remember that you set it, and if you lose your place or forget, have to go to edit it again to find out.

It would be more efficient if the table indicated which you had edited, or at least viewed.

Could we just add which subnet was assigned to a NIC in the NICs column? 
For example:
br_int
br_tun
ens7: Tenant
eth0
ovs_system

Version-Release number of selected component (if applicable):
current qe (0.5.15?)
Comment 3 Matt Reid 2015-01-30 22:00:21 UTC 
Created attachment 986296 [details]
One of these has been configured, the other hasn't

I've configured one of these nodes already to have a tenant network, which one was it? There's no way to tell from the table view which one I still need to configure.
Comment 7 Scott Seago 2015-03-11 17:30:38 UTC 
https://github.com/theforeman/staypuft/pull/423
Comment 9 Alexander Chuzhoy 2015-03-13 22:42:40 UTC 
Verified: FailedQA


Environment:
rhel-osp-installer-client-0.5.7-1.el7ost.noarch
openstack-foreman-installer-3.0.17-1.el7ost.noarch
rhel-osp-installer-0.5.7-1.el7ost.noarch
ruby193-rubygem-staypuft-0.5.21-1.el7ost.noarch
openstack-puppet-modules-2014.2.8-2.el7ost.noarch
ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el7ost.noarch


While the requested functionality is there, the user needs to refresh the page for the column to be updated.

After the refresh, the NIC column with ens7 assigned to tenant looks like that:
eth1 (default)
ens7 (tenant)
Comment 10 Mike Burns 2015-03-16 20:01:31 UTC 
After discussion, we're going to split the page refresh to a separate bug and move this back ON_QA.  The fix is correct in this bug, just not immediately displayed and getting the fix is not guaranteed at this point
Comment 11 Mike Burns 2015-03-16 20:05:35 UTC 
bug for the refresh/reload part:  bug 1202530
Comment 12 Alexander Chuzhoy 2015-03-16 20:10:04 UTC 
Verified:
Environment:
rhel-osp-installer-client-0.5.7-1.el7ost.noarch
openstack-foreman-installer-3.0.17-1.el7ost.noarch
rhel-osp-installer-0.5.7-1.el7ost.noarch
ruby193-rubygem-staypuft-0.5.21-1.el7ost.noarch
openstack-puppet-modules-2014.2.8-2.el7ost.noarch
ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el7ost.noarch


Verifying based on comment #11 and comment #9.
Comment 14 errata-xmlrpc 2015-04-07 15:08:04 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.

https://rhn.redhat.com/errata/RHSA-2015-0791.html