Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Incorrect compute profile values populated for Interfaces tab when provisioning
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 displays incorrect values or we can say it's not fetching the values from the compute profile.
Actual results:
Incorrect values are populated
Expected results:
Selecting the options during new host creation should fetch in the values from compute profiles properly
Additional info:
This issue is not reproduced if the Host Group is selected first and then the Deploy on VMware compute profile
*** Bug 1410194 has been marked as a duplicate of this bug. ***
Comment 17Daniel Lobato Garcia
2017-08-23 14:43:03 UTC
Verified.
Tested on Satellite 6.3 snap 13.
See the attached video. Summing up:
- Created a compute profile with interfaces info
- Created a host group which uses this compute profile
- Created a host which uses aforementioned hostgroup: it contains the interfaces defined by the compute profile.
Comment 18Daniel Lobato Garcia
2017-08-23 14:43:48 UTC
Comment 19Satellite Program
2018-02-21 16:51:07 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-2018:0336
Description of problem: Incorrect compute profile values populated for Interfaces tab when provisioning 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 displays incorrect values or we can say it's not fetching the values from the compute profile. Actual results: Incorrect values are populated Expected results: Selecting the options during new host creation should fetch in the values from compute profiles properly Additional info: This issue is not reproduced if the Host Group is selected first and then the Deploy on VMware compute profile