yahoo-eng-team team mailing list archive

[James Falcon <1961589@xxxxxxxxxxxxxxxxxx>]

I'm not convinced that this is a reasonable thing to expect from cloud-
init. If you're worried about data integrity from a planned shut down,
can't you just call sync yourself? If you're worried about data
integrity from an unplanned power loss, then you probably need to use a
different filesystem or configure the one you're using to sync its
buffers more often.

** Changed in: cloud-init
       Status: New => Opinion

-- 
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/1961589

Title:
  SSH Host keys / network config lost after reboot

Status in cloud-init:
  Opinion

Bug description:
  Debian 11

  dpkg -l cloud-init
  ii  cloud-init                     20.4.1-2+deb11u1               all

  
  In a rare case, when the system gets restarted via power reset and has not flushed its data to the storage before (fsync), it can happen that the SSH host keys or the network config are missing. However, cloud-init does not generate the keys/network config again.

  A graceful restart should write the data to the disk, but it would
  probably make sense that cloud-init does a fsync, at least at the
  first boot, to ensure that the system is still reachable, even after a
  hard reboot.

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