Bug 1389298

Summary: [Beta 1] When editing Hosts in Infrastructure, IP is not used in edit windows...
Product: Red Hat CloudForms Management Engine Reporter: Loic Avenel <lavenel>
Component: UI - OPSAssignee: Dan Clarizio <dclarizi>
Status: CLOSED NOTABUG QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.7.0CC: dclarizi, gblomqui, hkataria, jhardy, mpovolny, obarenbo
Target Milestone: GAKeywords: FutureFeature
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 20:31:35 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:
Attachments:
Description Flags
View of details
none
Edit Screenshots none

Description Loic Avenel 2016-10-27 12:02:22 UTC
Created attachment 1214579 [details]
View of details

Description of problem: When editing Hosts in Infrastructure, IP is not used in edit windows...


Version-Release number of selected component (if applicable): 5.7.0.7-beta1.20161025153249_9376fbd


How reproducible: Always


Steps to Reproduce:
1. Go to Host.. you can see Hostname and IP
2. Edit Host
3. 

Actual results: Host and IP has Hostname, then if hostname cannot be resolved, validate credentials is failing 


Expected results: IP field contains the IP


Additional info:

Comment 2 Loic Avenel 2016-10-27 12:02:54 UTC
Created attachment 1214580 [details]
Edit Screenshots

Comment 3 Dave Johnson 2016-11-03 00:58:54 UTC
Ok, looking at the screenshots, this does seem like the UI is pulling in the wrong value.  With that said though, its working as designed to not allow edits for this value, we use what the provider is reporting.

Since this would impact adding credentials, I believe we have to make this H/H blocker for 5.7

Comment 4 Loic Avenel 2016-11-03 01:01:55 UTC
Provider is reporting the IP, so, we should put the IP in IP...

Comment 5 Greg Blomquist 2016-11-03 20:05:43 UTC
I don't think the UI is pulling in the wrong value.  There's a field for `hostname` that's editable.  Then, there's a field for `ipaddress` which is *not* editable.

A couple of years ago it was decided that `hostname` would store any value of:

* hostname
* ipv4
* ipv6

And, if hostname is entered, the reverse-dns lookup for ipaddress would be saved in ipaddress.

Looking at the first screenshot (the summary page) it looks like the `hostname` field has "esxi" and the `ipaddress` field has the value "10.9.62.6" which was looked up based on the hostname.

On the edit page, the `hostname` field from the DB is used to populate the (albeit, poorly named) "Hostname (or IPv4 or IPv6)" text field.  And, that's what the user is allowed to edit.

If you're saying you'd like to be able to edit *both* the hostname and the IP address field, that's a separate RFE, and we'll have to reopen the history books to remember why it was decided to make it read-only in the first place.

IMO, this is not-a-bug.

Comment 6 Loic Avenel 2016-11-03 23:10:11 UTC
Ok, got it, we can close it.. I will make sure this is well documented