Bug 2008015

Summary:	RHEL 6 Host always getting registered under default location using new Satellite Server Token Registration Steps.
Product:	Red Hat Satellite	Reporter:	Surjeet Salvi <susalvi>
Component:	Registration	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Stephen Wadeley <swadeley>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.9.0	CC:	lstejska
Target Milestone:	6.10.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-16 14:13:51 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:
Embargoed:

Description Surjeet Salvi 2021-09-27 01:09:24 UTC

Description of problem:
- RHEL 6 Host getting registered under default location using new Satellite Server Token Registration Steps even if specific location id is mentioned in curl command

Version-Release number of selected component (if applicable):
- Red Hat Satellite Server 6.9

How reproducible:
- Create Token from Satellite WEBUI for a specific location and try to register RHEL 6 Host


Actual results:
- Even if a specific location ID is mentioned host is getting registered under the default location.


Expected results:
- Host should get registered under the given location. 


Additional info:
- No issue using the bootstrap script while registering the host under a specific location 
- No issue with RHEL 7 and RHEL 8 host.

Comment 7 Leos Stejskal 2021-10-05 11:24:36 UTC

Hi,
there have been some discussions about "Unknown subscription status" [0][1],
we still don't know why it is happening, I would suggest to create new BZ for it.

[0] https://community.theforeman.org/t/katello-4-2-0-rc1-1-registering-a-centos-8-content-host-results-in-build-pending-status-unkown-subscription/25293/12
[1] https://community.theforeman.org/t/simple-content-access-for-centos-repos/25369/3

Comment 8 Stephen Wadeley 2021-10-05 16:03:35 UTC

(In reply to Leos Stejskal from comment #7)
> Hi,
> there have been some discussions about "Unknown subscription status" [0][1],
> we still don't know why it is happening, I would suggest to create new BZ
> for it.
> 
> [0]
> https://community.theforeman.org/t/katello-4-2-0-rc1-1-registering-a-centos-
> 8-content-host-results-in-build-pending-status-unkown-subscription/25293/12
> [1]
> https://community.theforeman.org/t/simple-content-access-for-centos-repos/
> 25369/3

Hi Leos

I have this one already:

Bug 1999792 - Unknown subscription status on Satellite webui after successful host registration.

Comment 9 Stephen Wadeley 2021-10-07 14:00:03 UTC

Hi 

As "Unknown subscription status" issue is unrelated to this bug, seems its Insights config related and is being investigated as part of [1], I will set this to VERIFIED.


Thank you


[1] 
Bug 1999792 - Unknown subscription status on Satellite webui after successful host registration.

Comment 12 errata-xmlrpc 2021-11-16 14:13:51 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 (Moderate: Satellite 6.10 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-2021:4702