RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1181209 - Use systemd service status for run detection in S390 console
Summary: Use systemd service status for run detection in S390 console
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: initial-setup
Version: 7.2
Hardware: s390x
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Martin Kolman
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-12 15:23 UTC by Martin Kolman
Modified: 2015-11-19 11:23 UTC (History)
2 users (show)

Fixed In Version: initial-setup-0.3.9.28-2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 11:23:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2334 0 normal SHIPPED_LIVE initial-setup bug fix and enhancement update 2015-11-19 10:17:50 UTC

Description Martin Kolman 2015-01-12 15:23:42 UTC 
Description of problem:
In one of the s390 installation scenarios Initial setup is automatically launched by a special script on the first console loging after the installation. This script uses a configuration file even though it could just check if the Initial Setup systemd service is enabled. This introduces a special case that needs to be maintained to keep working, without bringing any benefits.

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

How reproducible:
always

Actual results:
a special configuration file is used to check if Initial Setup should be run

Expected results:
the startup script just checks if the Initial setup systemd service is enabled
Comment 4 Jan Stodola 2015-08-17 10:22:05 UTC 
Since systemd services are used now, I believe it is not necessary to create 
/etc/sysconfig/initial-setup in %post:

postinstall scriptlet (using /bin/sh):
if [ $1 -ne 2 -a ! -f /etc/sysconfig/initial-setup ]; then
  platform="$(arch)"
  if [ "$platform" = "s390" -o "$platform" = "s390x" ]; then
    echo "RUN_INITIAL_SETUP=YES" > /etc/sysconfig/initial-setup
  else
...

Moving to ASSIGNED
Comment 5 Martin Kolman 2015-08-25 11:26:01 UTC 
(In reply to Jan Stodola from comment #4)
> Since systemd services are used now, I believe it is not necessary to create 
> /etc/sysconfig/initial-setup in %post:
> 
> postinstall scriptlet (using /bin/sh):
> if [ $1 -ne 2 -a ! -f /etc/sysconfig/initial-setup ]; then
>   platform="$(arch)"
>   if [ "$platform" = "s390" -o "$platform" = "s390x" ]; then
>     echo "RUN_INITIAL_SETUP=YES" > /etc/sysconfig/initial-setup
>   else
> ...
> 
> Moving to ASSIGNED
Good point! I've posted a patch removing /etc/sysconfig/initial-setup creation from the spec file for review.
Comment 7 Jan Stodola 2015-09-04 10:54:19 UTC 
initial-setup starts based on the initial-setup systemd service status (enabled/disabled). Also /etc/sysconfig/initial-setup doesn't exist any more.

Tested with initial-setup-0.3.9.29-1.el7.

Moving to VERIFIED.
Comment 8 errata-xmlrpc 2015-11-19 11:23:16 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://rhn.redhat.com/errata/RHBA-2015-2334.html
Note You need to log in before you can comment on or make changes to this bug.