← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1893770] [NEW] Cloudinit resets network scripts to default configuration DHCP once Config Drive is removed after sometime

 

Public bug reported:

Cloudinit version: 19.1
Platform: OpenStack based.
OS: RHEL, SUSE

We use config drive(/dev/sr0) as a data source to configure network
interfaces in the guest but configdrive is not always available and may
be removed after couple of hours from the hypervisor.

On a first boot cloudinit uses data provided in config drive and updates
system level network scripts /etc/sysconfig/ifcfg-* (Static
configuration of networks) files and also configures the interface in
the guest.

As long as the configdrive is available, reboots will relay on system
scripts for the configuring network but once configdrive is removed,
datasource becomes None meaning it neither system script nor config
drive

which makes cloud init to configure default network which is DHCP

** Affects: cloud-init
     Importance: Undecided
         Status: New

** Description changed:

  Cloudinit version: 19.1
  Platform: OpenStack based.
  OS: RHEL, SUSE
  
+ We use config drive(/dev/sr0) as a data source to configure network
+ interfaces in the guest but configdrive is not always available and may
+ be removed after couple of hours from the hypervisor.
  
- We use config drive(/dev/sr0) as a data source to configure network interfaces in the guest but configdrive is not always available and may be removed after couple of hours from the hypervisor. 
- 
- 
- On a first boot cloudinit uses data provided in config drive and updates system level network scripts /etc/sysconfig/ifcfg-* (Static configuration of networks) files and also configures the interface in the guest. 
+ On a first boot cloudinit uses data provided in config drive and updates
+ system level network scripts /etc/sysconfig/ifcfg-* (Static
+ configuration of networks) files and also configures the interface in
+ the guest.
  
  As long as the configdrive is available, reboots will relay on system
  scripts for the configuring network but once configdrive is removed,
  datasource becomes None meaning it neither system script nor config
  drive
  
  which makes cloud init to configure default network which is DHCP

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1893770

Title:
  Cloudinit resets network scripts to default configuration DHCP once
  Config Drive is removed after sometime

Status in cloud-init:
  New

Bug description:
  Cloudinit version: 19.1
  Platform: OpenStack based.
  OS: RHEL, SUSE

  We use config drive(/dev/sr0) as a data source to configure network
  interfaces in the guest but configdrive is not always available and
  may be removed after couple of hours from the hypervisor.

  On a first boot cloudinit uses data provided in config drive and
  updates system level network scripts /etc/sysconfig/ifcfg-* (Static
  configuration of networks) files and also configures the interface in
  the guest.

  As long as the configdrive is available, reboots will relay on system
  scripts for the configuring network but once configdrive is removed,
  datasource becomes None meaning it neither system script nor config
  drive

  which makes cloud init to configure default network which is DHCP

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1893770/+subscriptions


Follow ups