Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.

Bug 1869176

Summary:	Add self upgrade foreman-maintain package support to list-versions sub command as well.
Product:	Red Hat Satellite	Reporter:	Jameer Pathan <jpathan>
Component:	Satellite Maintain	Assignee:	Jameer Pathan <jpathan>
Status:	CLOSED ERRATA	QA Contact:	Gaurav Talreja <gtalreja>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.8.0	CC:	apatel, gtalreja, kgaikwad, pcreech
Target Milestone:	6.8.0	Keywords:	Triaged, UserExperience
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-foreman_maintain-0.6.10	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 12:38:46 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 Jameer Pathan 2020-08-17 07:48:54 UTC

Description of problem:
foreman-maintain upgrade list-versions command doesn't check if update for foreman-maintain package is available or not.

Version-Release number of selected component (if applicable):
- Satellite 6.8.0 snap 11
- rubygem-foreman_maintain-0.6.8-1.el7sat.noarch

How reproducible:
- Always

Steps to Reproduce:
1. Run foreman-maintain upgrade list-versions

Actual results:
- It doesn't check if update for foreman-maintain package is available or not like run/check subcommands.

Expected results:
- 'foreman-maintain upgrade list-versions' should check if update for foreman-maintain package is available or not.

Additional info:

Comment 2 Bryan Kearney 2020-08-28 12:05:24 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30649 has been resolved.

Comment 3 Patrick Creech 2020-09-01 20:14:22 UTC

Hello,

Can we get a 0.6.z upstream release of foreman_maintain with this fix in it?

Thanks,
Patrick

Comment 4 Jameer Pathan 2020-09-07 07:23:49 UTC

Hi Patrick,

We will have fix for this in upcoming snap. (In foreman-maintain v0.6.10)

Comment 5 Gaurav Talreja 2020-09-16 08:45:36 UTC

Verified.

Version Tested:  Satellite-6.8.0 Snap 15 and rubygem-foreman_maintain-0.6.10
Steps followed: 
foreman-maintain upgrade list-versions   
foreman-maintain upgrade list-versions --disable-self-upgrade

Observation:
Here list-version sub-command is checking if update for foreman-maintain package is available or not, and if exists it will auto-upgrade the same to latest version
With  --disable-self-upgrade it won’t auto-grade and will retain the package with existing package version.
Note: feature was tested against upstream foreman-maintain v0.6.10 tag

Comment 8 errata-xmlrpc 2020-10-27 12:38:46 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 (Satellite 6.8 Satellite Maintenance 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/RHBA-2020:4365