Bug 1424786

Dan, does it make sense? Sounds like a tiny little fix for a newcomer:)

Flipping the default sounds reasonable, but I'm afraid that I am not familiar with the purpose of the checkbox.

Israel, can you explain what is it good for, and whether you'd want it to be set by default?

I guess it more PM decision the behavior of run once.
I think it should be set on default.  
If you going to fix this issue please see  this BZ 1439738 also.
Also UI issue in Run once.

The decision is PM's but I asked for *your* opinion. When unchecked, does it mean that the guest interface on down when the VM starts?

I recheck it 
Case 1:
2  nics (both nic are up) 
1. Create VM with 2 nics (both nic are up) 
2. Run it with runonce 
   Set the second NIC with cloud init 
   - Enable Network 
   - Add Nic with boot option None, static and DHCP 
     configure nic2 as eth1
     Set start on boot 
3. Check status after VM is up
Results: 
Nic2 is up
 
Case 2:
2  nics (nic1 up, nic2 down) 
Same steps as case 1
Results: 
Nic2 is down

The start on boot has no effect on Nic status.
I don't see we sent it in the payload:
[root@puma42 payload]# cat  /mnt/openstack/latest/
meta_data.json  user_data       
[root@puma42 payload]# cat  /mnt/openstack/latest/*
{
  "network-interfaces" : "auto eth1\niface eth1 inet none\n",
  "availability_zone" : "nova",
  "hostname" : "noc_down",
  "launch_index" : "0",
  "meta" : {
    "role" : "server",
    "dsmode" : "local",
    "essential" : "false"
  },
  "name" : "noc_down",
  "network_config" : {
    "path" : "/etc/network/interfaces",
    "content_path" : "/content/0000"
  },
  "uuid" : "2304c498-322d-4e25-bc68-e6c9aa1de93a"
}#cloud-config
output:
  all: '>> /var/log/cloud-init-output.log'
password: '1'
disable_root: 0
runcmd:
- 'sed -i ''/^datasource_list: /d'' /etc/cloud/cloud.cfg; echo ''datasource_list:
  ["NoCloud", "ConfigDrive"]'' >> /etc/cloud/cloud.cfg'
ssh_pwauth: true
chpasswd:
  expire: false
user: root

Sorry, Israel, but I don't understand your answer. What is your opinion: should the default be flipped? should the checkbox be dropped completely?

It is not clear which of the two cases generated the payload that you presented (which has only a single eth1 nic)

I recheck it with one nic.
Steps:
1. Create Vm with one NIC and set nic to down from the engine.
2. Set cloud init:
   -Add network
   -Add NIC
    Name: eth0 
    Enable start on boot for this nic
3. Start VM and check Nic status
Results:
On Guest Nic is down

See payload on host:
[root@puma43 payload]# cat  /mnt/openstack/latest/meta_data.json 
{
  "network-interfaces" : "auto eth0\niface eth0 inet dhcp\n",
  "availability_zone" : "nova",
  "hostname" : "nic_test",
  "launch_index" : "0",
  "meta" : {
    "role" : "server",
    "dsmode" : "local",
    "essential" : "false"
  },
  "name" : "nic_test",
  "network_config" : {
    "path" : "/etc/network/interfaces",
    "content_path" : "/content/0000"
  },
  "uuid" : "d45c5739-f150-4c60-93d3-71756c230c96"
}[root@puma43 payload]# cat  /mnt/openstack/latest/user_data 
#cloud-config
output:
  all: '>> /var/log/cloud-init-output.log'
password: '1'
disable_root: 0
runcmd:
- 'sed -i ''/^datasource_list: /d'' /etc/cloud/cloud.cfg; echo ''datasource_list:
  ["NoCloud", "ConfigDrive"]'' >> /etc/cloud/cloud.cfg'
ssh_pwauth: true
chpasswd:
  expire: false
user: root


I can't find the start on boot option in the network settings:
  "network-interfaces" : "auto eth0\niface eth0 inet dhcp\n"

https://gerrit.ovirt.org/#/c/81760/ makes Engine use the modern OpenStack metadata file to communicate with cloud-init.

In it, there is no way to specify anything but start-on-boot=True, so we plan to set the default (and the only valid value) to True.

Hi, Dan, where did you find information about start-on-boot?

Right know we have this checkbox checked and non-active, e.g. you cant disable it which might be not suitable for some users.

This is a known deficiency, due to our moving away from legacy http://cloudinit.readthedocs.io/en/latest/topics/network-config-format-eni.html#network-config-eni to modern https://specs.openstack.org/openstack/nova-specs/specs/liberty/implemented/metadata-service-network-info.html

If you think that it is important for our customers to be able to define a CFG but not actually activate it on boot, please file an RFE on cloud-init, with RHEV as its LayeredProduct.

I, for one, do not think that this is important at all, as cloud-init is all about initialiazing a VM.

Verified on Version 4.2.0-0.0.master.20171112130303.git8bc889c.el7.centos

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.