Bug 915206
| Summary: | The Management Server info not display in RHEV-M menu when add the rhevh from rhevm side | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | chenchao <chchen> | ||||||||
| Component: | vdsm | Assignee: | Douglas Schilling Landgraf <dougsland> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | |||||||||
| Severity: | low | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 3.1.3 | CC: | acathrow, alonbl, bazulay, bsarathy, cshao, dyasny, gouyang, hadong, hateya, iheim, jboggs, leiwang, lpeer, mburns, ovirt-maint, ycui, ykaul | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | 3.3.0 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | infra | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-03-13 17:51:17 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: | 866889 | ||||||||||
| Bug Blocks: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
chenchao
2013-02-25 08:45:27 UTC
Created attachment 702245 [details]
screenshot
Created attachment 702247 [details]
engin.log
Created attachment 702249 [details]
ovirt.log
All that interaction is owned by vdsm, so moving to vdsm component. This affects 3.1 vdsm The Management Server info still miss in RHEV-M menu after register RHEV-H to RHEV-M sf8 build from RHEV-H side. Hello, During the vdsm-bootstrap rewrite (bug#866889), the role of vdsm-reg is modified, it is used only to register one time within the engine. Once registered there is no difference between the flow of adding a new host and approving registered host, the host-deploy is executed and deploy the host. If that host is ovirt-node then the vdsm-reg service is disabled. This is the reason you don't see the address of the engine after deployment, as the vdsm-reg configuration is cleared. In future, we will remove the vdsm-reg entirely (bug#875088), and probably change the interaction to use the new node pluggable user interface. This will enable to be somewhat more flexible. |