Bug 2280181

Summary:	[Regression]Satellite is not updating subscription status of the registered hosts
Product:	Red Hat Satellite	Reporter:	Hao Chang Yu <hyu>
Component:	Candlepin	Assignee:	Barnaby Court <bcourt>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.14.4	CC:	paji, rlavi, sbakaj
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	candlepin-4.4.5-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2282411 (view as bug list)		Environment:
Last Closed:	2024-06-06 17:38:45 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:
Bug Depends On:	2282411
Bug Blocks:

Description Hao Chang Yu 2024-05-13 01:47:54 UTC

Description of problem:
Satellite is still showing the registered hosts as "unentitled" even the hosts have valid subscriptions attached.


How reproducible:
Easy

Steps to Reproduce:
1. Disable SCA on the Satellite.
2. Register a host without using activation key. Simply run "subscription-manager register" command.
3. The host should have registered to the Satellite and Web UI is showing "unentitled" status.
4. Attach a valid subscription to the host manually or use "subscription-manager attach --auto" command
5. Run the "subscription-manager status" command. The status should be "Valid" or "Insufficient" (temporary subscription if no virt-who is reported)

Actual results:
Web UI still showing the host status as "Unentitled" even the client is subscribed with valid subscriptions or partially subscribed.

Expected results:
Web UI should update the host status


Additional info:
It is because Candlepin sent an event message with empty event data (see below) so Satellite skipped the subscription status update.
~~~
principalType=trusteduser principal=foreman_admin target=COMPLIANCE entityId=xxxxxx-xxxx-xxxx-xxxx-xxxxxxxx type=CREATED owner=xxxxxxxxxxxxxxxxxxxxxx eventData=null
~~~


This is a known bug which has been fixed in candlepin-4.4.5-1. 
~~~
https://issues.redhat.com/browse/CANDLEPIN-786
https://github.com/candlepin/candlepin/pull/4532
~~~

Comment 1 Partha Aji 2024-05-17 18:49:50 UTC

A hotfix RPM is available for this BZ for Satellite 6.14.4 on RHEL 8

The Hotfix RPMs are too large to be provided as a Bugzilla attachment. Please open a case with Red Hat Technical Support to request them.

INSTALL INSTRUCTIONS:

1. Take a complete backup or snapshot of Satellite 6.14.4 server

2. Obtain the Hotfix RPM for Satellite 6.14.4 on RHEL 8 from Red Hat Technical Support and copy it to Satellite server

3. # dnf install ./candlepin-4.3.13-2.HOTFIXRHBZ2280181.el8sat.noarch.rpm --disableplugin=foreman-protector

4. # satellite-maintain service restart

Comment 3 Eric Helms 2024-06-06 17:38:45 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.