Device Path Pattern for Block Devices Rejects Legitimate Paths
Bug #1830326 reported by
Joseph Phillips
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Harry Pidcock |
Bug Description
The following log output was observed while working to resolve an unrelated issue:
https:/
The regular expression that designates a valid device path expects only the device name in the final segment - in this example that would mean "sdn1" instead of "sdn/sdn1".
This doesn't appear to be an error condition - the device path is simply not stored in state against the device. It should be fixed though.
Changed in juju: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in juju: | |
assignee: | nobody → Harry Pidcock (hpidcock) |
milestone: | none → 2.7-beta1 |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
milestone: | 2.7-beta1 → 2.6.10 |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Happens with the OCI provider too:
machine-0: 10:29:11 DEBUG juju.worker. diskmanager non matching DEVPATH for "sda1": "/devices/ pci0000: 00/0000: 00:04.0/ virtio0/ host2/target2: 0:0/2:0: 0:1/block/ sda/sda1" diskmanager non matching DEVPATH for "sda14": "/devices/ pci0000: 00/0000: 00:04.0/ virtio0/ host2/target2: 0:0/2:0: 0:1/block/ sda/sda14" diskmanager non matching DEVPATH for "sda15": "/devices/ pci0000: 00/0000: 00:04.0/ virtio0/ host2/target2: 0:0/2:0: 0:1/block/ sda/sda15"
machine-0: 10:29:11 DEBUG juju.worker.
machine-0: 10:29:11 DEBUG juju.worker.