Bug 725992
| Summary: | Restart vdsm-reg immediately after configure RHEV-M on UI | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Guohua Ouyang <gouyang> |
| Component: | vdsm | Assignee: | Yotam Oron <yoron> |
| Status: | CLOSED ERRATA | QA Contact: | Pavel Stehlik <pstehlik> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.2 | CC: | abaron, apevec, bazulay, cshao, iheim, ilvovsky, jboggs, leiwang, mburns, moli, sgordon, ycui, ykaul, yoron |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | vdsm-4.9-96.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-06 07:32:15 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Guohua Ouyang
2011-07-27 09:29:27 UTC
I guess you are referring to manual configuration of RHEV-M. Are you? Alan, shouldn't this happen only after everything on the node is configured, i.e. by ovirt-node? (In reply to comment #2) > I guess you are referring to manual configuration of RHEV-M. Are you? > Yes, it's manual configuration, on UI. > Alan, shouldn't this happen only after everything on the node is configured, > i.e. by ovirt-node? With new RHEV-H TUI there are two steps: - installation where only disk is selected and admin password set after installation to disk, node reboots and at login prompt you can logon as 'admin' to enter next step: - configuration menu where hostname, networking, RHN, RHEV-M etc. can be set. RHEV-M configuration UI plugin is part of this second step and there you don't have "end" phase where delayed actions can be performed. All configuration items should be self-contained e.g. under Networking we perform network restart after <Apply> button is selected. So it's responsibility of the RHEV-M TUI plugin to restart services it needs. But in this case, I'm not sure why vdsm-reg was not already running, once it's running (from RTFS) it should retry registration every 6-10s. Please expand "Steps to Reproduce" so we can see how did you get into situation that vdsm-reg is not running. It should be the vdsm-reg are not reloading the conf file after configured rhevm in TUI. #tail -f /var/log/vdsm-reg/vdsm-reg.log, it repeats below message in 6-10s: self.vdcURL None self.vdcPORT 443 self.vdcURI /RHEVManagerWeb/VdsAutoRegistration.aspx self.vdcRegPort 54321 self.ovirtURL None self.ovirtName None self.ovirtUID None self.vdcName None MainThread::DEBUG::2011-08-02 02:57:48,214::vdsm-reg-setup::74::root::validate start MainThread::DEBUG::2011-08-02 02:57:48,214::vdsm-reg-setup::81::root::validate end. return: False expand steps below: 1. install rhev-h node. 2. logon, check vdsm-reg service is running. 3. enter setup, configure network interface 4. configure rhevm. 5. apply the rhevm configuration. 6. drop to shell, check the vdsm-reg is still running. 7. check the conf file, looks fine. vdc_host_name=10.66.11.102 vdc_host_port=8443 8. Check on rhevm host page, no rhev-h node added there. Ouyangguohua, can you please try and reproduce it on the latest ovirt image ? I can't seem to be able to reproduce it. Thanks. Will try it (In reply to comment #6) > Ouyangguohua, can you please try and reproduce it on the latest ovirt image ? > I can't seem to be able to reproduce it. > Thanks. Ok, I will try it on the latest build. I think I reproduced it, after configuring RHEV-M in TUI, I dropped to shell and checked vdsm-reg.log: MainThread::DEBUG::2011-08-10 22:33:35,013::vdsm-reg-setup::270::vdsRegistrator::Total retry count: 535, waited: 8 seconds. MainThread::DEBUG::2011-08-10 22:33:35,015::vdsm-reg-setup::37::root::__init__ begin. MainThread::DEBUG::2011-08-10 22:33:35,016::vdsm-reg-setup::70::root::Setup::__init__ vars: self.vdcURL None self.vdcPORT 443 self.vdcURI /RHEVManagerWeb/VdsAutoRegistration.aspx self.vdcRegPort 54321 self.ovirtURL None self.ovirtName None self.ovirtUID None self.vdcName None MainThread::DEBUG::2011-08-10 22:33:35,017::vdsm-reg-setup::74::root::validate start MainThread::DEBUG::2011-08-10 22:33:35,018::vdsm-reg-setup::81::root::validate end. return: False [root@node8 ~]# ll /etc/vdsm-reg/vdsm-reg.conf -rw-r--r--. 1 root root 758 2011-08-10 22:28 /etc/vdsm-reg/vdsm-reg.conf Note vdsm-reg.conf timestamp - vdsm-reg still didn't pick it up after few minutes! Simple fix for this would be to restart the vdsm-reg service when the rhev-m configuration is changed. Verified on 6.2-0.15, after configure rhevm on TUI, the rhevh node is registered to rhevm automatically, no need to drop to shell and restart vdsm-reg now. Cleared release notes flags (no release notes needed) 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/RHEA-2011-1782.html |