Bug 1535466

Summary: [RFE] foreman-maintain support for Capsules
Product: Red Hat Satellite Reporter: Stephen Wadeley <swadeley>
Component: Satellite MaintainAssignee: Amit Upadhye <aupadhye>
Status: CLOSED ERRATA QA Contact: Vladimír Sedmík <vsedmik>
Severity: high Docs Contact:
Priority: high    
Version: 6.3.0CC: ahumbe, apatel, aupadhye, aymeric.marchal, bkearney, egolov, inecas, kgaikwad, mawerner, mmccune, mvanderw, spetrosi, ssainkar, sthirugn, supatil, vijsingh
Target Milestone: 6.8.0Keywords: FutureFeature, PrioBumpGSS, Triaged, UserExperience
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rubygem-foreman_maintain-0.6.2 Doc Type: Enhancement
Doc Text:
You can now upgrade and update Capsules using satellite-maintain. Refer to the documentation for more details at https://access.redhat.com/documentation/en-us/red_hat_satellite/6.8/html/upgrading_and_updating_red_hat_satellite/upgrading_red_hat_satellite#upgrading_capsule_server[Upgrading Capsule Servers] and https://access.redhat.com/documentation/en-us/red_hat_satellite/6.8-beta/html/upgrading_and_updating_red_hat_satellite/updating_satellite_server_capsule_server_and_content_hosts#updating_capsule_server_to_next_minor_version[Updating Capsule Server to the Next Minor Version]. + The package lock feature that was added in Satellite 6.7 to Satellite Server is enabled on Capsule Servers by default too.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 12:38:20 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:    
Bug Blocks: 1496794, 1817364    

Description Stephen Wadeley 2018-01-17 12:49:50 UTC
Description of problem:

Please add support for upgrading and updating Capsules using Foreman maintain.

Thank you

Comment 1 Steve Bream 2018-02-06 14:03:59 UTC
(In reply to Stephen Wadeley from comment #0)
> Description of problem:
> 
> Please add support for upgrading and updating Capsules using Foreman
> maintain.
> 
> Thank you

Per Mike McCune, foremain-maintain will not work with capsules in Satellite 6.3, so I think we can close this bz.

Thanks, 
Steve

Comment 2 Stephen Wadeley 2018-02-06 14:19:10 UTC
(In reply to Steve Bream from comment #1)
> (In reply to Stephen Wadeley from comment #0)
> > Description of problem:
> > 
> > Please add support for upgrading and updating Capsules using Foreman
> > maintain.
> > 
> > Thank you
> 
> Per Mike McCune, foremain-maintain will not work with capsules in Satellite
> 6.3, so I think we can close this bz.
> 
> Thanks, 
> Steve

Dear Steve

Noooo, this not a docs bug, this is an engineering bug, it shoud stay open till its fixed :)

Thank you

Comment 3 Stephen Wadeley 2018-05-19 08:57:17 UTC
https://github.com/RedHatSatellite/capsule-maintain

Comment 5 Aymeric Marchal SG 2019-01-07 10:18:02 UTC
Hello Stephen,
Happy new year !

There is no way to automatize capsule upgrade today. It is a main subject of support of the product when you have a very numberous capsules. The customer concerned number should be bigger and bigger because the subscription has changed but it is complicated and very tedious to support it manually. And to be precisely, this is to add the possibility to launch a playbook ansible that plays the update.

Aymeric

Comment 6 Aymeric Marchal SG 2019-01-07 10:21:07 UTC
The customer concerned number  -> 
the number of users involved

Comment 7 Stephen Wadeley 2019-01-07 10:35:01 UTC
Hello Aymeric

Happy new year to you too.

I raised this bug, when I worked in SatDocs, to get this issue addressed. The bug is currently assigned to Anurag (Happy new year Anurag).

If you have not already done so, please raise a support case and reference this bugzilla; it will help to increase its priority (which is already quite high).

Thank you

Comment 8 Aymeric Marchal SG 2019-01-07 10:44:48 UTC
Hello everyone,

Now, i have no need about Red Hat Satellite 6.3. 
On the other hand, the need is about Red Hat Satellite 6.4 (the latest version and the futur releases).

We did it manually, but the numbers of capsule is still manageable.

Yes this bugzilla object number comes from a Red Hat open case.


Regards,
Aymeric

Comment 9 Stephen Wadeley 2019-07-02 07:26:31 UTC
Hello

I see foreman-maintain already in since 6.4!


[root@rhel7-6-capsule ~]# rpm -q satellite-capsule
satellite-capsule-6.4.1-1.el7sat.noarch

[root@rhel7-6-capsule ~]# foreman-maintain -h
Usage:
    foreman-maintain [OPTIONS] SUBCOMMAND [ARG] ...

How did we miss it?

Comment 10 Kavita 2019-07-02 07:47:09 UTC
Hello Stephen,

Right now, there is no any upgrade scenario present for capsule in foreman-maintain.

Comment 11 Stephen Wadeley 2019-07-02 09:03:15 UTC
(In reply to Kavita from comment #10)
> Hello Stephen,
> 
> Right now, there is no any upgrade scenario present for capsule in
> foreman-maintain.

thank you for that info.

So I should ask for the help output to *not* offer upgrade option when run on Capsule as that is confusing.

~]# foreman-maintain -h
Usage:
    foreman-maintain [OPTIONS] SUBCOMMAND [ARG] ...

Parameters:
    SUBCOMMAND                    subcommand
    [ARG] ...                     subcommand arguments

Subcommands:
    health                        Health related commands
    upgrade                       Upgrade related commands   <-- Misleading
<snip>

Comment 12 Stephen Wadeley 2019-07-17 12:01:07 UTC
Re comment 11

Bug 1730703 - foreman-maintain on Capsule should not show upgrade option

Comment 14 Anurag Patel 2019-12-09 16:28:58 UTC
We're planning to align Capsule upgrade support with version locking for 6.8.0.

Comment 15 Bryan Kearney 2020-03-26 08:03:30 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28089 has been resolved.

Comment 16 Vladimír Sedmík 2020-08-21 18:06:21 UTC
Tested as a new 6.8 feature.

Comment 20 errata-xmlrpc 2020-10-27 12:38:20 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