Thanks for the test instance! Yeah, even though the resize is successful, we don't want tracebacks, warnings or degraded boot! (Also, I haven't checked, but I imagine this would cause functional issues if there was more than a single disk/partition that needed resizing; I expect we would resize the first only.)
Looking at the test instance, the by-partuuid symlinks are created after we hit this error:
That said, those timestamps are _so_ far after the error (~28s) that I _guess_ they were regenerated again. (It's also possible that nothing poked udev for that long, I suppose.)
Toby, if I give you a patched cloud-init in a PPA, would you be able to build a test image from it?
Thanks for the test instance! Yeah, even though the resize is successful, we don't want tracebacks, warnings or degraded boot! (Also, I haven't checked, but I imagine this would cause functional issues if there was more than a single disk/partition that needed resizing; I expect we would resize the first only.)
Looking at the test instance, the by-partuuid symlinks are created after we hit this error:
$ ls -l --time- style=full- iso /dev/disk/ by-partuuid/ 0763-4a42- b688-5d7c32604a 99 -> ../../sda14 a450-4661- ad65-fbe719c872 b0 -> ../../sda15 8c8c-434b- bb30-f80882728e 23 -> ../../sda1
total 0
lrwxrwxrwx 1 root root 10 2019-07-03 11:39:34.578632000 +0000 251ca684-01 -> ../../sdb1
lrwxrwxrwx 1 root root 11 2019-07-03 11:39:34.718632000 +0000 46150cea-
lrwxrwxrwx 1 root root 11 2019-07-03 11:39:34.674632000 +0000 76944892-
lrwxrwxrwx 1 root root 10 2019-07-03 11:39:34.698632000 +0000 b429205c-
That said, those timestamps are _so_ far after the error (~28s) that I _guess_ they were regenerated again. (It's also possible that nothing poked udev for that long, I suppose.)
Toby, if I give you a patched cloud-init in a PPA, would you be able to build a test image from it?