Bug 1868183 - Unable to change virt-who hypervisor location.
Summary: Unable to change virt-who hypervisor location.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts - Content
Version: 6.8.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: 6.8.0
Assignee: Jonathon Turel
QA Contact: Stephen Wadeley
URL:
Whiteboard:
: 1868184 1872592 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-11 22:21 UTC by Varatharaja Perumal G
Modified: 2020-10-27 13:08 UTC (History)
3 users (show)

Fixed In Version: tfm-rubygem-katello-3.16.0.3-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 13:05:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 30702 0 Normal Closed Unable to change host location 2021-01-12 09:15:38 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 13:08:31 UTC

Description Varatharaja Perumal G 2020-08-11 22:21:10 UTC 
Description of problem:

Once virt-who reported the hypervisor we are unable to assign location.

Version-Release number of selected component (if applicable):
satellite-6.8.0-0.7.beta.el7sat.noarch

How reproducible:


Steps to Reproduce:
1. Create more then one location.
2. Assign location to the virt-who hypervisor.
3

Actual results:

Unregister host virt-who-astron-1.syslab.pnq2.redhat.com-3 before assigning an organization

Expected results:

We should be able to assign location.

Additional info:
Comment 1 Brad Buckingham 2020-08-12 13:49:17 UTC 
*** Bug 1868184 has been marked as a duplicate of this bug. ***
Comment 2 Brad Buckingham 2020-08-13 14:14:51 UTC 
Is this a regression from Satellite 6.7?
Comment 3 Varatharaja Perumal G 2020-08-14 16:48:46 UTC 
Hello Brad,

yes its Satellite 6.7 regression.
Comment 4 Jonathon Turel 2020-08-24 22:02:23 UTC 
Created redmine issue https://projects.theforeman.org/issues/30702 from this bug
Comment 5 Bryan Kearney 2020-08-28 00:01:09 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30702 has been resolved.
Comment 6 Brad Buckingham 2020-08-31 14:59:04 UTC 
*** Bug 1872592 has been marked as a duplicate of this bug. ***
Comment 11 errata-xmlrpc 2020-10-27 13:05:24 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 (Important: Satellite 6.8 release), 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-2020:4366
Comment 12 errata-xmlrpc 2020-10-27 13:08:26 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 (Important: Satellite 6.8 release), 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-2020:4366
Note You need to log in before you can comment on or make changes to this bug.