Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
DescriptionJaskaran Singh Narula
2021-07-05 16:08:08 UTC
Description of problem:
During leapp pre-upgrade satellite-related repository is unknown to leapp.
i.e
rhel-7-server-satellite-tools-6.9-rpms
rhel-server-rhscl-7-rpms
Version-Release number of selected component (if applicable):
RHEL 7.9
How reproducible:
100%
Steps to Reproduce:
1. Make a fresh RHEL 7.9 system.
2. Register it with the Satellite server and enable basic repositories.
3. Enable the below-mentioned repositories.
[1] rhel-7-server-satellite-tools-6.9-rpms
[2] rhel-server-rhscl-7-rpms
Actual results:
Based on packages that are installed and coming from these repositories the following message appears in /var/log/leapp/leapp-report.txt
~~~
Title: Some enabled RPM repositories are unknown to Leapp
Summary: The following repositories with Red Hat-signed packages are unknown to Leapp:
- rhel-7-server-satellite-tools-6.9-rpms
- rhel-server-rhscl-7-rpms
And the following packages installed from those repositories may not be upgraded:
...
...{Package List}
...
Remediation: [hint] You can file a request to add this repository to the scope of in-place upgrades by filing a support ticket
Key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
~~~
Expected results:
If these repositories are enabled then it should not appear in the report.
Additional info:
I expected to for the RedHat promoted Satellite products also all client tools (e.g. puppet-agent) are updated.
Currently after the leapp upgrade and using the correct sat6-tools-el8 repo there is still a el7sat rpm installed.
This is easily spotted with doing a 'rpm -qa | grep el7'
I expected that RedHat has already identified this missed upgrade and include them in the el7->el8 process.
In case of puppet-agent it is a version number inconsistency and I have created already a dedicated case for the Satellite product for this
Comment 4RHEL Program Management
2023-09-12 11:05:18 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5RHEL Program Management
2023-09-12 11:10:20 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 "RHEL-" 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.
Description of problem: During leapp pre-upgrade satellite-related repository is unknown to leapp. i.e rhel-7-server-satellite-tools-6.9-rpms rhel-server-rhscl-7-rpms Version-Release number of selected component (if applicable): RHEL 7.9 How reproducible: 100% Steps to Reproduce: 1. Make a fresh RHEL 7.9 system. 2. Register it with the Satellite server and enable basic repositories. 3. Enable the below-mentioned repositories. [1] rhel-7-server-satellite-tools-6.9-rpms [2] rhel-server-rhscl-7-rpms Actual results: Based on packages that are installed and coming from these repositories the following message appears in /var/log/leapp/leapp-report.txt ~~~ Title: Some enabled RPM repositories are unknown to Leapp Summary: The following repositories with Red Hat-signed packages are unknown to Leapp: - rhel-7-server-satellite-tools-6.9-rpms - rhel-server-rhscl-7-rpms And the following packages installed from those repositories may not be upgraded: ... ...{Package List} ... Remediation: [hint] You can file a request to add this repository to the scope of in-place upgrades by filing a support ticket Key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ~~~ Expected results: If these repositories are enabled then it should not appear in the report. Additional info: