Description of problem: The Management Server info not display in RHEV-M menu when add the rhevh from rhevm side Version-Release number of selected component (if applicable): rhevh version: rhev-hypervisor6-6.4-20130221.0.el6 rhevm version: sf3. How reproducible: 100% Steps to Reproduce: 1.Install the rhevh on one machine. 2.Add the rhevh from the rhevm side.focus on rhev-m page on the TUI. Actual results: RHEV-H can up. but the Management Server info not display in RHEV-M menu Expected results: The Management Server info should display in RHEV-M menu when add the rhevh from rhevm side Additional info:
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.