-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
subs-client-tools
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
Goal
- A subscription-manager user can expect the package profile to include package persistence information.
Acceptance criteria
A list of verification conditions, successful functional tests, or expected outcomes in order to declare this story/task successfully completed.
- subscription-manager is able to take package persistence information from libdnf via https://issues.redhat.com/browse/RHEL-104149 and send it in the package profile.
Context:
With https://issues.redhat.com/browse/SAT-30671 , Satellite will be required to track which packages on an image mode host are installed transiently.
"Transient" is one of the new dnf persistence options that goes along with the --transient flag, which enables installing RPMs are image mode machines without first enabling the bootc usr-overlay.
This RFE requests that the persistence be added to the subscription-manager package profile. For example:
# Edited portion of a cached package profile { "rpm": [ { "name": "subscription-manager-rhsm-certificates", "version": "20220623", "release": "1.el9", "arch": "noarch", "epoch": 0, "vendor": "Red Hat, Inc.", "persistence": "transient" <=========== }, { "name": "hwdata", "version": "0.348", "release": "9.15.el9", "arch": "noarch", "epoch": 0, "vendor": "Red Hat, Inc.", "persistence": "transient" <=========== },
Data from subscription-manager is the best source of truth for Satellite. Otherwise, package persistence would need to be inferred.
- is blocked by
-
RHEL-104149 As a dnf library user, I can programatically determine if a package is transient or persistent
-
- Planning
-