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 1571859

Summary: Handle satellite 6.3 with puppet 3 upgrade to satellite 6.4
Product: Red Hat Satellite Reporter: Nikhil Kathole <nkathole>
Component: Satellite MaintainAssignee: Kavita <kgaikwad>
Status: CLOSED ERRATA QA Contact: Nikhil Kathole <nkathole>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.3.1CC: apatel, inecas, jspinks, kgaikwad, kmishra, mjia, mlele, mmccune, pcreech, swadeley
Target Milestone: 6.4.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman_maintain-0.2.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 15:16:57 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, 1619394    

Description Nikhil Kathole 2018-04-25 14:33:41 UTC
Description of problem: We need some more checks and modifications regarding puppet. As satellite 6.3. puppet3 -> sat6.4 update failed due to dependency

--> Finished Dependency Resolution
Error: Package: puppet-server-3.8.6-4.el7sat.noarch (@rhel-7-server-satellite-6.3-rpms)
           Requires: puppet = 3.8.6-4.el7sat
           Removing: puppet-3.8.6-4.el7sat.noarch (@rhel-7-server-satellite-6.3-rpms)
               puppet = 3.8.6-4.el7sat
           Obsoleted By: puppet-agent-5.5.0-1.el7sat.x86_64 (sat6)
               puppet >= 4.0.0-1.el7sat

and upgrade path will be sat 63 with puppet4 -> sat64. So possible twicks can be if 6.3 with puppet3, raise warning (do not allow ) upgrade to 6.4 or add support to f-m to update sat 63 to puppet4.


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


How reproducible:always


Steps to Reproduce:
1. Install 6.3 with puppet 3
2. yum update

Actual results: 

--> Finished Dependency Resolution
Error: Package: puppet-server-3.8.6-4.el7sat.noarch (@rhel-7-server-satellite-6.3-rpms)
           Requires: puppet = 3.8.6-4.el7sat
           Removing: puppet-3.8.6-4.el7sat.noarch (@rhel-7-server-satellite-6.3-rpms)
               puppet = 3.8.6-4.el7sat
           Obsoleted By: puppet-agent-5.5.0-1.el7sat.x86_64 (sat6)
               puppet >= 4.0.0-1.el7sat


Expected results:


Additional info:

Comment 2 Ivan Necas 2018-04-25 14:44:03 UTC
Since the upgrade of puppet can be quite complex (depending on how much of Puppet is used in the infrastucture). Therefore, I would like to keep the scope of this BZ to check the puppet3 presence in pre-upgrade for 6.4 and pointing the user to proceed with https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html/upgrading_and_updating_red_hat_satellite/upgrading_puppet-1 before continuing.

Comment 3 Mike McCune 2018-06-05 15:32:02 UTC
+1 to Ivan's comment above, error out with a pointer to the docs

Comment 4 Ivan Necas 2018-06-05 15:32:49 UTC
Created redmine issue http://projects.theforeman.org/issues/23819 from this bug

Comment 5 Ivan Necas 2018-06-06 13:49:42 UTC
*** Bug 1585792 has been marked as a duplicate of this bug. ***

Comment 6 Satellite Program 2018-06-08 12:18:38 UTC
Upstream bug assigned to apatel

Comment 7 Satellite Program 2018-06-11 10:17:40 UTC
Upstream bug assigned to kgaikwad

Comment 8 Satellite Program 2018-06-22 08:21:17 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23819 has been resolved.

Comment 10 Nikhil Kathole 2018-07-31 12:25:58 UTC
FailedQA

Version tested:
# rpm -qa | grep maintain
rubygem-foreman_maintain-0.2.4-1.el7sat.noarch

Comment 14 Nikhil Kathole 2018-08-07 12:43:54 UTC
VERIFIED

Version tested:
# rpm -qa | grep maintain
rubygem-foreman_maintain-0.2.6-1.el7sat.noarch

On satellite 6.3 with puppet 3,

--------------------------------------------------------------------------------
Verify puppet and provide upgrade guide for it: 
\ current puppet version: puppet-3.8.6-4.el7sat.noarch                [FAIL]    
Before continuing with upgrade, please make sure you finish puppet upgrade.
--------------------------------------------------------------------------------
Continue with step [Show knowledge base article for troubleshooting]?, [y(yes), n(no), q(quit)] y
Show knowledge base article for troubleshooting:                                
Go to https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html/upgrading_and_updating_red_hat_satellite/upgrading_puppet-1
please follow steps from above article to resolve this issue
press ENTER once done.

                                                                      [OK]
--------------------------------------------------------------------------------

On satellite 6.3 with puppet 4,

--------------------------------------------------------------------------------
Verify puppet and provide upgrade guide for it: 
- current puppet version:                                             [OK]      
--------------------------------------------------------------------------------

Check available only on sat 6.3.For sat 6.4 check doesn't exist.

Comment 15 Mihir Lele 2018-09-07 16:33:16 UTC
*** Bug 1626531 has been marked as a duplicate of this bug. ***

Comment 17 Ivan Necas 2018-09-25 07:29:55 UTC
*** Bug 1632083 has been marked as a duplicate of this bug. ***

Comment 21 errata-xmlrpc 2018-10-16 15:16:57 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-2018:2926