Bug 1543920 - Do not show 6.2.z upgrade option if Satellite is already in latest 6.2.z
Summary: Do not show 6.2.z upgrade option if Satellite is already in latest 6.2.z
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.2.14
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: Anurag Patel
QA Contact: Nikhil Kathole
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-09 15:17 UTC by sthirugn@redhat.com
Modified: 2019-04-02 13:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-01 12:07:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 22550 0 None None None 2018-02-12 12:31:22 UTC

Description sthirugn@redhat.com 2018-02-09 15:17:29 UTC
Description of problem:
Do not show 6.2.z upgrade option if Satellite is already in latest 6.2.z

Version-Release number of selected component (if applicable):
rubygem-foreman_maintain-0.1.3-1.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. The current 6.2 version in prod is 6.2.14. I have my Satellite in this version.  When I run the upgrade tooling check, it still gives me an option to move to latest z-stream

# rpm -q satellite
satellite-6.2.14-4.0.el7sat.noarch

# foreman-maintain upgrade check
--target-version not specified
Possible target versions are:
6.2.z
6.3

Actual results:
As explained above

Expected results:
Do not show 6.2.z stream option if Satellite is already in latest 6.2.z

Additional info:

Comment 1 sthirugn@redhat.com 2018-02-09 15:46:07 UTC
In the irc chat with mmccune, I realized that not showing 6.2.z option here will not address two scenarios:
1. user started upgrade of 6.2.z but it failed during installer run.
2. emergency async errata which sometimes doesnt bump satellite rpm version.

If technically possible, we can do something like this:

Assuming current Satellite version in prod in 6.2.14:

# rpm -q satellite
satellite-6.2.14-4.0.el7sat.noarch

# foreman-maintain upgrade check
--target-version not specified
Possible target versions are:
6.2.z (current)
6.3

By this way atleast the user is informed that Satellite has current 6.2.z version but a forced upgrade can still be run here. We can also enforce the usage of --force if someone needs an upgrade of the same current version.

Comment 3 Swapnil Abnave 2018-02-12 12:31:19 UTC
Created redmine issue http://projects.theforeman.org/issues/22550 from this bug

Comment 4 Bryan Kearney 2019-02-28 19:39:52 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 5 Bryan Kearney 2019-04-01 12:07:04 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.

Comment 6 Bryan Kearney 2019-04-02 13:33:46 UTC
Wrond closure reason.


Note You need to log in before you can comment on or make changes to this bug.