yahoo-eng-team team mailing list archive

[Scott Moser <1885527@xxxxxxxxxxxxxxxxxx>]

** Also affects: cloud-init
   Importance: Undecided
       Status: New

** Changed in: cloud-init
       Status: New => Fix Committed

** Changed in: cloud-init
   Importance: Undecided => Medium

** Changed in: cloud-init
     Assignee: (unassigned) => Markus Schade (lp-markusschade)

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

Title:
  cloud-init regenerating ssh-keys

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  In Progress

Bug description:
  Hi,

  I made some experiments with virtual machines with Ubuntu-20.04 at a
  german cloud provider (Hetzner), who uses cloud-init to initialize
  machines with a basic setup such as ip and ssh access.

  During my installation tests I had to reboot the virtual machines
  several times after installing or removing packages.

  Occassionally (not always) I noticed that the ssh host keys have
  changed, ssh complained. After accepting the new host keys (insecure!)
  I found, that all key files in /etc/ssh had fresh mod times, i.e. were
  freshly regenerated.

  This reminds me to a bug I had reported about cloud-init some time
  ago, where I could not change the host name permanently, because
  cloud-init reset it to it's initial configuration at every boot time
  (highly dangerous, because it seemed to reset passwords to their
  original state as well.

  Although cloud-init is intended to do an initial configuration for the
  first boot only, it seems to remain on the system and – even worse:
  occasionally – change configurations.

  I've never understood what's the purpose of cloud-init remaining
  active once after the machine is up and running.

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