Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 905849

Summary: rhevm server still is persisted even it is unreachable when auto install.
Product: Red Hat Enterprise Virtualization Manager Reporter: chenchao <chchen>
Component: vdsmAssignee: Douglas Schilling Landgraf <dougsland>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.1.0CC: bazulay, cpelland, cshao, dyasny, gouyang, hadong, hateya, iheim, leiwang, lpeer, ycui, ykaul
Target Milestone: ---   
Target Release: 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-21 03:14:13 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:
Attachments:
Description Flags
sreen shot none

Description chenchao 2013-01-30 10:11:35 UTC 
Description of problem:
rhevm server still is persisted even it is unreachable when auto install.

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.3-20130129.0.el6_3


How reproducible:

100%


Steps to Reproduce:
1.auto install with parameter "BOOTIF=eth0  adminpw=$ management_server=$RHEV-M_IP storage_init=ata storage_vol=:2000::20:2048:2000 firstboot",$RHEV-M_IP is not a unreachable server。
2.after reboot.focus on nic page.


actual result:
rhevm server still is persisted,the nic is readonly mode.

expect result:
rhevm server should be persisted if it is unreachable.

addtional:
1.There is no this issue on 6.4
2.If setting a unreachable rhevm server via TUI,it will not be persist.
Comment 1 chenchao 2013-01-30 10:13:30 UTC 
Created attachment 690263 [details]
sreen shot
Comment 3 Barak 2013-02-12 16:25:49 UTC 
chenchao,

Please elaborate what you mean by persist.
I assume you refer to the vdsm-reg conf file.

Basically the flows are different when you use PXE and TUI.
TUI is interactive and it is meant to leave the rhevh in operational state, so in case the host is unreachable it make sense not to persist it.

While on the PXE install, the actual installation of the rhevh may happen even prior to the rhevm installation (or while it's down), and one would expect the rhevh to continue try and register till it succeeds.

Simon ?
Comment 5 Dan Yasny 2013-02-14 13:19:00 UTC 
(In reply to comment #3)
> chenchao,
> 
> Please elaborate what you mean by persist.
> I assume you refer to the vdsm-reg conf file.
> 
> Basically the flows are different when you use PXE and TUI.
> TUI is interactive and it is meant to leave the rhevh in operational state,
> so in case the host is unreachable it make sense not to persist it.

ack

> 
> While on the PXE install, the actual installation of the rhevh may happen
> even prior to the rhevm installation (or while it's down), and one would
> expect the rhevh to continue try and register till it succeeds.

indefinitely? I would put a limit to the amount of retries, or set up a long timeout.
Comment 6 Douglas Schilling Landgraf 2013-02-20 19:53:05 UTC 
Target Release is 3.2.0 and if this report is not happening on 6.4 (by description), I do believe we should close this bugzillas as next release.

chenchao, can you please confirm?

Thanks!
Comment 7 chenchao 2013-02-21 02:31:53 UTC 

(In reply to comment #6)
> Target Release is 3.2.0 and if this report is not happening on 6.4 (by
> description), I do believe we should close this bugzillas as next release.
> 
> chenchao, can you please confirm?
> 
> Thanks!
I have verified this issue is not happening on 6.4 (by description),so this bugzillas can be closed as next release.