Can't use new dname on trusty deployed systems following renaming on maas UI
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
New
|
Undecided
|
Unassigned | ||
curtin |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I renamed sdi, sdj disks to sda and sdaa, and renamed sda disk to sdi in maas, but since curtin does not create a dname device that I can use, I am relying on /dev/sd<> name which won't work for our tests. They will be accessing disks sdb till the last available disk. So, the boot disk sdi will end up as designated storage.
From maas UI:
-------
Storage
Storage configuration cannot be modified unless the node is Ready or Allocated.
File systems
NameSizeMountpo
sda-part1120.0 GB/ext4
Available disks and partitions
Name Model Serial BootSizeDevice TypeFile systemTags
sdaa
120.0 GB Physical ssd sata
sdb
500.1 GB Physical rotary removable
sdc
500.1 GB Physical rotary removable
sdd
500.1 GB Physical rotary removable
sde
500.1 GB Physical rotary removable
sdf
500.1 GB Physical rotary removable
sdg
500.1 GB Physical rotary removable
sdh
500.1 GB Physical rotary removable
sdi
500.1 GB Physical rotary removable
-------
From system:
-------
ubuntu@janney:~$ ls /dev/sd*
/dev/sda /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdi1 /dev/sdj
ubuntu@janney:~$ sudo bash
root@janney:~# mount
/dev/sdi1 on / type ext4 (rw)
proc on /proc type proc (rw,noexec,
sysfs on /sys type sysfs (rw,noexec,
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,
tmpfs on /run type tmpfs (rw,noexec,
none on /run/lock type tmpfs (rw,noexec,
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,
none on /sys/fs/pstore type pstore (rw)
cgroup on /sys/fs/
systemd on /sys/fs/
ubuntu@
total 0
drwxr-xr-x 2 root root 480 Jun 10 20:10 by-id
drwxr-xr-x 2 root root 200 Jun 10 20:10 by-path
drwxr-xr-x 2 root root 60 Jun 10 20:10 by-uuid
ubuntu@
-------
ubuntu@
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 1.9.3+bzr4577-
ii maas-cli 1.9.3+bzr4577-
ii maas-cluster-
ii maas-common 1.9.3+bzr4577-
ii maas-dhcp 1.9.3+bzr4577-
ii maas-dns 1.9.3+bzr4577-
ii maas-proxy 1.9.3+bzr4577-
ii maas-region-
ii maas-region-
ii python-django-maas 1.9.3+bzr4577-
ii python-maas-client 1.9.3+bzr4577-
ii python-
ubuntu@
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii curtin 0.1.0~bzr385-
ii curtin-common 0.1.0~bzr385-
ii python-curtin 0.1.0~bzr385-
ii python3-curtin 0.1.0~bzr385-
ubuntu@
summary: |
- disks not renamed on deployed systems following renaming on maas UI + Can't use new dname on deployed systems following renaming on maas UI |
summary: |
- Can't use new dname on deployed systems following renaming on maas UI + Can't use new dname on trusty deployed systems following renaming on + maas UI |
There's no such thing as "rename" a block device in curtin.