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.
+++ This bug was initially created as a clone of Bug #847103 +++
Currently the ovirt-functions::reboot() executes /sbin/reboot directly, previous versions used cron to perform reboot but slept until reboot.
As a result the ssh session that invokes the upgrade script is not terminated, leaving the TCP session opened, thus enforce engine to wait for timeout.
Desired behaviour is to allow script to successfully terminate before reboot by executing reboot at background, either by crond[1], or by sub-shell[2], or any other magic.
[1] echo "* * * * * sleep 10 && /sbin/reboot" > /var/spool/cron/root
[2] nohup sh -c '( sleep 10 && reboot )' < /dev/null > /dev/null 2>&1
----------------------------
See original bug for debugging details, but in summary, vdsm changed to call python instead of bash. When testing with that version, we uncovered the following 3 problems:
--- Additional comment from mburns on 2012-09-05 14:55:33 EDT ---
(In reply to comment #18)
> Mike,
>
> I tried this[1] image.
>
> 1. There is no /data/updates in new image, so image upload fails.
/data/updates is created by vdsm on startup. This is caused by (#3) vdsm failing to start, so just another symptom of #3
>
> 2. After I create /data/updates, update succeeds but no reboot.
Partially ovirt-node, partially vdsm. Patches posted upstream:
http://gerrit.ovirt.org/7777 -- ovirt-node
http://gerrit.ovirt.org/7778 -- vdsm
>
> 3. Another issue: after I approve, vdsm does not come up:
Pure vdsm issue (vdsm team to fill in details
>
> [root@alonbl4 ~]# /etc/init.d/vdsmd start
> checking certs..
> vdsm: libvirt already configured for vdsm [ OK ]
> Starting iscsid:
> vdsm: Failed to define network filters on libvirt [FAILED]
>
> Do you have rhev-m environment to test?
>
>
Comment 3Douglas Schilling Landgraf
2012-09-06 16:00:50 UTC
For vdsm does not come up:
>
> [root@alonbl4 ~]# /etc/init.d/vdsmd start
> checking certs..
> vdsm: libvirt already configured for vdsm [ OK ]
> Starting iscsid:
> vdsm: Failed to define network filters on libvirt [FAILED]
>
> Do you have rhev-m environment to test?
>
[Downstream]: vdsmd: set nwfilter on ovirt-node
https://gerrit.eng.lab.tlv.redhat.com/#/c/1915/
[Upstream]:Upstream: vdsmd: set nwfilter on ovirt-node
http://gerrit.ovirt.org/#/c/7821/
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.
http://rhn.redhat.com/errata/RHSA-2012-1508.html