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:
whenever we refresh a manifest, a POST and PUT requests are made to the upstream candlepin with an invalid satellite version format in facts.
Sadly, upstream candlepin accepts the version but this causes issues down the road (missing SCA attribute in the RHSM api response, etc. )
The request looks like this:
```
2023-02-08T12:11:01 [debug|kat|8ec0c781] Sending POST request to upstream Candlepin: https://subscription.rhsm.redhat.com/subscription/consumers/<redacted uuid> {"capabilities":[{"name":"instance_multiplier"},{"name":"derived_product"},{"name":"vcpu"},{"name":"cert_v3"},{"name":"hypervisors_heartbeat"},{"name":"remove_by_pool_id"},{"name":"syspurpose"},{"name":"storage_band"},{"name":"cores"},{"name":"multi_environment"},{"name":"hypervisors_async"},{"name":"org_level_content_access"},{"name":"guest_limit"},{"name":"ram"},{"name":"batch_bind"}],"facts":{"distributor_version":"sat-6"}}
```
Note, that the valid values for the `distributor_version` according RHSM api are "sat-6.<y>" with `6.12` currently being the latest.
Version-Release number of selected component (if applicable):
6.13.0-snap8 but this has been occurring in 6.12 as well
How reproducible:
always on manifest refresh triggered from satellite
Steps to Reproduce:
1. create a subscription allocation on access.redhat.com
2. choose an appropriate version of satellite
3. download the manifest and upload it to the satellite organization
4. navigate to subscriptions->manage manifest and hit "Refresh"
5. after the refresh is finished, check the subscription allocation details on access.redhat.com
6. the Satellite version is now "Satellite 6"
Actual results:
Satellite version of the allocation is set to invalid value on access.redhat.com
Expected results:
satellite version stays untouched
Additional info:
Comment 4Nikos Moumoulidis
2023-03-22 13:36:04 UTC
*** Bug 2178845 has been marked as a duplicate of this bug. ***
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.13 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-2023:2097