Services tied to cloud-init are failing: AttributeError: module 'cloudinit.log' has no attribute 'getLogger'

Applicable to:

• Plesk for Linux

Symptoms

• Plesk Obsidian running on Ubuntu operating system, which resides on a virtual server provided by IONOS.

• The systemctl status cloud-config.service,  systemctl status cloud-init.service and systemctl status systemd-networkd-wait-online.service are returning errors that are similar to the following:

  # systemctl status cloud-init.service
  × cloud-init.service - Initial cloud-init job (metadata service crawler) 
  Active: failed (Result: exit-code)
  ... 
  AttributeError: module 'cloudinit.log' has no attribute 'getLogger' 
  Failed to start Initial cloud-init job (metadata service crawler).

  # systemctl status cloud-config.service
  × cloud-config.service - Apply the settings specified in cloud-config 
  Active: failed (Result: exit-code)
  ... 
  AttributeError: module 'cloudinit.log' has no attribute 'getLogger' 
  Failed to start Apply the settings specified in cloud-config.

  # systemctl status systemd-networkd-wait-online.service
  × systemd-networkd-wait-online.service - Wait for Network to be Configured 
  Active: failed (Result: exit-code) 
  ... 
  Timeout occurred while waiting for network connectivity. Failed to start Wait for Network to be Configured.

• Websites on the server are intermittently inaccessible, cycling between roughly 30 minutes of uptime and 30 minutes of downtime.

Cause

The errors are unrelated to Plesk. They stem from the virtual machine configuration that IONOS applies during VM creation via cloud-init. Since the network configuration service is among those affected, the intermittent website unavailability is a direct result of these failures.

Further details can be found here:

• Bug #2055770 “AttributeError: module 'cloudinit.log' has no attr...” : Bugs : cloud-init package : Ubuntu

Resolution

The best approach is contacting your server provider (IONOS) in order to assist with such issues, as Plesk does not manage or alter any of these services. When reaching out, provide them with the failing service names, the error output from the Symptoms section above, and reference to Bug #2055770 on the Ubuntu Launchpad tracker.