Today I was able to test Queens+Bionic for the first time in about 2
weeks, without being roadblocked by bugs, Due to a resource constraint
in hardware i was only giving one host. I decided to deploy opentack-on-
lxd which uses the same bits as a multi-node deployment.
ubuntu@alekhin:~/openstack-on-lxd$ openstack volume list
+--------------------------------------+---------+-----------+------+-------------+
| ID | Name | Status | Size | Attached
to |
+--------------------------------------+---------+-----------+------+-------------+
| 27ceef74-3746-48eb-88e0-6a3bf1a97dd6 | volume1 | available | 10 |
|
+--------------------------------------+---------+-----------+------+-------------+
ubuntu@alekhin:~/openstack-on-lxd$ openstack server list
+--------------------------------------+---------------+--------+-------------------------------------+--------+----------+
| ID | Name | Status | Networks
| Image | Flavor |
+--------------------------------------+---------------+--------+-------------------------------------+--------+----------+
| 4411c938-8a58-4a86-b666-a0e7d041e3f8 | sfeole-bionic | ACTIVE |
internal=192.168.20.7, 10.228.22.34 | bionic | m1.small |
+--------------------------------------+---------------+--------+-------------------------------------+--------+----------+
ubuntu@alekhin:~/openstack-on-lxd$ openstack hypervisor list
+----+---------------------+-----------------+---------------+-------+
| ID | Hypervisor Hostname | Hypervisor Type | Host IP | State |
+----+---------------------+-----------------+---------------+-------+
| 1 | juju-ac9015-20.lxd | QEMU | 10.228.22.203 | up |
+----+---------------------+-----------------+---------------+-------+
On the instance we can see that only the root disk is available.
ubuntu@sfeole-bionic:~$ sudo fdisk -l
Disk /dev/vda: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4A7C8D71-AC27-4899-89D8-213EAB291FB6
Device Start End Sectors Size Type
/dev/vda1 206848 20971486 20764639 9.9G Linux filesystem
/dev/vda15 2048 204800 202753 99M EFI System
Partition table entries are not in disk order.
ubuntu@sfeole-bionic:~$ sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 252:0 0 10G 0 disk
├─vda1 252:1 0 9.9G 0 part /
└─vda15 252:15 0 99M 0 part /boot/efi
If then attached the volume to the live-running instance,
ubuntu@alekhin:~/openstack-on-lxd$ openstack server add volume sfeole-bionic
volume1
ubuntu@alekhin:~/openstack-on-lxd$ openstack volume list
+--------------------------------------+---------+--------+------+----------------------------------------+
| ID | Name | Status | Size | Attached to
|
+--------------------------------------+---------+--------+------+----------------------------------------+
| 27ceef74-3746-48eb-88e0-6a3bf1a97dd6 | volume1 | in-use | 10 | Attached to
sfeole-bionic on /dev/vdb |
+--------------------------------------+---------+--------+------+----------------------------------------+
On the instance we now see the disks attached,
ubuntu@sfeole-bionic:~$ sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 252:0 0 10G 0 disk
├─vda1 252:1 0 9.9G 0 part /
└─vda15 252:15 0 99M 0 part /boot/efi
vdb 252:16 0 10G 0 disk <~~~~~~~~~~~~~~~~
ubuntu@sfeole-bionic:~$ sudo fdisk -l
Disk /dev/vda: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4A7C8D71-AC27-4899-89D8-213EAB291FB6
Device Start End Sectors Size Type
/dev/vda1 206848 20971486 20764639 9.9G Linux filesystem
/dev/vda15 2048 204800 202753 99M EFI System
Partition table entries are not in disk order.
Disk /dev/vdb: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
And we can mount / format and write to the volume.
ubuntu@sfeole-bionic:~$ sudo mke2fs /dev/vdb
mke2fs 1.44.1 (24-Mar-2018)
Creating filesystem with 2621440 4k blocks and 655360 inodes
Filesystem UUID: 96bcf8d5-31f9-43a3-b663-95202c4b00aa
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
ubuntu@sfeole-bionic:~$ sudo mount /dev/vdb /mnt/newdisk
ubuntu@sfeole-bionic:/mnt/newdisk$ sudo mkdir foo
ubuntu@sfeole-bionic:/mnt/newdisk$ sudo touch foo/bar.txt
ubuntu@sfeole-bionic:/mnt/newdisk$ ls -la
total 28
drwxr-xr-x 4 root root 4096 May 17 18:54 .
drwxr-xr-x 3 root root 4096 May 17 18:52 ..
drwxr-xr-x 2 root root 4096 May 17 18:55 foo
drwx------ 2 root root 16384 May 17 18:53 lost+found
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Sean Feole (sfeole)
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664737
Title:
[ARM] : Unable to use Cinder volumes on ARM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1664737/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
