Bug 2026415

Summary: RFE: Add command for upgrading foreman-maintain to next major version
Product: Red Hat Satellite Reporter: Amit Upadhye <aupadhye>
Component: Foreman MaintainAssignee: Amit Upadhye <aupadhye>
Status: CLOSED ERRATA QA Contact: Gaurav Talreja <gtalreja>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.11.0CC: apatel, kgaikwad, pcreech, pmendezh
Target Milestone: 6.11.0Keywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-foreman_maintain-0.9.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-05 14:30:29 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: 2036184, 2036187, 2060396, 2072530, 2078828, 2080909    
Bug Blocks:    

Description Amit Upadhye 2021-11-24 15:39:51 UTC
Description of problem:

The foreman-maintain should provide a command to do self upgrade from next version maintenance repository. This is to support shipping foreman-maintain in version specific maintenance repository and provide a way to grab next version's upgrade bits. 

Version-Release number of selected component (if applicable):

7.0

Comment 3 Gaurav Talreja 2022-05-25 20:15:58 UTC
Verified.

Tested on Satellite 6.11.0 Snap 21.0
Version: rubygem-foreman_maintain-1.0.10-1.el7sat.noarch

Steps:
1. # foreman-maintain self-upgrade --help

Observation, 
As part of foreman-maintain, a new sub-command "self-upgrade" is provided to upgrade "rubygem-foreman_maintain and satellite-maintain" packages from the next major version-specific maintenance repository, which is to support shipping foreman-maintain in the version-specific maintenance repository and provide a way to acquire the next version's upgrade bits.
Check usage here - https://bugzilla.redhat.com/show_bug.cgi?id=2072530#c3

Comment 6 errata-xmlrpc 2022-07-05 14:30:29 UTC
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 (Moderate: Satellite 6.11 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-2022:5498