Bug 1585792 - Installer Should error out if Puppet has not been upgraded to Puppet 4
Summary: Installer Should error out if Puppet has not been upgraded to Puppet 4
Keywords:
Status: CLOSED DUPLICATE of bug 1571859
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Upgrades
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-04 18:43 UTC by John Spinks
Modified: 2018-06-06 13:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-06 13:49:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description John Spinks 2018-06-04 18:43:19 UTC
Description of problem:

Satellite 6.4 will ONLY support Puppet 5.
A pre-requisite for upgrading is that the Satellite environment is using Satellite 6.3 and Puppet 4.
If the version of Puppet on Satellite 6.3 is anything other than Puppet 4, the installer should provide an error during an attempted upgrade.

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

Satellite 6.3 & Puppet 3.8 - Should provide an error condition
Satellite 6.3 & Puppet 4 - Should continue upgrade process.


Expected results:

If Satellite 6.3 and Puppet 3.8 is used, then the expectation is an attempted install to Satellite 6.4 should produce a clear error that indicates that an upgrade to Puppet 4 is required.

If Satellite 6.3 and Puppet 4 is used, then the expectation is that an attempted install will be successful.

Comment 2 Ivan Necas 2018-06-06 13:49:42 UTC
I'm marking this a a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1571859. Feel free to reopen if you believe that this bz aims to solve something else than the one mentioned.

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


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