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:
I plan to restart system and the osad pick this task. I changed opinion and I cancel restarting shutdown -c. But the task still is not finished. Problem is that the next task is not picked up by osad/rhn_check and it is still in queue.

Version-Release number of selected component (if applicable):
rhn-client-tools-2.0.2-11.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. run osad 
2. schedule reboot system
3. shudown -c

Actual results:
after cancel, the following tasks are not picked up

Expected results:
the next tasks are picked up and the task with reboot is cancel/finished

Hi,

could you please provide me some more detailed information about steps 2. and 3.? 

2. Did you schedule the reboot using the remote command? What exactly the command was?

3. Did you execute "shutdown -c" directly on the client or via remote command?

Thank you

I think that it is same. But steps are:

1) Install osad and start service
2) click to "Schedule System Reboot" (shutdown -r 3)
3) run the command in bash to cancel rebooting: shutdown -c

The same problem exists on RHEL 6.

The issue is very specific situation. I try to figure out real situation. For example that first person are working on the system and other person set reboot for it. First person sees that the reboot is planned (reboot sends message to wall each minute) and cancels reboot. 

Or (my situation) I choose bad system to reboot and need to quick cancel it.

Described case is definitely correct, but in order to keep event handling consistent, we won't do any code change for this BZ. In case you want to cancel pending action, please use API schedule.failSystemAction.

I created new bug 1471018 for described issue.