Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
If process is terminated when using 'connections' from rhnlib, 'connections' reports socket error but we need to distinguish interrupt more precisely.
This Bugzilla has been created from https://bugzilla.redhat.com/show_bug.cgi?id=1260527
This issue
Version-Release number of selected component (if applicable):
rhnlib-2.6.1-1
How reproducible:
Always on RHEL 7
Steps to Reproduce:
1. Register a RHEL 7 VM to satellite 5.7
2. Assign provisioning entitlement to RHEL 7 system
3. Subscribe RHEL 7 system to RHN tools channel.
4. Install rhncfg and osad packages on RHEL 7 system using below command :
# yum install rhncfg*
# yum install osad
5 enable all actions for RHEL 7 system by executing below command :
# rhn-actions-control --enable-all
6. Go to RHEL 7 systems profile on satellite webui.
7. Click on "Details" tab.
8. Click on "Remote Command".
9. In "Script" section add following command
shutdown -h now
10. Select appropriate time interval and date.
11. Click on schedule.
12. Now wait till command is executed. Once system is shutdown observe its status satellite webui.
Actual results:
1. Command is executed and system shuts down.
2. Status on satellite webUI remains as "The client has not yet completed this action"
3. When we power-on the system again the task gets executed and system gets shutdown
This goes in a loop. Action is never marked as completed.
Expected results:
1. Command is executed and system shuts down.
2. Status on satellite webUI should be : Completed
Additional info:
See https://bugzilla.redhat.com/show_bug.cgi?id=1260527 for original bug report.
This is fixed in spacewalk.git by
75d9c00b96ab430221c5c7668baebebc74ddd67e
1840e8fb9fe2f5bf8fe29fd62bbd245660ceb1d2
Comment 3Lukáš Hellebrandt
2017-06-29 14:42:27 UTC
Verified with rhnlib-2.5.65-4, rhn-client-tools-2.0.2-11 (ONLY, rhn-client-tools-2.0.2-16 version is broken).
Schedule a script to be run (long sleep), rhn_check, wait for it to pick up the script (it is shown in WebUI), then kill rhn_check with SIGTERM. If in WebUI, the state of script becomes '"Script executed. Termination signal occurred during execution" (code 0)', this part of fix works fine.
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/RHBA-2017:2039