cloud-init

ds-identify uses the /sys filesystem which is linux specific and non-portable

Bug #1852442 reported by Mina Galić
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Fix Released
Undecided
Unassigned

Bug Description

On FreeBSD, /sys is a convenient link to /usr/src/sys; the kernel source code.

Especially for the DMI_ info, we should probably look into using `dmidecode` which at least on FreeBSD we already pull in as dependency:

    root@container-host-02:~ # pkg info -r dmidecode
    dmidecode-3.2:
     py36-cloud-init-19.2

The only problem i see is that many names don't map nicely.
For instance, sys_vendor is (either bios-vendor or) system-manufacturer.

Revision history for this message
Scott Moser (smoser) wrote :

pull request at
https://github.com/canonical/cloud-init/pull/42

Paride Legovini (paride)
Changed in cloud-init:
status: New → Triaged
Revision history for this message
Chad Smith (chad.smith) wrote : Fixed in cloud-init version 19.4.

This bug is believed to be fixed in cloud-init in version 19.4. 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: Triaged → Fix Released
Revision history for this message
James Falcon (falcojr) wrote :

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/3494

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.