On Thu, Feb 1, 2018 at 4:09 PM, Dmitrii Shcherbakov <
<email address hidden>> wrote:
> Ryan,
>
> I did have a PPA added via MAAS though.
>
> I looked at /lib/udev/rules.d which was incorrect - should have looked
> at /etc/udev/rules.d.
>
> Now, with an entry in MAAS and in curtin_userdata as well:
>
> https://paste.ubuntu.com/26502622/
>
> root@maas-xenial2:~# apt policy bcache-tools
> bcache-tools:
> Installed: 1.0.8-2ubuntu2~ppa3
> Candidate: 1.0.8-2ubuntu2~ppa3
> Version table:
> *** 1.0.8-2ubuntu2~ppa3 500
> 500 http://ppa.launchpad.net/raharper/bugfixes/ubuntu xenial/main
> amd64 Packages
>
> ...
> dev.label (empty)
> ...
>
> root@maas-xenial2:~# cat /etc/udev/rules.d/bcache0.rules.rules
> SUBSYSTEM=="block", ACTION=="add|change", ENV{DEVNAME}=="/dev/bcache0",
> SYMLINK+="disk/by-dname/bcache0"
>
> So, it seems like a dname symlink -> UUID symlink was not created. The
> /dev/bcache/by-uuid rules are there.
>
> I did try a manual label writing test based on the kernel code - a written
> label seems to persist after reboot.
> https://paste.ubuntu.com/26502649/
>
> So something tells me that I simply did not get the new *curtin* code.
>
Yes, you need the updated curtin installed, I *think* to the region
controllers; I'm not sure.
The updated curtin includes the new rule format that uses the CACHED_UUID
value from the
backing device (as well as updating the backing device label).
>
> https://paste.ubuntu.com/26502671/ (curtin-install-cfg.yaml)
>
> I will poke around more in the morning - any ideas are appreciated.
>
> Also, thx for working on this.
>
On Thu, Feb 1, 2018 at 4:09 PM, Dmitrii Shcherbakov <
<email address hidden>> wrote:
> Ryan, /paste. ubuntu. com/26502622/ xenial2: ~# apt policy bcache-tools ppa.launchpad. net/raharper/ bugfixes/ ubuntu xenial/main xenial2: ~# cat /etc/udev/ rules.d/ bcache0. rules.rules ="add|change" , ENV{DEVNAME} =="/dev/ bcache0" , ="disk/ by-dname/ bcache0" /paste. ubuntu. com/26502649/
>
> I did have a PPA added via MAAS though.
>
> I looked at /lib/udev/rules.d which was incorrect - should have looked
> at /etc/udev/rules.d.
>
> Now, with an entry in MAAS and in curtin_userdata as well:
>
> https:/
>
> root@maas-
> bcache-tools:
> Installed: 1.0.8-2ubuntu2~ppa3
> Candidate: 1.0.8-2ubuntu2~ppa3
> Version table:
> *** 1.0.8-2ubuntu2~ppa3 500
> 500 http://
> amd64 Packages
>
> ...
> dev.label (empty)
> ...
>
> root@maas-
> SUBSYSTEM=="block", ACTION=
> SYMLINK+
>
> So, it seems like a dname symlink -> UUID symlink was not created. The
> /dev/bcache/by-uuid rules are there.
>
> I did try a manual label writing test based on the kernel code - a written
> label seems to persist after reboot.
> https:/
>
> So something tells me that I simply did not get the new *curtin* code.
>
Yes, you need the updated curtin installed, I *think* to the region
controllers; I'm not sure.
The updated curtin includes the new rule format that uses the CACHED_UUID
value from the
backing device (as well as updating the backing device label).
> /paste. ubuntu. com/26502671/ (curtin- install- cfg.yaml)
> https:/
>
> I will poke around more in the morning - any ideas are appreciated.
>
> Also, thx for working on this.
>
Sure
> /bugs.launchpad .net/bugs/ 1728742 /bugs.launchpad .net/bcache- tools/+ bug/1728742/ +subscriptions
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> curtin dname for bcache uses unstable devname instead of UUID
>
> To manage notifications about this bug go to:
> https:/
>