Bug 1640051

Summary: Add target version satellite 6.5 in foreman-maintain
Product: Red Hat Satellite Reporter: Nikhil Kathole <nkathole>
Component: Satellite MaintainAssignee: Ivan Necas <inecas>
Status: CLOSED ERRATA QA Contact: Nikhil Kathole <nkathole>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.5.0CC: apatel, aupadhye, egolov, inecas, kgaikwad, mbacovsk
Target Milestone: ReleasedKeywords: PrioBumpQA, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-foreman_maintain-0.3.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-14 12:28:21 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 Nikhil Kathole 2018-10-17 08:58:12 UTC 
Description of problem: We will be having sat 6.5 soon. Lets add support for upgrading sat 64 to sat65.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Kavita 2018-10-29 08:52:35 UTC 
Created redmine issue http://projects.theforeman.org/issues/25329 from this bug
Comment 3 Satellite Program 2018-11-07 19:06:33 UTC 
Upstream bug assigned to inecas
Comment 4 Satellite Program 2018-11-07 19:06:37 UTC 
Upstream bug assigned to inecas
Comment 5 Satellite Program 2018-11-08 15:06:27 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25329 has been resolved.
Comment 7 Nikhil Kathole 2018-11-13 12:06:44 UTC 
VERIFIED

Version tested:

# rpm -qa | grep maintain
rubygem-foreman_maintain-0.3.0-1.el7sat.noarch

sat 6.5 snap 3

foreman-maintain now has 6.5 and 6.5.z target versions.
Comment 12 errata-xmlrpc 2019-05-14 12:28:21 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, 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-2019:1221