Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-17120

6.11 rubygem-foreman_rh_cloud uses a 6.12 posttrans macro

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 6.11.z
    • 6.11.5
    • None
    • Important
    • None

      Description of problem:
      The 6.11 rubygem-foreman_rh_cloud plugin includes the following posttrans macro:

      posttrans scriptlet (using /bin/sh):
      %

      {foreman_plugin_log}

      That macro was not introduced until the 6.12 foreman-3.3.0.* package.

      As a result, a failure is encountered during an installation or update with the following in the logs:

      2023-04-10T13:13:39+0000 INFO /var/tmp/rpm-tmp.EUph50: line 1: fg: no job control
      warning: %posttrans(rubygem-foreman_rh_cloud-5.0.46-1.el8sat.noarch) scriptlet failed, exit status 1

      2023-04-10T13:13:39+0000 ERROR Error in POSTTRANS scriptlet in rpm package rubygem-foreman_rh_cloud

      Version-Release number of selected component (if applicable):
      rubygem-foreman_rh_cloud-5.0.46-1.el8sat

      How reproducible:
      Every time, and easily

      Steps to Reproduce:
      1. yum module enable satellite --enablerepo=satellite-6.12-for-rhel-8-x86_64-rpms
      2. yum install rubygem-foreman_rh_cloud --enablerepo=satellite-6.12-for-rhel-8-x86_64-rpms
      3.

      Actual results:
      Errors during installation

      Expected results:
      Successful installation, with no errors encountered

      Additional info:
      There is at least one report of this failure causing an in-place-upgrade failure between RHEL 7 and RHEL 8. Setting severity to High as a result.

              jira-bugzilla-migration RH Bugzilla Integration
              jira-bugzilla-migration RH Bugzilla Integration
              RH Bugzilla Integration RH Bugzilla Integration
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: