Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1192944 - A tool tip is required on add_interface form adjacent to identifier field to clearly state what identifier user should provide based on type of interface
Summary: A tool tip is required on add_interface form adjacent to identifier field to...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Marek Hulan
QA Contact: Sachin Ghai
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On: 1203588
Blocks: 1193987
TreeView+ depends on / blocked
 
Reported: 2015-02-16 09:54 UTC by Sachin Ghai
Modified: 2017-02-23 20:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 05:25:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
currently identifier field has help info like: Device identifier, i.e.: eth0 or eth1.1, which doesn't clearly state what identifier user should provide based on selected interface type (11.20 KB, image/png)
2015-02-16 09:54 UTC, Sachin Ghai 		no flags Details
Firebug raises: "NetworkError: 404 Not Found" (48.54 KB, image/png)
2015-03-13 15:54 UTC, Sachin Ghai 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 9435 0 None None None 2016-04-22 15:02:05 UTC
Red Hat Product Errata RHSA-2015:1592 0 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 09:04:35 UTC

Description Sachin Ghai 2015-02-16 09:54:49 UTC 
Created attachment 992103 [details]
currently identifier field has help info like: Device identifier, i.e.: eth0 or eth1.1, which doesn't clearly state what identifier user should provide based on selected interface type

Description of problem:
While adding new_interface, the identifier field should have a tool-tip that clearly state what identifier user should specify based on type of interface.

If type is alias interface then identifier should be like eth0:0 assuming eth0 is the interface to which alias interface will be attached.

if type is vlan interface then identifier should be line eth0.1

if type is bond interface then identifier should be like bond0.


Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-6-20150210.0
Sat6.1.0 beta snap2

How reproducible:
always

Steps to Reproduce:
1. New/edit Host --> add_interface
2.
3.

Actual results:
currently identifier field has help info like: Device identifier, i.e.: eth0 or eth1.1

which doesn't clearly state what identifier user should provide based on selected interface type

Expected results:

the identifier field should have a tool-tip that clearly state what identifier user should specify based on type of interface.


Additional info:
Comment 2 Bryan Kearney 2015-02-18 21:03:53 UTC 
Created redmine issue http://projects.theforeman.org/issues/9435 from this bug
Comment 3 Bryan Kearney 2015-03-05 15:05:16 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/9435 has been closed
-------------
Marek Hulán
Applied in changeset commit:c3e83a58d6a7d9822340c89e016472d24f897582.
Comment 6 Sachin Ghai 2015-03-13 15:52:25 UTC 
Verified with:

sat6.1 beta snap6 compose2
Satellite-6.1.0-RHEL-6-20150311.1

I can see the tool_tip or info box but when I clicked it, it was not expandable. Also firebug raises Network Error 404 on clicking it.

Please see the screenshot. Moving back to assigned.
Comment 7 Sachin Ghai 2015-03-13 15:54:35 UTC 
Created attachment 1001435 [details]
Firebug raises: "NetworkError: 404 Not Found"
Comment 8 Marek Hulan 2015-03-18 15:10:46 UTC 
Sachin, this is separate issue, please report it and set it as a blocker (tooltip does not work in modal window). It seems that this was fixed in upstream as a part of new networking. I think this should be ON_QA until the blocker is fixed.
Comment 9 Sachin Ghai 2015-03-19 08:19:12 UTC 
Ah.. didn't realize its a separate issue. I'm fine reporting it in separate issue.. Will new bz for reported issue in comment 6..thanks
Comment 10 Sachin Ghai 2015-03-19 08:28:40 UTC 
verification of this bz depends on https://bugzilla.redhat.com/show_bug.cgi?id=1203588
Comment 11 Sachin Ghai 2015-04-29 09:54:39 UTC 
Verified with:

sat6.1 GA snap1 compose2(Satellite-6.1.0-RHEL-7-20150424.0)

I can see tool_tip under add_interface modal window.
Comment 12 Bryan Kearney 2015-08-11 13:22:40 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 13 errata-xmlrpc 2015-08-12 05:25:59 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://access.redhat.com/errata/RHSA-2015:1592
Note You need to log in before you can comment on or make changes to this bug.