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 910816 - [RFE] node upgrade command-line interface
Summary: [RFE] node upgrade command-line interface
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 858596
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-13 16:11 UTC by Mike Burns
Modified: 2014-01-21 19:25 UTC (History)
19 users (show)

Fixed In Version: ovirt-node-3.0.0-6.el6
Doc Type: Enhancement
Doc Text:
A new upgrade utility is provided to use the python modules from the newer media. This is to prevent work-flow upgrade issues where problems are solved in a newer version. These issues were overcome by booting install media in previous versions.
Clone Of: 858596
Environment:
Last Closed: 2014-01-21 19:25:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0033 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2014-01-22 00:14:30 UTC

Description Mike Burns 2013-02-13 16:11:35 UTC 
+++ This bug was initially created as a clone of Bug #858596 +++

Following discussion, was asked to open RFE, did not find RFE category, please feel free to label this correctly.

Will be glad to discuss this.

---

MISSION

Providing component independent node upgrade command-line interface.

REASON

Node base should provide life cycle management:
 - install - provided.
 - reinstall - provided.
 - upgrade via boot - provided.
 - upgrade via command-line - provided indirectly as an API.

Node upgrade is not related to any hosted components, for example VDSM.

Node infrastructure is the one that knows the filesystem structure, where to put large images, what is the image format etc... No reason to expose these to hosted components.

USAGE

 ovirt-node-upgrade [--reboot[=NN]] [-f|--image image|-]
     --reboot
         perform reboot after installation, defer to NN seconds,
         default=10.
     -f, --image
         read node image from this file, '-' is stdin.

HOOKS

In order to allow hosted components to take action during upgrade, hooks mechanism is suggested.

A directory for each state, each directory contains files/symlinks, which will be executed alphabetical sorted.

 /usr/libexec/ovirt-node/hooks/
     pre-upgrade
         000-vdsm
     post-upgrade
     rollback
         900-vdsm

At the above example, VDSM will be stopped before upgrade, and started if rollbacked.

LOGIC

At least:

1. If image is read from stdin, read image and store it on the filesystem within temporary location.

2. Verify image integrity, using md5sum of the iso.

3. Execute pre-upgrade hooks.

4. Mount^^3 the image, execute image upgrade.

5. Delete the image from temporary location if read from stdin.

6. Execute post-upgrade or rollback hooks.

7. Optionally async reboot.

SIMPLE TEST CASE

$ cat ovirt-node.iso | ssh root@node "ovirt-node-upgrade --reboot -f -"


--- Additional comment from Alon Bar-Lev on 2012-09-19 05:29:43 EDT ---

I forgot two more hooks I would like to have...

On the image it-self, pre-image-upgrade, post-image-upgrade, so that the new component on the image can execute some logic during upgrade.
Comment 12 Cheryn Tan 2013-11-08 00:35:05 UTC 
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.
Comment 15 errata-xmlrpc 2014-01-21 19:25:05 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.

http://rhn.redhat.com/errata/RHBA-2014-0033.html
Note You need to log in before you can comment on or make changes to this bug.