[openstack-dev] failed to load customised image
Hi All, I want to upload my customised rootfs and kernel image for powerpc to the openstack database. For this I followed the following document: http://docs.openstack.org/grizzly/openstack-compute/admin/content/creating-custom-images.html#d6e6473 I followed the following steps as described in the document: 1. copied the kernel and rootfs for powerpc on the Openstack controller. kernel-image - uImage rootfs - guest.rootfs.ext2.gz 2. sudo tune2fs -L uec-rootfs serverfinal.img 3.when i tried to upload the images to the openstack image service using the following commad: cloud-publish-image -t image --kernel-file uImage --ramdisk-file guest.rootfs.ext2.gz ppc64 disk.img bucket1 i got the following error: failed to check for existing manifest failed to register uImage Please help me regarding this. Thanks Sonia ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Ironic] no team meeting this monday
Hi Devananda Can you please help regarding my openstack issue? On Sat, May 17, 2014 at 6:44 PM, Devananda van der Veen < devananda@gmail.com> wrote: > Since many folks are flying home this weekend, and will probably need a > few days to recover from the conference, we're going to skip this Monday's > meeting. > > We all got a lot of design and planning done during the week, so stay > tuned to the mailing list for some discussions/announcements! > > Regards, > Devananda > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] nova compute repeating logs
Hi I'm trying to boot VM from my controller node(openstack dashboard) onto compute node but it is stucking at spawning state. I'm able to see the VM interface onto the compute but the status is spawning even after 10-15 minutes. Below are the nova schedular logs.. ova/openstack/common/loopingcall.py:130^M 2014-05-16 16:02:16.581 13421 DEBUG nova.openstack.common.periodic_task [-] Running periodic task SchedulerManager._expire_reservations run_periodic_tasks /opt/stack/nova/nova/openstack/common/periodic_task.py:178^M 2014-05-16 16:02:16.588 13421 DEBUG nova.openstack.common.periodic_task [-] Running periodic task SchedulerManager._run_periodic_tasks run_periodic_tasks /opt/stack/nova/nova/openstack/common/periodic_task.py:178^M 2014-05-16 16:02:16.589 13421 DEBUG nova.openstack.common.loopingcall [-] Dynamic looping call sleeping for 60.00 seconds _inner /opt/stack/nova/nova/openstack/common/loopingcall.py:130^M 2014-05-16 16:03:16.593 13421 DEBUG nova.openstack.common.periodic_task [-] Running periodic task SchedulerManager._expire_reservations run_periodic_tasks /opt/stack/nova/nova/openstack/common/periodic_task.py:178^M 2014-05-16 16:03:16.600 13421 DEBUG nova.openstack.common.periodic_task [-] Running periodic task SchedulerManager._run_periodic_tasks run_periodic_tasks /opt/stack/nova/nova/openstack/common/periodic_task.py:178^M 2014-05-16 16:03:16.601 13421 DEBUG nova.openstack.common.loopingcall [-] Dynamic looping call sleeping for 60.00 seconds _inner /opt/stack/nova/nova/openstack/common/loopingcall.py:130^M Also my nova-compute logs at the compute node are repeating continuesly.Below are the logs. -05-16 05:34:19.503 26935 DEBUG nova.openstack.common.periodic_task [-] Running periodic task ComputeManager._poll_volume_usage run_periodic_tasks /opt/stack/nova/nova/openstack/common/periodic_task.py:176^M 2014-05-16 05:34:19.504 26935 DEBUG nova.openstack.common.periodic_task [-] Running periodic task ComputeManager._instance_usage_audit run_periodic_tasks /opt/stack/nova/nova/openstack/common/periodic_task.py:176^M 2014-05-16 05:34:19.504 26935 DEBUG nova.openstack.common.periodic_task [-] Running periodic task ComputeManager.update_available_resource run_periodic_tasks /opt/stack/nova/nova/openstack/common/periodic_task.py:176^M 2014-05-16 05:34:19.505 26935 DEBUG nova.openstack.common.lockutils [-] Got semaphore "compute_resources" lock /opt/stack/nova/nova/openstack/common/lockutils.py:166^M 2014-05-16 05:34:19.505 26935 DEBUG nova.openstack.common.lockutils [-] Got semaphore / lock "update_available_resource" inner /opt/stack/nova/nova/openstack/common/lockutils.py:245^M 2014-05-16 05:34:19.505 26935 AUDIT nova.compute.resource_tracker [-] Auditing locally available compute resources^M 2014-05-16 05:34:19.506 26935 DEBUG nova.virt.libvirt.driver [-] Updating host stats update_status /opt/stack/nova/nova/virt/libvirt/driver.py:4865^M 2014-05-16 05:34:19.566 26935 DEBUG nova.openstack.common.processutils [-] Running cmd (subprocess): env LC_ALL=C LANG=C qemu-img info /opt/stack/data/nova/instances/961b0fcd-60e3-488f-93df-5b852d93ede2/disk execute /opt/stack/nova/nova/openstack/common/processutils.py:147^M 2014-05-16 05:34:19.612 26935 DEBUG nova.openstack.common.processutils [-] Running cmd (subprocess): env LC_ALL=C LANG=C qemu-img info /opt/stack/data/nova/instances/961b0fcd-60e3-488f-93df-5b852d93ede2/disk execute /opt/stack/nova/nova/openstack/common/processutils.py:147^M 2014-05-16 05:34:19.703 26935 DEBUG nova.compute.resource_tracker [-] Hypervisor: free ram (MB): 5565 _report_hypervisor_resource_view /opt/stack/nova/nova/compute/resource_tracker.py:388^M 2014-05-16 05:34:19.705 26935 DEBUG nova.compute.resource_tracker [-] Hypervisor: free disk (GB): 95 _report_hypervisor_resource_view /opt/stack/nova/nova/compute/resource_tracker.py:389^M 2014-05-16 05:34:19.705 26935 DEBUG nova.compute.resource_tracker [-] Hypervisor: free VCPUs: 24 _report_hypervisor_resource_view /opt/stack/nova/nova/compute/resource_tracker.py:394^M 2014-05-16 05:34:19.706 26935 DEBUG nova.compute.resource_tracker [-] Hypervisor: assignable PCI devices: [] _report_hypervisor_resource_view /opt/stack/nova/nova/compute/resource_tracker.py:401^M 2014-05-16 05:34:19.708 26935 DEBUG nova.openstack.common.rpc.amqp [-] Making synchronous call on conductor ... multicall /opt/stack/nova/nova/openstack/common/rpc/amqp.py:553^M 2014-05-16 05:34:19.709 26935 DEBUG nova.openstack.common.rpc.amqp [-] MSG_ID is 7435553a261b4f3eb61f985017441333 multicall /opt/stack/nova/nova/openstack/common/rpc/amqp.py:556^M 2014-05-16 05:34:19.709 26935 DEBUG nova.openstack.common.rpc.amqp [-] UNIQUE_ID is f2dd9f9fc517406bbe82366085de5523. _add_unique_id /opt/stack/nova/nova/openstack/common/rpc/amqp.py:341^M 2014-05-16 05:34:19.716 26935 DEBUG nova.openstack.common.rpc.amqp [-] Making synchronous call on conductor ... multicall /opt/stack/nova/nova/openstack/common/rpc/amqp.py:553^M 2014-05-16 05:34:19.717 26935 DEBUG nova.openstack.common.
[openstack-dev] running VM manually using openstack
HI I have install openstack using devstack.I'm using multinode setup with one controller node and one compute node.I'm able to launch VM from openstack dashboard onto the controller node. At the controller node when i do ps -ef | grep nova,the following appears.. ps -ef | grep nova root 799 798 0 11:48 pts/22 00:00:00 sg libvirtd /usr/local/bin/nova-compute --config-file /etc/nova/nova.conf shiv 801 799 0 11:48 pts/22 00:00:55 /usr/bin/python /usr/local/bin/nova-compute --config-file /etc/nova/nova.conf shiv 1233 1232 1 11:48 pts/23 00:03:45 /usr/bin/python /usr/local/bin/nova-conductor --config-file /etc/nova/nova.conf shiv 1457 1233 0 11:48 pts/23 00:00:45 /usr/bin/python /usr/local/bin/nova-conductor --config-file /etc/nova/nova.conf shiv 1458 1233 0 11:48 pts/23 00:00:45 /usr/bin/python /usr/local/bin/nova-conductor --config-file /etc/nova/nova.conf shiv 1459 1233 0 11:48 pts/23 00:00:45 /usr/bin/python /usr/local/bin/nova-conductor --config-file /etc/nova/nova.conf shiv 1460 1233 0 11:48 pts/23 00:00:45 /usr/bin/python /usr/local/bin/nova-conductor --config-file /etc/nova/nova.conf shiv 1578 1577 0 11:48 pts/24 00:00:09 /usr/bin/python /usr/local/bin/nova-cert --config-file /etc/nova/nova.conf shiv 1880 1879 0 11:48 pts/25 00:00:10 /usr/bin/python /usr/local/bin/nova-scheduler --config-file /etc/nova/nova.conf shiv 2221 2219 0 11:48 pts/26 00:00:05 /usr/bin/python /usr/local/bin/nova-novncproxy --config-file /etc/nova/nova.conf --web /opt/stack/noVNC shiv 2431 2429 0 11:48 pts/27 00:00:00 /usr/bin/python /usr/local/bin/nova-xvpvncproxy --config-file /etc/nova/nova.conf shiv 2670 2669 0 11:48 pts/28 00:00:09 /usr/bin/python /usr/local/bin/nova-consoleauth --config-file /etc/nova/nova.conf shiv 2897 2895 0 11:48 pts/29 00:00:00 /usr/bin/python /usr/local/bin/nova-objectstore --config-file /etc/nova/nova.conf 122 13484 1 19 15:43 ?00:00:02 /usr/bin/kvm -S -M pc-1.0 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name instance-0003 -uuid cec324c7-2398-49b8-844b-08c6cca7fff3 -smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=2014.2,serial=44454c4c-5600-1039-804c-c7c04f595831,uuid=cec324c7-2398-49b8-844b-08c6cca7fff3 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-0003.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-hpet -no-shutdown -drive file=/opt/stack/data/nova/instances/cec324c7-2398-49b8-844b-08c6cca7fff3/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/opt/stack/data/nova/instances/cec324c7-2398-49b8-844b-08c6cca7fff3/disk.config,if=none,media=cdrom,id=drive-ide0-1-1,readonly=on,format=raw,cache=none -device ide-drive,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1 -netdev tap,fd=19,id=hostnet0,vhost=on,vhostfd=20 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:9b:09:3b,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/opt/stack/data/nova/instances/cec324c7-2398-49b8-844b-08c6cca7fff3/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -usb -vnc 127.0.0.1:1 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 shiv 14867 20602 0 15:43 pts/700:00:00 grep --color=auto nova shiv 31444 31443 1 11:47 pts/16 00:03:45 /usr/bin/python /usr/local/bin/nova-api shiv 31469 31444 0 11:47 pts/16 00:00:00 /usr/bin/python /usr/local/bin/nova-api shiv 31470 31444 0 11:47 pts/16 00:00:00 /usr/bin/python /usr/local/bin/nova-api shiv 31471 31444 0 11:47 pts/16 00:00:00 /usr/bin/python /usr/local/bin/nova-api I see the VM instance booted using KVM utility on to the controller node. However when i try to launch VM manually using the similar command but changing the instances id and name as above.. sudo /usr/bin/kvm -S -M pc-1.0 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name instance-0002 -uuid 3765ec4d-48d0-4f0b-9f7d-2f73ee3a3852 -smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=2014.2,serial=44454c4c-4400-1034-8042-c7c04f313032,uuid=3765ec4d-48d0-4f0b-9f7d-2f73ee3a3852 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-0002.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-hpet -no-shutdown -drive file=/opt/stack/data/nova/instances/3765ec4d-48d0-4f0b-9f7d-2f73ee3a3852/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/opt/stack/data/nova/instances/3765ec4
[openstack-dev] booting VM with customized kernel and rootfs image
Hi all I have installed openstack using devstack.I'm able able to boot VM from the opebstack dashboard onto the compute node. Now i need to boot VM from the openstack dashboard(controller node) onto compute node using customized kernel imae and rootfs. Therefore my question is whether can we boot VM from controller node onto compute node using the customized kernel and rootfs image. Please help regarding this. Thanks Sonia ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] nova compute error
Hi I'm getting foollowing error while booting VM on compute node in nova-compute service using devstack due to which the VM is stuck at spawning state.. ERROR nova.openstack.common.rpc.amqp [req-da485913-0cb2-47c1-ac61-6657361286c3 nova service] Exception during message handling [16:18:23] Abhishek Jain: Traceback (most recent call last): 2014-05-07 05:38:52.835 6754 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 461, in _process_data 2014-05-07 05:38:52.835 6754 TRACE nova.openstack.common.rpc.amqp **args) 2014-05-07 05:38:52.835 6754 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/openstack/common/rpc/dispatcher.py", line 178, in dispatch Please help regarding this.. Thanks Sonia ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] nova-compute error
Hi Thierry Thanks for help On Wed, May 7, 2014 at 1:31 PM, Thierry Carrez wrote: > sonia verma wrote: > > Hi all > > > > I'm getting following error when booting VM onto compute node from > > openstack dashboard... > > [...] > > Hi! > > This list is for future development topics only, and your question is > about debugging an issue you have using OpenStack. You shall get better > answers by asking your question on the general OpenStack mailing-list > (openst...@lists.openstack.org). > > For more information see: > https://wiki.openstack.org/wiki/Mailing_Lists > > -- > Thierry Carrez (ttx) > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] nova-compute error
Hi all I'm getting following error when booting VM onto compute node from openstack dashboard... 014-05-06 12:47:22.393 DEBUG nova.openstack.common.processutils [req-cc3cf4c6-160d-4dd4-b44d-d8f5c25fb55c admin admin] Result was 12 execute /opt/stack/nova/nova/openstack/common/processutils.py:172 2014-05-06 12:47:22.395 DEBUG nova.virt.disk.mount.api [req-cc3cf4c6-160d-4dd4-b44d-d8f5c25fb55c admin admin] Failed to mount filesystem: Unexpected error while running command. Command: sudo nova-rootwrap /etc/nova/rootwrap.conf mount /dev/nbd9 /tmp/openstack-vfs-localfsjqwQWj Exit code: 12 Stdout: '' Stderr: "Failed to read bootsector (size=0)\nFailed to mount '/dev/nbd9': Invalid argument\nThe device '/dev/nbd9' doesn't seem to have a valid NTFS.\nMaybe the wrong device is used? Or the whole disk instead of a\npartition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?\n" mnt_dev /opt/stack/nova/nova/virt/disk/mount/api.py:198 2014-05-06 12:47:22.396 DEBUG nova.virt.disk.mount.api [req-cc3cf4c6-160d-4dd4-b44d-d8f5c25fb55c admin admin] Fail to mount, tearing back down do_mount /opt/stack/nova/nova/virt/disk/mount/api.py:219 2014-05-06 12:47:22.396 DEBUG nova.virt.disk.mount.api [req-cc3cf4c6-160d-4dd4-b44d-d8f5c25fb55c admin admin] Unmap dev /dev/nbd9 unmap_dev /opt/stack/nova/nova/virt/disk/mount/api.py:184 2014-05-06 12:47:22.397 DEBUG nova.virt.disk.mount.nbd [req-cc3cf4c6-160d-4dd4-b44d-d8f5c25fb55c admin admin] Release nbd device /dev/nbd9 unget_dev /opt/stack/nova/nova/virt/disk/mount/nbd.py:129 2014-05-06 12:47:22.398 DEBUG nova.openstack.common.processutils [req-cc3cf4c6-160d-4dd4-b44d-d8f5c25fb55c admin admin] Running cmd (subprocess): sudo nova-rootwrap /etc/nova/rootwrap.conf qemu-nbd -d /dev/nbd9 execute /opt/stack/nova/nova/openstack/common/processutils.py:147 2014-05-06 12:47:22.573 DEBUG nova.virt.disk.vfs.localfs [req-cc3cf4c6-160d-4dd4-b44d-d8f5c25fb55c admin admin] Failed to mount image Failed to mount filesystem: Unexpected error while running command. Command: sudo nova-rootwrap /etc/nova/rootwrap.conf mount /dev/nbd9 /tmp/openstack-vfs-localfsjqwQWj Exit code: 12 Please help regarding this. Thanks Sonia ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] q-agt error
Hi Aaron
Thanks for the reply.
Following are the nova-compute logs...
pt/stack/nova/nova/openstack/common/processutils.py:172
2014-05-05 13:52:37.632 DEBUG nova.virt.disk.mount.api
[req-3cc7cbae-1ef2-4602-bdc8-82b50f8207c6 admin admin] Failed to mount
filesystem: Unexpected error while running command.
Command: sudo nova-rootwrap /etc/nova/rootwrap.conf mount /dev/nbd10
/tmp/openstack-vfs-localfsCn1KbQ
Exit code: 12
Stdout: ''
Stderr: "Failed to read bootsector (size=0)\nFailed to mount '/dev/nbd10':
Invalid argument\nThe device '/dev/nbd10' doesn't seem to have a valid
NTFS.\nMaybe the wrong device is used? Or the whole disk instead of
a\npartition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?\n"
mnt_dev /opt/stack/nova/nova/virt/disk/mount/api.py:198
2014-05-05 13:52:37.633 DEBUG nova.virt.disk.mount.api
[req-3cc7cbae-1ef2-4602-bdc8-82b50f8207c6 admin admin] Fail to mount,
tearing back down do_mount /opt/stack/nova/nova/virt/disk/mount/api.py:219
2014-05-05 13:52:37.633 DEBUG nova.virt.disk.mount.api
[req-3cc7cbae-1ef2-4602-bdc8-82b50f8207c6 admin admin] Unmap dev /dev/nbd10
unmap_dev /opt/stack/nova/nova/virt/disk/mount/api.py:184
2014-05-05 13:52:37.634 DEBUG nova.virt.disk.mount.nbd
[req-3cc7cbae-1ef2-4602-bdc8-82b50f8207c6 admin admin] Release nbd device
/dev/nbd10 unget_dev /opt/stack/nova/nova/virt/disk/mount/nbd.py:128
2014-05-05 13:52:37.636 DEBUG nova.openstack.common.processutils
[req-3cc7cbae-1ef2-4602-bdc8-82b50f8207c6 admin admin] Running cmd
(subprocess): sudo nova-rootwrap /etc/nova/rootwrap.conf qemu-nbd -d
/dev/nbd10 execute
/opt/stack/nova/nova/openstack/common/processutils.py:147
2014-05-05 13:52:37.803 DEBUG nova.virt.disk.vfs.localfs
[req-3cc7cbae-1ef2-4602-bdc8-82b50f8207c6 admin admin] Failed to mount
image Failed to mount filesystem: Unexpected error while running command.
Command: sudo nova-rootwrap /etc/nova/rootwrap.conf mount /dev/nbd10
/tmp/openstack-vfs-localfsCn1KbQ
Exit code: 12
Also the q-gt logs in the previous mail are repeatedly comnig.Is that any
issue?
Please help regarding that.
On Tue, May 6, 2014 at 11:40 AM, Aaron Rosen wrote:
> I don't see any error in the above logs you've pasted. I'd check the
> nova-compute logs as well.
>
> Aaron
>
>
> On Mon, May 5, 2014 at 10:51 PM, sonia verma wrote:
>
>> Hi all
>>
>> I want to boot VM from openstack dashboard onto compute node using
>> devstack.When I'm booting VM from opensatck dashboard onto compute node,the
>> VM status is stuck at 'SPAWNING' and never changes to 'ACTIVE'. I'm also
>> able to get tap interface of the VM onto compute node.I'm getting following
>> error in q-agt service...
>>
>> Stdout:
>> '{"data":[["qvo4b71e52b-d1",["map",[["attached-mac","fa:16:3e:83:6d:7c"],["iface-id","4b71e52b-d14d-48cc-bbce-0eb07719e830"],["iface-status","active"],["vm-uuid","037cbf7a-e3b7-401d-b941-9e0b1c5aaf99",["br-tun",["map",[]]],["br-int",["map",[]]],["qvo2ce34d70-ab",["map",[["attached-mac","fa:16:3e:31:97:c4"],["iface-id","2ce34d70-ab92-456a-aa12-8823df2c007f"],["iface-status","active"],["vm-uuid","370a2bec-7a56-4aa4-87d0-a22470e169fe"],"headings":["name","external_ids"]}\n'
>>
>> Stderr: '' execute /opt/stack/neutron/neutron/agent/linux/utils.py:73
>> 2014-05-05 14:00:50.082 14236 DEBUG neutron.agent.linux.utils [-]
>> Running command: ['sudo', '/usr/local/bin/neutron-rootwrap',
>> '/etc/neutron/rootwrap.conf', 'ovs-vsctl', '--timeout=2', 'list-ports',
>> 'br-int'] create_process /opt/stack/neutron/neutron/agent/linux/utils.py:47
>> 2014-05-05 14:00:50.446 14236 DEBUG neutron.agent.linux.utils [-]
>> Command: ['sudo', '/usr/local/bin/neutron-rootwrap',
>> '/etc/neutron/rootwrap.conf', 'ovs-vsctl', '--timeout=2', 'list-ports',
>> 'br-int']
>> Exit code: 0
>> Stdout: 'qvo2ce34d70-ab\nqvo4b71
>>
>>
>> Please help regarding this.
>>
>> Thanks
>> Sonia
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] q-agt error
Hi all
I want to boot VM from openstack dashboard onto compute node using
devstack.When I'm booting VM from opensatck dashboard onto compute node,the
VM status is stuck at 'SPAWNING' and never changes to 'ACTIVE'. I'm also
able to get tap interface of the VM onto compute node.I'm getting following
error in q-agt service...
Stdout:
'{"data":[["qvo4b71e52b-d1",["map",[["attached-mac","fa:16:3e:83:6d:7c"],["iface-id","4b71e52b-d14d-48cc-bbce-0eb07719e830"],["iface-status","active"],["vm-uuid","037cbf7a-e3b7-401d-b941-9e0b1c5aaf99",["br-tun",["map",[]]],["br-int",["map",[]]],["qvo2ce34d70-ab",["map",[["attached-mac","fa:16:3e:31:97:c4"],["iface-id","2ce34d70-ab92-456a-aa12-8823df2c007f"],["iface-status","active"],["vm-uuid","370a2bec-7a56-4aa4-87d0-a22470e169fe"],"headings":["name","external_ids"]}\n'
Stderr: '' execute /opt/stack/neutron/neutron/agent/linux/utils.py:73
2014-05-05 14:00:50.082 14236 DEBUG neutron.agent.linux.utils [-] Running
command: ['sudo', '/usr/local/bin/neutron-rootwrap',
'/etc/neutron/rootwrap.conf', 'ovs-vsctl', '--timeout=2', 'list-ports',
'br-int'] create_process /opt/stack/neutron/neutron/agent/linux/utils.py:47
2014-05-05 14:00:50.446 14236 DEBUG neutron.agent.linux.utils [-]
Command: ['sudo', '/usr/local/bin/neutron-rootwrap',
'/etc/neutron/rootwrap.conf', 'ovs-vsctl', '--timeout=2', 'list-ports',
'br-int']
Exit code: 0
Stdout: 'qvo2ce34d70-ab\nqvo4b71
Please help regarding this.
Thanks
Sonia
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
