Bug #30204
closedforeman-maintain enables rhel-7-server-satellite-tools-6.8-beta-rpms repo instead of rhel-7-server-satellite-tools-6-beta-rpms for beta scenario.
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1849941
Description of problem:
foreman-maintain enables rhel-7-server-satellite-tools-6.8-beta-rpms repo instead of rhel-7-server-satellite-tools-6-beta-rpms for beta scenario.
Version-Release number of selected component (if applicable):
- Satellite 6.8.0 snap 5
- rubygem-foreman_maintain-0.6.5-1
How reproducible:
- Always
Steps to Reproduce:
1.export FOREMAN_MAINTAIN_USE_BETA=1
2.foreman-maintain advanced procedure run repositories-setup --version 6.8
Actual results:
Error: 'rhel-7-server-satellite-tools-6.8-beta-rpms' does not match a valid repository ID. Use "subscription-manager repos --list" to see valid repositories.
Expected results:
- All required beta repositories gets enabled. i.e rhel-server-7-satellite-6-beta-rpms, rhel-7-server-ansible-2.8-rpms, rhel-7-server-satellite-maintenance-6-beta-rpm, rhel-server-rhscl-7-rpms, rhel-7-server-rpms, rhel-7-server-satellite-tools-6-beta-rpms.
Additional info:
Updated by Suraj Patil almost 4 years ago
- Assignee changed from Anurag Patel to Suraj Patil
Updated by The Foreman Bot almost 4 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman_maintain/pull/361 added
Updated by Anonymous almost 4 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_maintain|d6b4a818b3eca1d14c36a4b8392c1a7a994241c1.