Bug 2047281

Summary:	[RFE] Use 'foreman-maintain self-upgrade' command for performing minor version upgrades of rubygem-foreman_maintain
Product:	Red Hat Satellite	Reporter:	Gaurav Talreja <gtalreja>
Component:	Foreman Maintain	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	NEW ---	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.11.0	CC:	apatel, aupadhye, ehelms, kgaikwad, mkalyat
Target Milestone:	Unspecified	Keywords:	FutureFeature, Reopened, Triaged, Upgrades
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-27 11:21:54 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:

Description Gaurav Talreja 2022-01-27 14:17:20 UTC

Description of problem:
foreman-maintain self-upgrade command added in BZ 2026415 for updating rubygem-foreman_maintain package from next major version repository, and to make this command more general for both major and minor version upgrades of rubygem-foreman_maintain package adding this feature request

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

How reproducible:
Always

Steps to Reproduce:
1. foreman-maintain self-upgrade --target-version x.y
2.

Actual results:
Bug 2036187 - self-upgrade fails with x.y should be greater than existing version x.y.z! 

Expected results:
If provide x.y version self-upgrade should pull the latest rubygem-foreman_maintain package from the same x.y repository 


Additional info:

Comment 3 Amit Upadhye 2022-05-27 11:21:54 UTC

Hello,

Users have option to update foreman-maintain packages using yum/dnf or using foreman-maintain packages cmd itself.
We should not merge to behaviors of major version upgrade and .z stream upgrade which can confuse users.

As per this I am closing this bugzilla.

Thank You!

Comment 4 Eric Helms 2023-07-28 13:56:49 UTC

*** Bug 2222952 has been marked as a duplicate of this bug. ***