Public bug reported:

This FFe would cause EC2 instance to fetch networking information every
boot and is implemented in https://github.com/canonical/cloud-
init/pull/5110 . Currently, EC2 only fetches that information first boot
and uses that cached information on subsequent boots.

https://github.com/canonical/cloud-init/pull/4799 (which is part of
Noble) added the ability to respond to NIC changes (hotplug) on a
running instance and made it default behavior. This leaves us with a gap
in that we can respond to hotplug events while the instance is running,
but if network changes while the instance is powered off, the instance
won't be aware of the network changes on next boot.

This FFe is to close that gap. This has already been discussed with and
approved by Amazon in Salesforce case #00378972 .

** Affects: cloud-init (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

- This would cause EC2 instance to fetch networking information every
+ This FFe would cause EC2 instance to fetch networking information every
  boot. Currently, EC2 only fetches that information first boot and uses
  that cached information on subsequent boots.
  
  https://github.com/canonical/cloud-init/pull/4799 (which is part of
  Noble) added the ability to respond to NIC changes (hotplug) on a
  running instance and made it default behavior. This leaves us with a gap
  in that we can respond to hotplug events while the instance is running,
  but if network changes while the instance is powered off, the instance
  won't be aware of the network changes on next boot.
  
  This FFe is to close that gap. This has already been discussed with and
  approved by Amazon in Salesforce case #00378972 .

** Description changed:

  This FFe would cause EC2 instance to fetch networking information every
- boot. Currently, EC2 only fetches that information first boot and uses
- that cached information on subsequent boots.
+ boot and is implemented in https://github.com/canonical/cloud-
+ init/pull/5110 . Currently, EC2 only fetches that information first boot
+ and uses that cached information on subsequent boots.
  
  https://github.com/canonical/cloud-init/pull/4799 (which is part of
  Noble) added the ability to respond to NIC changes (hotplug) on a
  running instance and made it default behavior. This leaves us with a gap
  in that we can respond to hotplug events while the instance is running,
  but if network changes while the instance is powered off, the instance
  won't be aware of the network changes on next boot.
  
  This FFe is to close that gap. This has already been discussed with and
  approved by Amazon in Salesforce case #00378972 .

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059317

Title:
  [FFe] EC2 fetch metadata every boot

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


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to