Red Hat Bugzilla – Bug 964967
PRD33 - [RFE] vdsm-tool for offline usages
Last modified: 2016-02-10 14:27:56 EST
Per bug#916095, discussion at and other uses, it would be great if we have offline vdsm tool for tasks that do not require vdsm to be configured nor up.
1. get vdsm id (bug#916095)
engine may use utility to return vdsm id, without duplicate the logic into the engine.
2. libvirt reconfigure
remove the logic from the init script which is not supported by systemd into common place.
3. certificate issue sequence [FUTURE]
ability to issue a certificate, perform the request accept the chain in a user friendly manner (and program friendly), this will enable host-deploy to perform enrollment without depend on the artifacts locations.
4. stop/start [FUTURE]
stop/start the entire component. handy when there are several services around.
according to tracker, patch is merged.
moving to MODIFIED.
*** Bug 978906 has been marked as a duplicate of this bug. ***
1) libvirt-configure part is not merged - why is it on_qa ?
2) missing libvirt-configure usage in help
3) missing service-like usage in help
4) missing vdsm-id usage in help
1) still in progress.
2) its part of the patch that hasn't been merged yet.
3,4) "vdsm-id: Printing host uuid" -> that's what it does, if its lack of more information, let me know what do you think we should add?
and the service like is quite informative:
service-disable Disable a system service
service-is-managed Check the existence of a service
service-reload Notify a system service to reload
service-restart Restart a system service
service-start Start a system service
service-status Get status of a system service
service-stop Stop a system service
Also when run command vdsm-tool service-restart vdsmd for example, not any information messages appear
If I need to verify for sections 3 and 4(id and services) or wait until libvirt-configure part?
http://gerrit.ovirt.org/15216 with libvirt-configure is in.
Verified on is7
vdsm-tool vdsm-id return host id
vdsm-tool service-* not return any information message and return traceback instead of user friendly message, but work fine checking via service status
example of return vdsm-tool service-stop vdsm 1
Traceback (most recent call last):
File "/usr/bin/vdsm-tool", line 143, in <module>
File "/usr/bin/vdsm-tool", line 140, in main
TypeError: service_stop() takes exactly 1 argument (2 given)
This bug is currently attached to errata RHBA-2013:15291. 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:
Thanks in advance.
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.