Running zap-disk action with devices separated by more then one space dies with an unhelpful error message

Bug #1930218 reported by Peter Sabaini
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ceph OSD Charm
In Progress
Undecided
Peter Sabaini

Bug Description

Running zap-disk with:

juju run-action --wait ceph-osd/48 zap-disk devices='/dev/disk/by-dname/bcache-sdb /dev/disk/by-dname/bcache-sdc /dev/disk/by-dname/bcache-sdd' i-really-mean-it=True

This dies with:

2021-05-31 09:23:09 DEBUG zap-disk Traceback (most recent call last):
2021-05-31 09:23:09 DEBUG zap-disk File "/var/lib/juju/agents/unit-ceph-osd-48/charm/actions/zap-disk", line 94, in <module>
2021-05-31 09:23:09 DEBUG zap-disk zap()
2021-05-31 09:23:09 DEBUG zap-disk File "/var/lib/juju/agents/unit-ceph-osd-48/charm/actions/zap-disk", line 53, in zap
2021-05-31 09:23:09 DEBUG zap-disk devices = get_devices()
2021-05-31 09:23:09 DEBUG zap-disk File "/var/lib/juju/agents/unit-ceph-osd-48/charm/actions/zap-disk", line 41, in get_devices
2021-05-31 09:23:09 DEBUG zap-disk raise
2021-05-31 09:23:09 DEBUG zap-disk RuntimeError: No active exception to reraise

This is due to the action not handling the two consecutive whitespaces in the args

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-ceph-osd (master)
Changed in charm-ceph-osd:
status: New → In Progress
Revision history for this message
Peter Sabaini (peter-sabaini) wrote :

PS.: on master I can see the faulty exception raise was already fixed, so the error message is already a bit more helpful

Changed in charm-ceph-osd:
assignee: nobody → Peter Sabaini (peter-sabaini)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-ceph-osd (master)

Change abandoned by "Chris MacNaughton <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/charm-ceph-osd/+/793812
Reason: Closing this review as it has updates requested for over a year and no updates submitted.

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.