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 2160528

Summary: foreman-installer and foreman-installer-katello have failing post scriptlets
Product: Red Hat Satellite Reporter: Lukas Pramuk <lpramuk>
Component: PackagingAssignee: Eric Helms <ehelms>
Status: CLOSED ERRATA QA Contact: Lukas Pramuk <lpramuk>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.13.0CC: ehelms, pcreech
Target Milestone: 6.13.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-installer-3.5.1-2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-03 13:24:33 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:

Description Lukas Pramuk 2023-01-12 17:44:34 UTC 
Description of problem:
this issue is really anoying as it is introduced with every new downstream release.
scriptlets use upstream installer scenario names 

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

How reproducible:
deterministic

Steps to Reproduce:
1. # yum upgrade or # yum install satellite
...

  Upgrading        : foreman-installer-1:3.5.1-1.el8sat.noarch                          67/483 
warning: /etc/foreman-installer/custom-hiera.yaml created as /etc/foreman-installer/custom-hiera.yaml.rpmnew
warning: /etc/foreman-installer/scenarios.d/foreman-answers.yaml created as /etc/foreman-installer/scenarios.d/foreman-answers.yaml.rpmnew

  Running scriptlet: foreman-installer-1:3.5.1-1.el8sat.noarch                          67/483 
ERROR: Selected scenario is DISABLED, can not continue.
       Use --list-scenarios to list available options.
       You can also --enable-scenario SCENARIO to make the selected scenario available.
warning: %post(foreman-installer-1:3.5.1-1.el8sat.noarch) scriptlet failed, exit status 27

Error in POSTIN scriptlet in rpm package foreman-installer
  Upgrading        : foreman-installer-katello-1:3.5.1-1.el8sat.noarch                  68/483 
warning: /etc/foreman-installer/scenarios.d/foreman-proxy-content-answers.yaml created as /etc/foreman-installer/scenarios.d/foreman-proxy-content-answers.yaml.rpmnew
warning: /etc/foreman-installer/scenarios.d/foreman-proxy-content.yaml created as /etc/foreman-installer/scenarios.d/foreman-proxy-content.yaml.rpmnew
warning: /etc/foreman-installer/scenarios.d/katello-answers.yaml created as /etc/foreman-installer/scenarios.d/katello-answers.yaml.rpmnew
warning: /etc/foreman-installer/scenarios.d/katello.yaml created as /etc/foreman-installer/scenarios.d/katello.yaml.rpmnew

  Running scriptlet: foreman-installer-katello-1:3.5.1-1.el8sat.noarch                  68/483 
ERROR: Selected scenario is DISABLED, can not continue.
       Use --list-scenarios to list available options.
       You can also --enable-scenario SCENARIO to make the selected scenario available.
ERROR: Selected scenario is DISABLED, can not continue.
       Use --list-scenarios to list available options.
       You can also --enable-scenario SCENARIO to make the selected scenario available.
warning: %post(foreman-installer-katello-1:3.5.1-1.el8sat.noarch) scriptlet failed, exit status 27

Error in POSTIN scriptlet in rpm package foreman-installer-katello


Actual results:
errors/warnings shown during rpm install

Expected results:
no errors/warnings

Additional info:

# rpm -q --scripts foreman-installer
postinstall scriptlet (using /bin/sh):
foreman-installer --scenario foreman --migrations-only > /dev/null

# rpm -q --scripts foreman-installer-katello
postinstall scriptlet (using /bin/sh):
foreman-installer --scenario foreman-proxy-content --migrations-only > /dev/null
foreman-installer --scenario katello --migrations-only > /dev/null
Comment 1 Lukas Pramuk 2023-03-21 12:14:18 UTC 
VERIFIED.

@Satellite 6.13.0 Snap15
foreman-installer-3.5.2.1-1.el8sat.noarch
foreman-installer-katello-3.5.2.1-1.el8sat.noarch

by the following steps:

# yum install satellite
...
  Installing       : foreman-installer-1:3.5.2.1-1.el8sat.noarch                136/434 
  Installing       : rubygem-locale-2.1.3-1.el8sat.noarch                       137/434 
...
  Installing       : foreman-installer-katello-1:3.5.2.1-1.el8sat.noarch        430/434 
  Installing       : katello-4.7.0-1.el8sat.noarch                              431/434 

>>> there are no scriptlets warnings 

# rpm -q --scripts foreman-installer foreman-installer-katello
<empty>

>>> no problematic scriptlets present for the two rpms
Comment 4 errata-xmlrpc 2023-05-03 13:24:33 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 (Important: Satellite 6.13 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/RHSA-2023:2097