• Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Puppet, Satellite Maintain
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • 0
    • Rocket

      Description of problem:

      "satellite-maintain plugin purge-puppet" commands fails mentioning disable Puppet from Satellite along external capsule/proxy first

      How reproducible:

       

      Is this issue a regression from an earlier version:

      Yes, regression in Satellite 6.17 snap 1.1 from stream snap 89

      Steps to Reproduce:

      1. Setup Satellite 6.17 with Capsule and Puppet enabled on both

      2.

      # satellite-maintain plugin purge-puppet
      Running Remove Puppet feature
      ================================================================================
      Check for Puppet capsules from the database:
      You have proxies with Puppet feature enabled, please disable Puppet on all proxies first.
      The following proxies have Puppet feature: <satellite-fqdn>, <capsule-fqdn>.                                                                      [ABORTED]
      --------------------------------------------------------------------------------
      Scenario [Remove Puppet feature] failed.The processing was aborted by user during the following steps:  [puppet-capsules]
       

      Actual behavior:

      "satellite-maintain plugin purge-puppet" commands fails mentioning disable Puppet from Satellite along external capsule/proxy first

      Expected behavior:

      "satellite-maintain plugin purge-puppet" commands should fail only with mentioning disable Puppet on external capsule/proxy first

      Business Impact / Additional info:

       

      QE Tracker for https://issues.redhat.com/browse/SAT-31338

              rhn-support-shwsingh Shweta Singh
              satellite-jira-automation@redhat.com Satellite Jira-Automation
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: