ds-identify cannot identify disk-based resources on FreeBSD

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

Bug Description

Following https://github.com/canonical/cloud-init/pull/617
i tried to replicate this on my laptop.

In a FreeBSD 12, there is no `blkid`. That means that the NoCloud seed image, which was provided as iso9660 formatted disk with the label 'cidata' was not found.
The equivalent tool on FreeBSD to find disks and their labels would be `geom`:

```
meena@fbsd12-1 /u/h/meena> geom label status -a
          Name Status Components
  gpt/gptboot0 N/A vtbd1p1
     gpt/swap0 N/A vtbd1p2
iso9660/cidata N/A vtbd2
```

and here, in -s for script-friendly output:

```
meena@fbsd12-1 /u/h/meena> geom label status -as
  gpt/gptboot0 N/A vtbd1p1
     gpt/swap0 N/A vtbd1p2
iso9660/cidata N/A vtbd2
```

where we have type/label followed by status and and then device name (a partition or slice)

We should change read_fs_info() to call a `blkid` or `geom` parser function based on which OS we're on.

Mina Galić (minagalic)
description: updated
description: updated
Revision history for this message
Paride Legovini (paride) wrote :
Changed in cloud-init:
status: New → In Progress
Revision history for this message
James Falcon (falcojr) wrote :
Changed in cloud-init:
status: In Progress → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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