Reviewed: https://review.openstack.org/329403
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=d442c1aa31b0a0cbfa0d057e8b6574002ee2e2fc
Submitter: Jenkins
Branch: master
commit d442c1aa31b0a0cbfa0d057e8b6574002ee2e2fc
Author: KevinZhao <kevin.z...@linaro.org>
Date: Mon Jun 13 02:14:51 2016 +0000
libvirt: Delete the lase_device of find_disk_dev_for_disk_bus
Delete the last_device parameters of find_disk_dev_for_disk_bus.
Just pick the first available letter on the bus as the device,
instead of hardcoding on the last device for config drive. Also
tweak the test case for this.
Closes-bug: #1591827
Change-Id: I6343d7ab6f1b0aa58f29805e24db7e2c61d1409e
Signed-off-by: Kevin Zhao <kevin.z...@linaro.org>
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1591827
Title:
Scsi device can't be recognized in Guest in aarch64
Status in OpenStack Compute (nova):
Fix Released
Bug description:
Description
===========
Using nova to create an instance in Aarch64,the disk.config is the 'cdrom'
and has the type of 'scsi'.After instance creation ,log into the instance and
can't see the cdrom device.
Steps to reproduce
==================
1.Using devstack to deploy openstack. Using default local.conf.
2.Upload the aarch64 image with glance.
$ source ~/devstack/openrc admin admin
$ glance image-create --name image-arm64.img --disk-format qcow2
--container-format bare --visibility public --file
images/image-arm64-wily.qcow2 --progress
$ glance image-create --name image-arm64.vmlinuz --disk-format aki
--container-format aki --visibility public --file
images/image-arm64-wily.vmlinuz --progress
$ glance image-create --name image-arm64.initrd --disk-format ari
--container-format ari --visibility public --file
images/image-arm64-wily.initrd --progress
$ IMAGE_UUID=$(glance image-list | grep image-arm64.img | awk '{ print $2 }')
$ IMAGE_KERNEL_UUID=$(glance image-list | grep image-arm64.vmlinuz | awk '{
print $2 }')
$ IMAGE_INITRD_UUID=$(glance image-list | grep image-arm64.initrd | awk '{
print $2 }')
$ glance image-update --kernel-id ${IMAGE_KERNEL_UUID} --ramdisk-id
${IMAGE_INITRD_UUID} ${IMAGE_UUID}
3.Set the scsi model:
$ glance image-update --property hw_disk_bus --property
hw_scsi_model=virtio-scsi ${IMAGE_UUID}
4.nova add keypair
$ nova keypair-add default --pub-key ~/.ssh/id_rsa.pub
5.Launch the instance:
$ image=$(nova image-list | egrep "image-arm64.img"'[^-]' | awk '{ print $2
}')
$ nova boot --flavor m1.small--image ${image} --key-name default test-arm64
6.After creation,use ssh to login into the instance.In the guest:
$ ls -l /dev
The we can see that cdrom doesn't exist.
Expected result
===============
After spawningn the instance, login into the guest :
$ ls -l /dev
We can see the cdrom is here.
Actual result
=============
The xml file of the disk.config is generated by nova ,but can't work.
Environment
===========
1. Exact version of OpenStack you are running. See the following
list for all releases: http://docs.openstack.org/releases/
Nova development, commit code: 279f1a9bf65c4b904e01d26f0619a62ed99fc4d3
2. Which hypervisor did you use?
Libvirt+KVM
$ kvm --version
QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.1), Copyright
(c) 2003-2008 Fabrice Bellard
$ libvirtd --version
libvirtd (libvirt) 1.3.1
2. Which storage type did you use?
In the host file system,all in one physics machine.
stack@u202154:/opt/stack/nova$ df -hl
Filesystem Size Used Avail Use% Mounted on
udev 7.8G 0 7.8G 0% /dev
tmpfs 1.6G 61M 1.6G 4% /run
/dev/sda2 917G 41G 830G 5% /
tmpfs 7.9G 0 7.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
/dev/sda1 511M 888K 511M 1% /boot/efi
cgmfs 100K 0 100K 0% /run/cgmanager/fs
tmpfs 1.6G 0 1.6G 0% /run/user/1002
tmpfs 1.6G 0 1.6G 0% /run/user/1000
tmpfs 1.6G 0 1.6G 0% /run/user/0
3. Which networking type did you use?
nova-network
4. Environment information:
Architecture : AARCH64
OS: Ubuntu 16.04
Detailed log info is in the accessory.
The guest xml is also in the log info.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1591827/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
