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 1706267 - fg: no job control in post scriptlet while installing satellite 6.6
Summary: fg: no job control in post scriptlet while installing satellite 6.6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Packaging
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.6.0
Assignee: Evgeni Golov
QA Contact: Nikhil Kathole
URL:
Whiteboard:
: 1708848 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-04 01:08 UTC by Nikhil Kathole
Modified: 2019-10-22 12:47 UTC (History)
4 users (show)

Fixed In Version: foreman-1.22.0.4-2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 12:47:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 27225 0 Normal Closed fg: no job control in post scriptlet while installing foreman 2020-09-03 16:08:55 UTC
Red Hat Product Errata RHSA-2019:3172 0 None None None 2019-10-22 12:47:28 UTC

Description Nikhil Kathole 2019-05-04 01:08:20 UTC 
Description of problem:

fg: no job control in post scriptlet while installing satellite 6.6

Transaction Summary
==================================================================================================================================================
Install  2 Packages (+568 Dependent packages)

Total download size: 384 M
Is this ok [y/d/N]: y
Warning: RPMDB altered outside of yum.
warning: user apache does not exist - using root
warning: group apache does not exist - using root
warning: user apache does not exist - using root
warning: group apache does not exist - using root
sed: can't read /etc/sysconfig/ipmi: No such file or directory
/var/tmp/rpm-tmp.eSpJPO: line 7: fg: no job control

Installed:
  python2-pycurl.x86_64 0:7.43.0.2-4.el7sat                                 satellite.noarch 0:6.6.0-2.beta.el7sat 

Version-Release number of selected component (if applicable): 
Satellite 6.6 snap 1


How reproducible: always


Steps to Reproduce:
1. yum install satellite

Actual results:

post scriptlet while installing satellite 6.6
/var/tmp/rpm-tmp.eSpJPO: line 7: fg: no job control

Expected results: No post scriptlet error.


Additional info:
Comment 4 Evgeni Golov 2019-05-06 09:51:38 UTC 
Thanks Nikhil,

the Satellite RPM does not have any `fg` in its %post scriptlet.

Do you happen to know from which RPM this is coming?
Comment 5 Nikhil Kathole 2019-05-06 11:43:38 UTC 
Hey Evgeni,

I am not sure which rpm is causing it :/

Thanks.
Comment 6 Devendra Singh 2019-05-11 14:18:08 UTC 
*** Bug 1708848 has been marked as a duplicate of this bug. ***
Comment 7 Lukas Pramuk 2019-06-04 14:52:47 UTC 
Evgeni,

Regarding "/var/tmp/rpm-tmp.r1JyVV: line 7: fg: no job control" 
I found out it's posttrans scriptlet in foreman rpm:

# rpm -q foreman foreman-1.22.0-0.5.RC2.1.el7sat.noarch

# rpm -q --scripts foreman
...
posttrans scriptlet (using /bin/sh):
# We need to run the db:migrate after the install transaction
# always attempt to reencrypt after update in case new fields can be encrypted
/usr/sbin/foreman-rake db:migrate db:encrypt_all >> /var/log/foreman/db_migrate.log 2>&1 || :
/usr/sbin/foreman-rake db:seed >> /var/log/foreman/db_seed.log 2>&1 || :
/usr/sbin/foreman-rake apipie:cache:index >> /var/log/foreman/apipie_cache.log 2>&1 || :
/usr/sbin/foreman-rake tmp:clear >> /var/log/foreman/tmp_clear.log 2>&1 || :
%{foreman_restart} || :
exit 0


^ There is un-expanded %{foreman_restart}
Comment 8 Ewoud Kohl van Wijngaarden 2019-07-03 15:56:36 UTC 
Created redmine issue https://projects.theforeman.org/issues/27225 from this bug
Comment 9 Bryan Kearney 2019-07-03 18:06:10 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27225 has been resolved.
Comment 11 Nikhil Kathole 2019-07-07 09:02:08 UTC 
VERIFIED

version tested:
Satellite 6.6.0 snap 10

 ================================================================================
 Install  2 Packages (+564 Dependent packages)
 
 Total download size: 399 M
 Warning: RPMDB altered outside of yum.
 warning: user apache does not exist - using root
 warning: group apache does not exist - using root
 warning: user apache does not exist - using root
 warning: group apache does not exist - using root
 sed: can't read /etc/sysconfig/ipmi: No such file or directory
 
 Installed:
   python2-pycurl.x86_64 0:7.43.0.2-4.el7sat                                     
   satellite.noarch 0:6.6.0-5.beta.el7sat
Comment 13 errata-xmlrpc 2019-10-22 12:47:18 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, 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-2019:3172
Note You need to log in before you can comment on or make changes to this bug.