Multi-node with MAAS, machine is missing disks

Bug #2065211 reported by Chris Johnston
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Snap
Triaged
Undecided
Unassigned

Bug Description

Running the openstack 2024.1/edge snap for a multi-node with MAAS deployment results in:

Error: Machine 'microceph/0' is missing disks: {'/dev/disk/by-id/usb-PNY_USB_3.0_FD_AA611F2650000004-0:0'}

Currently the manifest is deploying microceph reef/edge, rev 32.

If I manually list the disks, the microceph snap responds appropriately:

$ juju ssh -m openstack-machines microceph/0 "sudo microceph disk list --json"
{"ConfiguredDisks":[],"AvailableDisks":[{"Model":"USB 3.0 FD","Size":"30.77GiB","Type":"usb","Path":"/dev/disk/by-id/usb-PNY_USB_3.0_FD_AA611F2650000004-0:0"}]}
Connection to 192.168.100.140 closed.

If I run the microceph charm list-disks action, it returns empty:

$ juju run -m openstack-machines microceph/0 list-disks
Running operation 13 with 1 task
  - task 14 on unit-microceph-0

Waiting for task 14...
osds: '[]'
unpartitioned-disks: '[]'

{'osds': [], 'unpartitioned-disks': []}

If I change the manifest to use the microceph latest/edge (r47) charm things seem to work as expected:

$ juju run -m openstack-machines microceph/0 list-disks
Running operation 21 with 1 task
  - task 22 on unit-microceph-0

Waiting for task 22...
osds: '[{''osd'': 1, ''path'': ''/dev/disk/by-id/usb-PNY_USB_3.0_FD_AA611F2650000004-0:0'',
  ''location'': ''lab02''}, {''osd'': 2, ''path'': ''/dev/disk/by-id/usb-PNY_USB_3.0_FD_AA620120F0013819-0:0'',
  ''location'': ''lab03''}, {''osd'': 3, ''path'': ''/dev/disk/by-id/usb-PNY_USB_3.0_FD_AA62012390000030-0:0'',
  ''location'': ''lab04''}]'
unpartitioned-disks: '[]'

Revision history for this message
Hemanth Nakkina (hemanth-n) wrote :

Seems to be similar symtpoms as https://bugs.launchpad.net/snap-openstack/+bug/2065470.
Need to wait for next reef/candidate release.

Changed in snap-openstack:
status: New → Triaged
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.