Bug 1322053 - No auto-suggestion of IP values populated in Interfaces tab when provisioning and selecting deploy first.
Summary: No auto-suggestion of IP values populated in Interfaces tab when provisioning...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Marek Hulan
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-29 16:14 UTC by Kedar Bidarkar
Modified: 2019-09-26 13:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-21 21:25:17 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Kedar Bidarkar 2016-03-29 16:14:50 UTC
Description:
 No auto-suggestion of IP values populated in Interfaces tab when provisioning and selecting deploy first and not "host-group".

Version-Release number of selected component (if applicable):
Satellite 6.2 Beta

How reproducible:
100% 

Steps to Reproduce:

1. Create a compute resource (VMware) and associate a compute profile with it.
2. Create a Host group to associate with this compute profile
2. Create a new host 
     i. Select Deploy on VMware compute resource
     ii. Select Host Group 
     iii. Now check the Interfaces tab which does not autosuggest the IP address.


Actual results:
No auto suggestion of IP address

Expected results:

Auto suggestion of IP address

Additional info:
This issue is not reproduced if the Host Group is selected first and then the Deploy on VMware compute resource

Comment 3 Marek Hulan 2016-04-12 13:56:13 UTC
Kedar, according to logs it didn't even try to do IP request, it failed on the same error reported at https://bugzilla.redhat.com/show_bug.cgi?id=1313659. That could cause no IP auto-suggestion. You didn't specify exact version so I'd like to ask you to check again with latest snap, the linked BZ seems to be fixed in sat6.2 beta snap5.1

Comment 4 Kedar Bidarkar 2016-04-15 17:21:57 UTC
I re-tested this with sat62-snap8.1 , auto IP sugestion works perfectly fine if,

a) hostgroup is selected first and then
b) deploy on CR field

But if we select the other way,

a) deploy on CR field first and then 
b) hostgroup is selected

we face this issue.

This is similar to the issue reported in this bug https://bugzilla.redhat.com/show_bug.cgi?id=1261663, but may be the changes were not in as we now have a new interfaces tab for sat6.2. :)

This issue is not related to https://bugzilla.redhat.com/show_bug.cgi?id=1313659

Also I will be attaching a screenshot of the same.

Comment 6 Bryan Kearney 2017-03-21 21:25:17 UTC
I do not believe this will be addressed int he next few releases, so I am closing this out. If you feel this was incorrect, please feel free to re-open with additional information.


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