Bug 1029812
| Summary: | vdsm-tool configure outputs misleading error messages although it ends successfully | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Vered Volansky <vered> |
| Component: | vdsm | Assignee: | Yaniv Bronhaim <ybronhei> |
| Status: | CLOSED ERRATA | QA Contact: | Petr Beňas <pbenas> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.3.0 | CC: | aberezin, acathrow, adahms, amureini, bazulay, iheim, lpeer, mgoldboi, pstehlik, sbonazzo, ybronhei, yeylon |
| Target Milestone: | --- | ||
| Target Release: | 3.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | infra | ||
| Fixed In Version: | ovirt-3.4.0-beta2 | Doc Type: | Bug Fix |
| Doc Text: |
This update enhances the output produced by the vdsm-tool to provide more information to users on encountering errors.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-09 13:26:34 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1078909, 1142926 | ||
|
Description
Vered Volansky
2013-11-13 09:41:48 UTC
Yes, it looks kinda funny imo. I'll think what we can do there.. Thanks. Verified in vdsm-4.14.1-3.el6.x86_64.
[root@slot-7 ~]# vdsm-tool configure
Checking configuration status...
SUCCESS: ssl configured to true. No conflicts
libvirt is not configured for vdsm yet
sanlock service is already configured
Traceback (most recent call last):
File "/usr/bin/vdsm-tool", line 145, in <module>
sys.exit(main())
File "/usr/bin/vdsm-tool", line 142, in main
return tool_command[cmd]["command"](*args[1:])
File "/usr/lib64/python2.6/site-packages/vdsm/tool/configurator.py", line 213, in configure
"--force flag.\n" % s
RuntimeError:
Cannot configure while service 'vdsmd' is running.
Stop the service manually or use the --force flag.
[root@slot-7 ~]# service vdsmd stop
Shutting down vdsm daemon:
vdsm watchdog stop [ OK ]
vdsm: Running run_final_hooks [ OK ]
vdsm stop [ OK ]
[root@slot-7 ~]# vdsm-tool configure
Checking configuration status...
SUCCESS: ssl configured to true. No conflicts
libvirt is not configured for vdsm yet
sanlock service is already configured
Running configure...
Reconfiguration of libvirt is done.
Done configuring modules to VDSM.
[root@slot-7 ~]# vdsm-tool configure
Checking configuration status...
SUCCESS: ssl configured to true. No conflicts
libvirt is already configured for vdsm
sanlock service is already configured
Running configure...
Done configuring modules to VDSM.
Doc-text is actually wrong. The update removed misleading error messages that shouldn't have gotten to the user the way they did. It does not provide *more* inforamtion to the user. Bronheim, do you agree? no, the output was correct but hard to understand. this is only enhancement in stdout prints, as described in the doc-text. 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-0504.html |