Bug 989360 - IP of rhevm bridge should be greyed out when rhevm has static IP configuration
Summary: IP of rhevm bridge should be greyed out when rhevm has static IP configuration
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.3.0
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
: 3.3.0
Assignee: Lior Vernia
QA Contact: GenadiC
URL:
Whiteboard: network
Depends On:
Blocks: 1019461 3.3snap1
TreeView+ depends on / blocked
 
Reported: 2013-07-29 06:58 UTC by GenadiC
Modified: 2016-02-10 19:49 UTC (History)
10 users (show)

Fixed In Version: is20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-26 15:00:39 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 20345 0 None None None Never
oVirt gerrit 20346 0 None None None Never
oVirt gerrit 20347 0 None None None Never

Description GenadiC 2013-07-29 06:58:12 UTC
Description of problem:
You can't change static IP configuration on rhevm bridge, so it should be greyed out. The situation now is that you can change the ip, but when pushing the ok button you get an error message that you need to reinstall the host in order to change IP

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Start with static ip configuration 
2. Try to change ip
3.

Actual results:
You get an error message: The management network address cannot be modified without reinstalling the host

Expected results:
IP should be greyed out and this message should be in tool tip.

Additional info:
	
	
	
Error while executing action:

silver-vdsa.qa.lab.tlv.redhat.com:

    Cannot setup Networks. The management network address cannot be modified without reinstalling the host, since this address was used to create the host's certification.

Comment 2 Lior Vernia 2013-10-27 07:25:00 UTC
Some documentation for posterity's sake: the bug wasn't fixed as proposed, but rather the behavior was changed so that the IP address of ANY network (not only management) can be changed if and only if it hadn't been equal to the hostname, as in that case (and only in that case) it is known for sure that the engine would lose connectivity to the host.


Note You need to log in before you can comment on or make changes to this bug.