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 1626531

Summary: [RFE] Foreman-maintain should have a puppet version pre-check
Product: Red Hat Satellite Reporter: Mihir Lele <mlele>
Component: Satellite MaintainAssignee: Anurag Patel <apatel>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.4CC: apatel, inecas, kgaikwad, mbacovsk, mlele, nkathole
Target Milestone: UnspecifiedKeywords: FutureFeature
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-07 16:33:16 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: 1619394    

Description Mihir Lele 2018-09-07 14:54:39 UTC
Description of problem:

Foreman-maintain should have a puppet version pre-check that checks whether the Satellite 6.3 or Capsule 6.3 has puppet 3 or puppet 4 before allowing users to attempt upgrade to satellite 6.4/capsule 6.4, and should prohibit upgradation if found that the customer satellite is still installed with puppet 3.


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

Comment 1 Nikhil Kathole 2018-09-07 15:21:23 UTC
shouldn't the bugzilla[1] work for you? 

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]      
--------------------------------------------------------------------------------

This is already there in beta maintain version.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1571859

Comment 2 Mihir Lele 2018-09-07 16:31:38 UTC
yes that looks similar. Got for marking this bug as duplicate.

--Mihir

Comment 3 Mihir Lele 2018-09-07 16:31:56 UTC
good*

Comment 4 Mihir Lele 2018-09-07 16:33:16 UTC

*** This bug has been marked as a duplicate of bug 1571859 ***