Created attachment 900314[details]
ovirt.log
Description of problem:
1. If user just register hypervisor to rhevm but not approve it, the
network status will show as unconfigured. This would cause all network
related configure are not able to complete.(e.g. logging, kdump,
remote storage, rhn)
2. Another issue is user can't register to another RHEVM in TUI once the
hypervisor has been registered. So set priority to High.
Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.5-20140527.0
ovirt-node-3.0.1-18.el6_5.10
ovirt-node-plugin-vdsm-0.1.1-22.el6ev
vdsm-4.14.7-3.el6ev.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Install RHEV-H.
2. Register the hypervisor to RHEVM but without approve.
3. TUI:Check network status in RHEV-H side.
4. CMD: run command "ifconfig"
Actual results:
1. After step 3, the network status show as unconfigured in TUI.
2. All network related configure are not able to complete.(e.g.
logging, kdump, remote storage, rhn)
3. After step4, the hypervisor can obtain IP in CMD, and the bridge
show as RHEVM.
Expected results:
Network show as "Managed" and all network related configure are operable.
Additional info:
This is actually work as designed.
The network configuration happens after:
1 - registration
2 - approval
3 - host deploy is executed
4 - network configuration is applied from the engine
Alon, Moti - please approve
Created attachment 900314 [details] ovirt.log Description of problem: 1. If user just register hypervisor to rhevm but not approve it, the network status will show as unconfigured. This would cause all network related configure are not able to complete.(e.g. logging, kdump, remote storage, rhn) 2. Another issue is user can't register to another RHEVM in TUI once the hypervisor has been registered. So set priority to High. Version-Release number of selected component (if applicable): rhev-hypervisor6-6.5-20140527.0 ovirt-node-3.0.1-18.el6_5.10 ovirt-node-plugin-vdsm-0.1.1-22.el6ev vdsm-4.14.7-3.el6ev.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install RHEV-H. 2. Register the hypervisor to RHEVM but without approve. 3. TUI:Check network status in RHEV-H side. 4. CMD: run command "ifconfig" Actual results: 1. After step 3, the network status show as unconfigured in TUI. 2. All network related configure are not able to complete.(e.g. logging, kdump, remote storage, rhn) 3. After step4, the hypervisor can obtain IP in CMD, and the bridge show as RHEVM. Expected results: Network show as "Managed" and all network related configure are operable. Additional info: