cloud-init-generator hardcodes path to ds-identify

Bug #1833264 reported by Ryan Harper on 2019-06-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

On systemd systems, the cloud-init-generator uses the ds-identify program and hardcodes the path to the program. The value is correct for Ubuntu/Debian and other systems, however on centos-based systems, ds-identify is installed down libexec path.

Related branches

Ryan Harper (raharper) wrote :

This generally isn't an issue for existing Centos 6/7 systems as they don't use systemd to start cloud-init; however on newer releases RHEL8/Centos8/Fedora29+ this is broken.

Ryan Harper (raharper) on 2019-06-18
Changed in cloud-init:
status: New → In Progress

This bug is fixed with commit e1795a5c to cloud-init on branch master.
To view that commit see the following URL:

Changed in cloud-init:
status: In Progress → Fix Committed

This bug is believed to be fixed in cloud-init in version 19.2. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in cloud-init:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers