Comment 15 for bug 1778033

machine-115.log is logging about a non matching path for the partitions sdn{1,2,3} and sdn{1,2,3}[0] which according to lsblk[1] they are used to build a raid, specifically:

sdn1 -> used for '/boot/efi'
sdo1 -> unused
sdn2 + sdo2 -> md0 used for '/boot'
sdn3 + sdo3 -> md1 used for '/'

The debug message "non matching DEVPATH for ..."[2] doesn't look like it's related to the stuck state of the hooks, because it's simply indicating that a scsi path couldn't be found based on the device name.

The reason why the DEVPATH message is being printed over and over again giving the idea juju is stuck it's because this is part of the diskmanager worker which polls disks every 30 seconds[3]

The sequence of calls is:

diskmanager worker every 30 secs:
-> listBlockDevices()
-> addHardwareInfo()
-> logger.Debugf("non matching DEVPATH for %q: %q", dev.DeviceName, devpath)

[0] $ grep DEVPATH machine-115.log | awk -F' ' '{print $10}' | sort | uniq | cut -d'"' -f2
sdn1
sdn2
sdn3
sdo1
sdo2
sdo3
[1] NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdf 8:80 0 1.5T 0 disk
sdo 8:224 0 222.6G 0 disk
|-sdo3 8:227 0 204.9G 0 part
| `-md1 9:1 0 204.8G 0 raid1 /
|-sdo1 8:225 0 96M 0 part
`-sdo2 8:226 0 500M 0 part
`-md0 9:0 0 499.7M 0 raid1 /boot
sdd 8:48 0 1.5T 0 disk
sdm 8:192 0 1.5T 0 disk
sdb 8:16 0 1.5T 0 disk
sdk 8:160 0 1.5T 0 disk
sdi 8:128 0 1.5T 0 disk
sdg 8:96 0 1.5T 0 disk
sde 8:64 0 1.5T 0 disk
sdn 8:208 0 222.6G 0 disk
|-sdn3 8:211 0 204.9G 0 part
| `-md1 9:1 0 204.8G 0 raid1 /
|-sdn1 8:209 0 96M 0 part /boot/efi
`-sdn2 8:210 0 500M 0 part
`-md0 9:0 0 499.7M 0 raid1 /boot
sdc 8:32 0 1.5T 0 disk
sdl 8:176 0 1.5T 0 disk
sda 8:0 0 1.5T 0 disk
sdj 8:144 0 1.5T 0 disk
sdh 8:112 0 1.5T 0 disk
[2] https://github.com/juju/juju/blob/2.3/worker/diskmanager/lsblk.go#L228-L252
[3] https://github.com/juju/juju/blob/2.3/worker/diskmanager/diskmanager.go#L24