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 1820522 - Bare-metal host 'Deploy On' setting doesn't persist
Summary: Bare-metal host 'Deploy On' setting doesn't persist
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources
Version: 6.6.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
: 1903223 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-03 09:40 UTC by Anand Jambhulkar
Modified: 2023-09-07 22:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-28 18:00:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 25799 0 Normal New Bare-metal host 'Deploy On' setting doesn't persist 2020-12-01 16:12:27 UTC

Description Anand Jambhulkar 2020-04-03 09:40:27 UTC 
Description of problem:
----------------------

The customer has some bare-metal hosts in a hostgroup that has 'Deploy On' defaulted to a vmware compute resource.

Each time they edit the hosts, they have to set 'Deploy On' back to 'bare metal'.

They need to do this before they can 'submit' any changes they've made.

But afterwards, the host page still has a 'VM' tab and the 'Deploy On' change isn't persisted.

The bug has been already filed in upstream whose link is given down below - 

	https://projects.theforeman.org/issues/25799



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

Satellite 6.6.1


How reproducible:
----------------

Always


Steps to Reproduce:
------------------

1. Create a hostgroup with the "Deploy On" setting set to vmware compute resource.

2. Then, try to provision a bare metal host with this particular hostgroup where the setting of the "Deploy On" should be manually changed to "Bare Metal" instead of what the hostgroup sets it to by default.

3. Then provision a hostgroup with the above setting in place.

4. After the host is completely provisioned, check the above "Deploy On" setting by editing the host. It is now defaulted to vmware instead of being bare metal.


Actual results:

The "Deploy On" field changes to vmware instead of being "Bare Metal" which was set manually.


Expected results:

The "Deploy On" field should not change to vmware, and instead should be showing as set to "Bare Metal" which was set manually.


Additional info:

The upstream foreman tracker link - https://projects.theforeman.org/issues/25799
Comment 3 Tomer Brisker 2021-07-01 09:03:14 UTC 
*** Bug 1903223 has been marked as a duplicate of this bug. ***
Comment 5 Brad Buckingham 2022-09-02 20:25:18 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 6 Brad Buckingham 2022-09-02 20:31:56 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 7 Brad Buckingham 2022-10-28 18:00:09 UTC 
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.
Note You need to log in before you can comment on or make changes to this bug.