Description of problem: Hi, currently, you can not set a static network via Cloud-Init. To clarify: The IP-Address, Netmask and Gateway get passed, but instead of "static" the option "none" gets passed to the vm. Version-Release number of selected component (if applicable): ovirt-engine 3.3.1-2 beta How reproducible: Steps to Reproduce: Select a shutdown vm, click run once. Click Initial Run, select Cloud-Init Now select "Network" and "add new" Name your interface, e.g. eth0 Do not configure DHCP, instead, fill in IP Address, Netmask, Gateway, etc. Start the vm. Actual results: if you mount the meta-data cd-rom into any vm and read the meta-data.json it says: iface eth0 inet none the rest of the information seems to be correct, though. Expected results: I would suppose that this would pass the following options into the meta-data: iface eth0 inet static Additional info: You can see this from 2 point of views: 1. If I do not select DHCP and I configure IP Address etc. I want a static configuration, therefore "static" should be in the meta-data. If I would have wanted "none", I wouldn't bother configuring the interface, would I? -> Bug 2. There is no button for "static" in the GUI, therefore the option get's not passed, "none" may be the default option. In this case, it would be cool to have a checkbox for "static". --> RFE I didn't test this from the API yet, but I hope there is an option to set the networking to static from there? What do you think? Bug or RFE? Can this be fixed in 3.3.1.1 maybe (fix should be small, without looking into the code)? I can't always do full upgrades (3.3.2 would be next). On the Maillinglist this was suggested as a bug.
Setting urgent priority until analysed
reduced priority to high, no reason for this to be urgent
setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.
This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
Hi Sven, There is really only two options dhcp and static/none, its look like there is no different between static to none bootproto. I notice some complains that in Fedora 20 that setting none as bootproto fall back to dhcp... The problem that I saw in the code is as you thought that if you are not selecting dhcp you are getting the default enumeration value which is none. We can fix it to set for static if dhcp is not selected, Would that be sufficient enough? (I don't think that we need to add another checkbox or set a select box)
Yes, I noticed pretty much the same, sorry for not reporting back earlier. in the offical RH docs there is no bootproto entry other than "none" and "dhcp". So I think your proposed solution should suffice.
This is an automated message oVirt 3.4.1 has been released: * should fix your issue * should be available at your local mirror within two days. If problems still persist, please make note of it in this bug report.