Re: [openstack-dev] [Openstack] Openstack Havana installation using devstack
I'm also facing the same trouble. On Jan 15, 2015 12:05 PM, masoom alam masoom.a...@gmail.com wrote: No I want Havana purposefully. Thanks On Thu, Jan 15, 2015 at 10:45 AM, iKhan ik.ibadk...@gmail.com wrote: Go with stable/icehouse then. On Thu Jan 15 2015 at 11:13:37 AM masoom alam masoom.a...@gmail.com wrote: Hi every one, How can I install Openstack Havana using devstack. The problem is that Havana branch does not exist on Github. git clone https://github.com/openstack-dev/devstack.git -b stable/havana Please guide. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject: unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openst...@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] nova-compute vfsguestfs
Hi Rich I'm trying to run VM from controller node onto compute node and it is stucking at spawning state.I'm able to get the libvirt.xml in /opt/stack/data/nova/instances/729482302900. on the compute node and below is the libvirt.xml file.. domain type=kvm uuid7210aa10-6c98-418a-b97e-94ef2dcbb7f3/uuidHi I'm trying to run VM from controller node onto compute node and it is stucking at spawning state.I'm able to get the libvirt.xml in /opt/stack/data/nova/instances/729482302900. on the compute node and below is the libvirt.xml file.. domain type=kvm uuid7210aa10-6c98-418a-b97e-94ef2dcbb7f3/uuid nameinstance-0003/name memory524288/memory vcpu1/vcpu os type machine=ppce500hvm/type kernel/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/kernel/kernel initrd/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/ramdisk/initrd cmdlineroot=/dev/vda console=tty0 console=ttyS0/cmdline /os features acpi/ apic/ /features clock offset=utc timer name=pit tickpolicy=delay/ timer name=rtc tickpolicy=catchup/ /clock devices disk type=file device=disk driver name=qemu type=qcow2 cache=none/ source file=/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/disk/ target bus=virtio dev=vda/ /disk interface model type=virtio/ source bridge=qbr5d2ebebf-03/ target dev=tap5d2ebebf-03/ filterref filter=nova-instance-instance-0003-fa163ebb2b75/ /interface serial type=file source path=/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/console.log/ /serial serial type=pty/ /devices /domain I'm able to manually run VM through virsh and it is appearing running in virsh list but I'm not able to understand that why it is not able to run automatically from the cloud itself. Below are the steps for running VM manually through virsh.. virsh undefine instance-0003 virsh define libvirt.xml virsh start instance-0003 Please help regarding this. Thanks nameinstance-0003/name memory524288/memory vcpu1/vcpu os type machine=ppce500hvm/type kernel/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/kernel/kernel initrd/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/ramdisk/initrd cmdlineroot=/dev/vda console=tty0 console=ttyS0/cmdline /os features acpi/ apic/ /features clock offset=utc timer name=pit tickpolicy=delay/ timer name=rtc tickpolicy=catchup/ /clock devices disk type=file device=disk driver name=qemu type=qcow2 cache=none/ source file=/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/disk/ target bus=virtio dev=vda/ /disk interface model type=virtio/ source bridge=qbr5d2ebebf-03/ target dev=tap5d2ebebf-03/ filterref filter=nova-instance-instance-0003-fa163ebb2b75/ /interface serial type=file source path=/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/console.log/ /serial serial type=pty/ /devices /domain I'm able to manually run VM through virsh and it is appearing running in virsh list but I'm not able to understand that why it is not able to run automatically from the cloud itself. Below are the steps for running VM manually through virsh.. virsh undefine instance-0003 virsh define libvirt.xml virsh start instance-0003 Please help regarding this. Thanks On Wed, Jun 18, 2014 at 3:55 PM, abhishek jain ashujain9...@gmail.com wrote: Hi RIch Thanks for the reply.The libguestfs is working fine here and there are no issues regarding that on the ubuntu compute node.From the nova-compute logs on the compute node,it appears that the tap interface is not coming up on the compute node. Also in the file driver.py at the path /opt/stack/nova/nova/virt/libvirt in the below section, *uuid = dom.UUIDString()if event == libvirt.VIR_DOMAIN_EVENT_STOPPED:transition = virtevent.EVENT_LIFECYCLE_STOPPED elif event == libvirt.VIR_DOMAIN_EVENT_STARTED:transition = virtevent.EVENT_LIFECYCLE_STARTEDelif event == libvirt.VIR_DOMAIN_EVENT_SUSPENDED:transition = virtevent.EVENT_LIFECYCLE_PAUSED elif event == libvirt.VIR_DOMAIN_EVENT_RESUMED:transition = virtevent.EVENT_LIFECYCLE_RESUMED* the compute node should go in the second part i.e in *libvirt.VIR_DOMAIN_EVENT_STARTED ,which it it missing. * The output of brctl show is follows on the ubuntu compute node-- brctl show bridge namebridge idSTP enabledinterfaces qbr06865952-4f8000.6654b7d239b7noqvb06865952-4f qbr9cbe0875-428000.da3180e79619
[openstack-dev] virsh not running VM autoatically
Hi I'm trying to run VM from controller node onto compute node and it is stucking at spawning state.I'm able to get the libvirt.xml in /opt/stack/data/nova/instances/729482302900. on the compute node and below is the libvirt.xml file.. domain type=kvm uuid7210aa10-6c98-418a-b97e-94ef2dcbb7f3/uuid nameinstance-0003/name memory524288/memory vcpu1/vcpu os type machine=ppce500hvm/type kernel/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/kernel/kernel initrd/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/ramdisk/initrd cmdlineroot=/dev/vda console=tty0 console=ttyS0/cmdline /os features acpi/ apic/ /features clock offset=utc timer name=pit tickpolicy=delay/ timer name=rtc tickpolicy=catchup/ /clock devices disk type=file device=disk driver name=qemu type=qcow2 cache=none/ source file=/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/disk/ target bus=virtio dev=vda/ /disk interface model type=virtio/ source bridge=qbr5d2ebebf-03/ target dev=tap5d2ebebf-03/ filterref filter=nova-instance-instance-0003-fa163ebb2b75/ /interface serial type=file source path=/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/console.log/ /serial serial type=pty/ /devices /domain I'm able to manually run VM through virsh and it is appearing running in virsh list but I'm not able to understand that why it is not able to run automatically from the cloud itself. Below are the steps for running VM manually through virsh.. virsh undefine instance-0003 virsh define libvirt.xml virsh start instance-0003 Please help regarding this. Thanks ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] nova-compute vfsguestfs
Hi RIch Thanks for the reply.The libguestfs is working fine here and there are no issues regarding that on the ubuntu compute node.From the nova-compute logs on the compute node,it appears that the tap interface is not coming up on the compute node. Also in the file driver.py at the path /opt/stack/nova/nova/virt/libvirt in the below section, *uuid = dom.UUIDString()if event == libvirt.VIR_DOMAIN_EVENT_STOPPED:transition = virtevent.EVENT_LIFECYCLE_STOPPEDelif event == libvirt.VIR_DOMAIN_EVENT_STARTED:transition = virtevent.EVENT_LIFECYCLE_STARTEDelif event == libvirt.VIR_DOMAIN_EVENT_SUSPENDED:transition = virtevent.EVENT_LIFECYCLE_PAUSEDelif event == libvirt.VIR_DOMAIN_EVENT_RESUMED:transition = virtevent.EVENT_LIFECYCLE_RESUMED* the compute node should go in the second part i.e in *libvirt.VIR_DOMAIN_EVENT_STARTED ,which it it missing.* The output of brctl show is follows on the ubuntu compute node-- brctl show bridge namebridge idSTP enabledinterfaces qbr06865952-4f8000.6654b7d239b7noqvb06865952-4f qbr9cbe0875-428000.da3180e79619noqvb9cbe0875-42 qbrb61ecf20-cf8000.e24a1b9d71c0noqvbb61ecf20-cf qbrda8485b3-738000.f602a0f09835noqvbda8485b3-73 The main problem is that the tap interface is not able to come up.Below are the nova-compute logs.. ova.virt.libvirt.config [req-6ce8d1f9-5d85-4d4c-a06e-bd8c4d3071ec admin admin] Generated XML domain type=kvm^M uuid3a0e6076-1136-47d2-b883-326d7a87e5d4/uuid^M nameinstance-0009/name^M memory524288/memory^M vcpu1/vcpu^M os^M typehvm/type^M kernel/opt/stack/data/nova/instances/3a0e6076-1136-47d2-b883-326d7a87e5d4/kernel/kernel^M initrd/opt/stack/data/nova/instances/3a0e6076-1136-47d2-b883-326d7a87e5d4/ramdisk/initrd^M cmdlineroot=/dev/vda console=tty0 console=ttyS0/cmdline^M /os^M features^M acpi/^M apic/^M /features^M clock offset=utc^M timer name=pit tickpolicy=delay/^M timer name=rtc tickpolicy=catchup/^M /clock^M devices^M disk type=file device=disk^M driver name=qemu type=qcow2 cache=none/^M source file=/opt/stack/data/nova/instances/3a0e6076-1136-47d2-b883-326d7a87e5d4/disk/^M target bus=virtio dev=vda/^M /disk^M interface type=bridge^M mac address=fa:16:3e:17:c5:cc/^M model type=virtio/^M source bridge=qbrb61ecf20-cf/^M target dev=tapb61ecf20-cf/^M filterref filter=nova-instance-instance-0009-fa163e17c5cc/^M /interface^M serial type=file^M source path=/opt/stack/data/nova/instances/3a0e6076-1136-47d2-b883-326d7a87e5d4/console.log/^M 365,1036% Please help regarding this. Thanks On Tue, Jun 17, 2014 at 8:05 PM, Richard W.M. Jones rjo...@redhat.com wrote: On Fri, Jun 13, 2014 at 03:06:25PM +0530, abhishek jain wrote: Hi Rich Can you help me regarding the possible cause for VM stucking at spawning state on ubuntu powerpc compute node in openstack using devstack. Did you solve this one? It's impossible to debug unless you collect the full debugging information. See also: http://libguestfs.org/guestfs-faq.1.html#how-do-i-debug-when-using-the-api https://bugs.launchpad.net/nova/+bug/1279857 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW ___ 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] no tap interface on compute node
Hi I'm not able to get tap interface up on compute node when I boot VM from controller node onto compute node. Please help regarding this. Thanks Abhishek Jain ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] no tap interface on compute node
Hi I posted it on ask.openstack.org but I got no response. On Mon, Jun 16, 2014 at 6:41 PM, Kashyap Chamarthy kcham...@redhat.com wrote: On Mon, Jun 16, 2014 at 11:31:50AM +0530, abhishek jain wrote: Hi I'm not able to get tap interface up on compute node when I boot VM from controller node onto compute node. Please help regarding this. For such usage questions, please post (with more verbose details including Neutron investigation) them on ask.openstack.org. That said, I use these scripts to debug Neutron: https://raw.github.com/larsks/neutron-diag/ Neutron requires systematic debugging as there are plenty of network devices involved. -- /kashyap ___ 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 stucking at spawning
Hi I have installed openstack using devstack.I'm able to boot VM from openstack cloud on the controller node.When I'm trying to boot VM on the compute node,it is stucking at spawning state.The logs of the nova-compute on the controller node is almost the same as that of of the nova-compute on the compute node except one difference i.e the ', '/usr/bin/tee: /sys/class/net/tapd836ffc38-f2/brport/hairpin_mode: No such file or directory\n') 2014-06-13 09:45:17.314 DEBUG nova.virt.libvirt.driver [req-5abd5544-03a6-4046-99 267-65912a4ce477 admin admin] [instance: 46c68bd3-455b-4997-a9a0-8bd04de3da51] II nstance is running spawn /opt/stack/nova/nova/virt/libvirt/driver.py:2092^M It is not able to get any tap directry in /sys/class/net path. Please help regarding this . Thanks Abhishek Jain ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] nova-compute vfsguestfs
Hi Rich Can you help me regarding the possible cause for VM stucking at spawning state on ubuntu powerpc compute node in openstack using devstack. Thanks On Tue, Jun 10, 2014 at 10:29 PM, abhishek jain ashujain9...@gmail.com wrote: Hi Rich I'm able to solve the problem regarding PAPR in libguestfs on my powerpc ubuntu.By default the libguestfs was configuring pseries machine and afterwards I changed it to my original machine i.e ppce500 .The changes are performed in ./src/guestfs-internal.h file. However still my VM is stucking in spawning state.The compute node is not able generate the xml file required for running the instances which I have checked by comparing the nova-compute logs of controller node aw well as compute node since I'm able to run VM on controller node. Thanks for the help,I'll let you know if any further issues. On Sat, Jun 7, 2014 at 5:06 PM, Richard W.M. Jones rjo...@redhat.com wrote: On Tue, May 27, 2014 at 03:25:10PM +0530, abhishek jain wrote: Hi Daniel Thanks for the help. The end result of my setup is that the VM is stucking at Spawning state on my compute node whereas it is working fine on the controller node. Therefore I'm comparing nova-compute logs of both compute node as well as controller node and trying to proceed step by step. I'm having all the above packages enabled Do you have any idea regarding reason for VM stucking at spawning state. The most common reason is that nested virt is broken. libguestfs is the canary in the mine here, not the cause of the problem. Rich. On Tue, May 27, 2014 at 2:38 PM, Daniel P. Berrange berra...@redhat.comwrote: On Tue, May 27, 2014 at 12:04:23PM +0530, abhishek jain wrote: Hi Below is the code to which I'm going to reffer to.. vim /opt/stack/nova/nova/virt/disk/vfs/api.py # try: LOG.debug(_(Trying to import guestfs)) importutils.import_module(guestfs) hasGuestfs = True except Exception: pass if hasGuestfs: LOG.debug(_(Using primary VFSGuestFS)) return importutils.import_object( nova.virt.disk.vfs.guestfs.VFSGuestFS, imgfile, imgfmt, partition) else: LOG.debug(_(Falling back to VFSLocalFS)) return importutils.import_object( nova.virt.disk.vfs.localfs.VFSLocalFS, imgfile, imgfmt, partition) ### When I'm launching VM from the controller node onto compute node,the nova compute logs on the compute node displays...Falling back to VFSLocalFS and the result is that the VM is stuck in spawning state. However When I'm trying to launch a VM onto controller node form the controller node itself,the nova compute logs on the controller node dislpays ...Using primary VFSGuestFS and I'm able to launch VM on controller node. Is there any module in the kernel or any package that i need to enable.Please help regarding this. VFSGuestFS requires the libguestfs python module corresponding native package to be present, and only works with KVM/QEMU enabled hosts. VFSLocalFS requires loopback module, nbd module, qemu-nbd, kpartx and a few other misc host tools Neither of these should cause a VM getting stuck in the spawning state, even if stuff they need is missing. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/:| |: http://libvirt.org -o- http://virt-manager.org:| |: http://autobuild.org -o- http://search.cpan.org/~danberr/:| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc:| ___ 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 -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html ___ 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
Re: [openstack-dev] nova-compute vfsguestfs
Hi Rich I'm able to solve the problem regarding PAPR in libguestfs on my powerpc ubuntu.By default the libguestfs was configuring pseries machine and afterwards I changed it to my original machine i.e ppce500 .The changes are performed in ./src/guestfs-internal.h file. However still my VM is stucking in spawning state.The compute node is not able generate the xml file required for running the instances which I have checked by comparing the nova-compute logs of controller node aw well as compute node since I'm able to run VM on controller node. Thanks for the help,I'll let you know if any further issues. On Sat, Jun 7, 2014 at 5:06 PM, Richard W.M. Jones rjo...@redhat.com wrote: On Tue, May 27, 2014 at 03:25:10PM +0530, abhishek jain wrote: Hi Daniel Thanks for the help. The end result of my setup is that the VM is stucking at Spawning state on my compute node whereas it is working fine on the controller node. Therefore I'm comparing nova-compute logs of both compute node as well as controller node and trying to proceed step by step. I'm having all the above packages enabled Do you have any idea regarding reason for VM stucking at spawning state. The most common reason is that nested virt is broken. libguestfs is the canary in the mine here, not the cause of the problem. Rich. On Tue, May 27, 2014 at 2:38 PM, Daniel P. Berrange berra...@redhat.com wrote: On Tue, May 27, 2014 at 12:04:23PM +0530, abhishek jain wrote: Hi Below is the code to which I'm going to reffer to.. vim /opt/stack/nova/nova/virt/disk/vfs/api.py # try: LOG.debug(_(Trying to import guestfs)) importutils.import_module(guestfs) hasGuestfs = True except Exception: pass if hasGuestfs: LOG.debug(_(Using primary VFSGuestFS)) return importutils.import_object( nova.virt.disk.vfs.guestfs.VFSGuestFS, imgfile, imgfmt, partition) else: LOG.debug(_(Falling back to VFSLocalFS)) return importutils.import_object( nova.virt.disk.vfs.localfs.VFSLocalFS, imgfile, imgfmt, partition) ### When I'm launching VM from the controller node onto compute node,the nova compute logs on the compute node displays...Falling back to VFSLocalFS and the result is that the VM is stuck in spawning state. However When I'm trying to launch a VM onto controller node form the controller node itself,the nova compute logs on the controller node dislpays ...Using primary VFSGuestFS and I'm able to launch VM on controller node. Is there any module in the kernel or any package that i need to enable.Please help regarding this. VFSGuestFS requires the libguestfs python module corresponding native package to be present, and only works with KVM/QEMU enabled hosts. VFSLocalFS requires loopback module, nbd module, qemu-nbd, kpartx and a few other misc host tools Neither of these should cause a VM getting stuck in the spawning state, even if stuff they need is missing. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/:| |: http://libvirt.org -o- http://virt-manager.org:| |: http://autobuild.org -o- http://search.cpan.org/~danberr/:| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc:| ___ 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 -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html ___ 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
Re: [openstack-dev] nova-compute rpc version
Hi Russell Thanks I'm able to solve it now by switching onto havana release on both the controller node and compute node. On Tue, Jun 3, 2014 at 10:56 AM, abhishek jain ashujain9...@gmail.com wrote: Hi Russell Below are the details... controller node... nova --version 2.17.0.122 nova-compute --version 2014.2 compute node. nova --version 2.17.0.122 nova-compute --version 2013.2.4 Can you help me what i need to change in order to achieve the desired functioonality. Thaks On Tue, Jun 3, 2014 at 2:16 AM, Russell Bryant rbry...@redhat.com wrote: On 06/02/2014 08:20 AM, abhishek jain wrote: |Hi | | I'm getting following error in nova-compute logs when trying to boot VM from controller node onto compute node ... Specified RPC version, 3.23, not supported Please help regarding this. It sounds like you're using an older nova-compute with newer controller services (without the configuration to allow a live ugprade). Check the versions of Nova services you have running. -- Russell Bryant ___ 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 rpc version
Hi I'm getting following error in nova-compute logs when trying to boot VM from controller node onto compute node ... Specified RPC version, 3.23, not supported Please help regarding this. Thanks Abhishek Jain ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] nova-compute rpc version
Hi Russell Below are the details... controller node... nova --version 2.17.0.122 nova-compute --version 2014.2 compute node. nova --version 2.17.0.122 nova-compute --version 2013.2.4 Can you help me what i need to change in order to achieve the desired functioonality. Thaks On Tue, Jun 3, 2014 at 2:16 AM, Russell Bryant rbry...@redhat.com wrote: On 06/02/2014 08:20 AM, abhishek jain wrote: |Hi | | I'm getting following error in nova-compute logs when trying to boot VM from controller node onto compute node ... Specified RPC version, 3.23, not supported Please help regarding this. It sounds like you're using an older nova-compute with newer controller services (without the configuration to allow a live ugprade). Check the versions of Nova services you have running. -- Russell Bryant ___ 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 I'm trying to run my q-agt service and getting following error ... -05-28 02:00:51.205 15377 DEBUG neutron.agent.linux.utils [-] Command: ['ip', '-o', 'link', 'show', 'br-int'] Exit code: 0 Stdout: '28: br-int: BROADCAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT \\link/ether 3a:ed:a9:bd:14:19 brd ff:ff:ff:ff:ff:ff\n' Stderr: '' execute /opt/stack/neutron/neutron/agent/linux/utils.py:74 2014-05-28 02:00:51.209 15377 CRITICAL neutron [-] Policy configuration policy.json could not be found 2014-05-28 02:00:51.209 15377 TRACE neutron Traceback (most recent call last): 2014-05-28 02:00:51.209 15377 TRACE neutron File /usr/local/bin/neutron-openvswitch-agent, line 10, in module 2014-05-28 02:00:51.209 15377 TRACE neutron sys.exit(main()) 2014-05-28 02:00:51.209 15377 TRACE neutron File /opt/stack/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 1485, in main 2014-05-28 02:00:51.209 15377 TRACE neutron agent = OVSNeutronAgent(**agent_config) 2014-05-28 02:00:51.209 15377 TRACE neutron File /opt/stack/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 207, in __init__ Please help regarding this. Thanks Abhishek Jain ___ 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 Asaf Thanks I'm able to solve the above error but I'm stuck in the another one. Below is the code which I'm going to reffer to.. vim /opt/stack/nova/nova/virt/disk/vfs/api.py # try: LOG.debug(_(Trying to import guestfs)) importutils.import_module(guestfs) hasGuestfs = True except Exception: pass if hasGuestfs: LOG.debug(_(Using primary VFSGuestFS)) return importutils.import_object( nova.virt.disk.vfs.guestfs.VFSGuestFS, imgfile, imgfmt, partition) else: LOG.debug(_(Falling back to VFSLocalFS)) return importutils.import_object( nova.virt.disk.vfs.localfs.VFSLocalFS, imgfile, imgfmt, partition) ### When I'm launching VM from the controller node onto compute node,the nova compute logs on the compute node displays...Falling back to VFSLocalFS and the result is that the VM is stuck in spawning state. However When I'm trying to launch a VM onto controller node form the controller node itself,the nova compute logs on the controller node dislpays ...Using primary VFSGuestFS and I'm able to launch VM on controller node. Is there any module in the kernel or any package that i need to enable.Please help. On Wed, May 28, 2014 at 3:00 PM, Assaf Muller amul...@redhat.com wrote: - Original Message - Hi I'm trying to run my q-agt service and getting following error ... You've stumbled on the development mailing list. You will have better luck with ask.openstack.org or the users mailing list. Good luck! -05-28 02:00:51.205 15377 DEBUG neutron.agent.linux.utils [-] Command: ['ip', '-o', 'link', 'show', 'br-int'] Exit code: 0 Stdout: '28: br-int: BROADCAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT \\ link/ether 3a:ed:a9:bd:14:19 brd ff:ff:ff:ff:ff:ff\n' Stderr: '' execute /opt/stack/neutron/neutron/agent/linux/utils.py:74 2014-05-28 02:00:51.209 15377 CRITICAL neutron [-] Policy configuration policy.json could not be found 2014-05-28 02:00:51.209 15377 TRACE neutron Traceback (most recent call last): 2014-05-28 02:00:51.209 15377 TRACE neutron File /usr/local/bin/neutron-openvswitch-agent, line 10, in module 2014-05-28 02:00:51.209 15377 TRACE neutron sys.exit(main()) 2014-05-28 02:00:51.209 15377 TRACE neutron File /opt/stack/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 1485, in main 2014-05-28 02:00:51.209 15377 TRACE neutron agent = OVSNeutronAgent(**agent_config) 2014-05-28 02:00:51.209 15377 TRACE neutron File /opt/stack/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 207, in __init__ Please help regarding this. Thanks Abhishek Jain ___ 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] nova-compute vfsguestfs
Hi Below is the code to which I'm going to reffer to.. vim /opt/stack/nova/nova/virt/disk/vfs/api.py # try: LOG.debug(_(Trying to import guestfs)) importutils.import_module(guestfs) hasGuestfs = True except Exception: pass if hasGuestfs: LOG.debug(_(Using primary VFSGuestFS)) return importutils.import_object( nova.virt.disk.vfs.guestfs.VFSGuestFS, imgfile, imgfmt, partition) else: LOG.debug(_(Falling back to VFSLocalFS)) return importutils.import_object( nova.virt.disk.vfs.localfs.VFSLocalFS, imgfile, imgfmt, partition) ### When I'm launching VM from the controller node onto compute node,the nova compute logs on the compute node displays...Falling back to VFSLocalFS and the result is that the VM is stuck in spawning state. However When I'm trying to launch a VM onto controller node form the controller node itself,the nova compute logs on the controller node dislpays ...Using primary VFSGuestFS and I'm able to launch VM on controller node. Is there any module in the kernel or any package that i need to enable.Please help regarding this. Thanks Abhishek Jain ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] nova-compute vfsguestfs
Hi Daniel Thanks for the help. The end result of my setup is that the VM is stucking at Spawning state on my compute node whereas it is working fine on the controller node. Therefore I'm comparing nova-compute logs of both compute node as well as controller node and trying to proceed step by step. I'm having all the above packages enabled Do you have any idea regarding reason for VM stucking at spawning state. On Tue, May 27, 2014 at 2:38 PM, Daniel P. Berrange berra...@redhat.comwrote: On Tue, May 27, 2014 at 12:04:23PM +0530, abhishek jain wrote: Hi Below is the code to which I'm going to reffer to.. vim /opt/stack/nova/nova/virt/disk/vfs/api.py # try: LOG.debug(_(Trying to import guestfs)) importutils.import_module(guestfs) hasGuestfs = True except Exception: pass if hasGuestfs: LOG.debug(_(Using primary VFSGuestFS)) return importutils.import_object( nova.virt.disk.vfs.guestfs.VFSGuestFS, imgfile, imgfmt, partition) else: LOG.debug(_(Falling back to VFSLocalFS)) return importutils.import_object( nova.virt.disk.vfs.localfs.VFSLocalFS, imgfile, imgfmt, partition) ### When I'm launching VM from the controller node onto compute node,the nova compute logs on the compute node displays...Falling back to VFSLocalFS and the result is that the VM is stuck in spawning state. However When I'm trying to launch a VM onto controller node form the controller node itself,the nova compute logs on the controller node dislpays ...Using primary VFSGuestFS and I'm able to launch VM on controller node. Is there any module in the kernel or any package that i need to enable.Please help regarding this. VFSGuestFS requires the libguestfs python module corresponding native package to be present, and only works with KVM/QEMU enabled hosts. VFSLocalFS requires loopback module, nbd module, qemu-nbd, kpartx and a few other misc host tools Neither of these should cause a VM getting stuck in the spawning state, even if stuff they need is missing. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/:| |: http://libvirt.org -o- http://virt-manager.org:| |: http://autobuild.org -o- http://search.cpan.org/~danberr/:| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc:| ___ 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
Hi all
I'm trying to run VM on a compute node having ubuntu 13.10 with powerpc
arch.When I launch a VM from the controller node,it is stucking at
spawning state and below are the logs of nova-compute ...
/common/processutils.py:147^M
#Result is passed#^M
2014-05-17 04:54:26.662 DEBUG nova.openstack.common.processutils
[req-8d485ab7-4879-42fe-9c6b-d6ffb8dde644 None None] Result was 0 execute
/opt/stack/nova/nova/openstack/common/processutils.py:174^M
result is :('image:
/opt/stack/data/nova/instances/f7d43412-3c5f-46cf-978b-670a29506d89/disk\nfile
format: qcow2\nvirtual size: 1.0G (1073741824 bytes)\ndisk size:
204K\ncluster_size: 65536\nbacking file:
/opt/stack/data/nova/instances/_base/b54371f89f94085a638ff098ed31e0027555eedc\n',
'')^M
#finally condition met^M
2014-05-17 04:54:26.705 DEBUG nova.compute.resource_tracker
[req-8d485ab7-4879-42fe-9c6b-d6ffb8dde644 None None] Hypervisor: free ram
(MB): 5449 _report_hypervisor_resource_view
/opt/stack/nova/nova/compute/resource_tracker.py:388^M
2014-05-17 04:54:26.706 DEBUG nova.compute.resource_tracker
[req-8d485ab7-4879-42fe-9c6b-d6ffb8dde644 None None] Hypervisor: free disk
(GB): 95 _report_hypervisor_resource_view
/opt/stack/nova/nova/compute/resource_tracker.py:389^M
2014-05-17 04:54:26.706 DEBUG nova.compute.resource_tracker
[req-8d485ab7-4879-42fe-9c6b-d6ffb8dde644 None None] Hypervisor: free
VCPUs: 24 _report_hypervisor_resource_view
/opt/stack/nova/nova/compute/resource_tracker.py:394^M
2014-05-17 04:54:26.707 DEBUG nova.compute.resource_tracker
[req-8d485ab7-4879-42fe-9c6b-d6ffb8dde644 None None] Hypervisor: assignable
PCI devices: [] _report_hypervisor_resource_view
/opt/stack/nova/nova/compute/resource_tracker.py:401^M
2014-05-17 04:54:26.708 DEBUG nova.openstack.common.rpc.amqp
[req-8d485ab7-4879-42fe-9c6b-d6ffb8dde644 None None] Making synchronous
call on conductor ... multicall
/opt/stack/nova/nova/openstack/common/rpc/amqp.py:553^M
I'm using mini.iso for ppc64 as a VM for booting onto the compute node from
the below link...
https://help.ubuntu.com/community/Installation/MinimalCD
However when I'm trying to launch a VM onto x86 compute node with mini.iso
as VM from the above link for x86 machine,the status of VM is ACTIVE and
below are the nova-compute logs..
t/stack/nova/nova/openstack/common/processutils.py:188^M
#Result is passed#^M
result is :('', '')^M
#finally condition met^M
2014-05-17 14:07:13.701 DEBUG nova.network.linux_net
[req-d0effb91-f036-45d5-b212-18dea1bd1e19 admin admin] Net device removed:
'qvod42ac663-a4' delete_net_dev
/opt/stack/nova/nova/network/linux_net.py:1358^M
2014-05-17 14:07:13.744 DEBUG nova.objects.instance
[req-d0effb91-f036-45d5-b212-18dea1bd1e19 admin admin] Lazy-loading
`system_metadata' on Instance uuid b2257f51-56c1-4464-ba1e-b24e44cbaba9
obj_load_attr /opt/stack/nova/nova/objects/instance.py:519^M
2014-05-17 14:07:13.801 INFO nova.virt.libvirt.driver
[req-d0effb91-f036-45d5-b212-18dea1bd1e19 admin admin] [instance:
b2257f51-56c1-4464-ba1e-b24e44cbaba9] Deleting instance files
/opt/stack/data/nova/instances/b2257f51-56c1-4464-ba1e-b24e44cbaba9^M
2014-05-17 14:07:13.805 INFO nova.virt.libvirt.driver
[req-d0effb91-f036-45d5-b212-18dea1bd1e19 admin admin] [instance:
b2257f51-56c1-4464-ba1e-b24e44cbaba9] Deletion of
/opt/stack/data/nova/instances/b2257f51-56c1-4464-ba1e-b24e44cbaba9
complete^M
2014-05-17 14:07:13.937 DEBUG nova.compute.manager
[req-d0effb91-f036-45d5-b212-18dea1bd1e19 admin admin] [instance:
b2257f51-56c1-4464-ba1e-b24e44cbaba9] Deallocating network for instance
_deallocate_network /
While comparing the logs from the two different compute logs,the value of
result comes out as the only difference.
I'm also attaching the file from where the above logs are coming i.e
/opt/stack/nova/nova/openstack/common/processutils.py.
Please help regarding this.
Thanks
Abhishek Jain
# vim: tabstop=4 shiftwidth=4 softtabstop=4
# Copyright 2011 OpenStack Foundation.
# All Rights Reserved.
#
#Licensed under the Apache License, Version 2.0 (the License); you may
#not use this file except in compliance with the License. You may obtain
#a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
#Unless required by applicable law or agreed to in writing, software
#distributed under the License is distributed on an AS IS BASIS, WITHOUT
#WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
#License for the specific language governing permissions and limitations
#under the License.
System-level utilities and helper functions.
import logging as stdlib_logging
import os
import random
import shlex
import signal
from eventlet.green import subprocess
from eventlet import greenthread
from nova.openstack.common.gettextutils import _ # noqa
from
[openstack-dev] Vm stucking at spawning state
/filter_scheduler.py:82 2014-05-11 18:48:51.375 AUDIT nova.scheduler.host_manager [req-e36b289c-510c-4f47-9500-73f9a91c5f0e admin admin] Host filter forcing available hosts to t4240-ubuntu1310 2014-05-11 18:48:51.375 DEBUG nova.scheduler.filter_scheduler [req-e36b289c-510c-4f47-9500-73f9a91c5f0e admin admin] Filtered [(t4240-ubuntu1310, t4240-ubuntu1310) ram:4352 disk:97280 io_ops:2 instances:2] _schedule /opt/stack/nova/nova/scheduler/filter_scheduler.py:331 2014-05-11 18:48:51.376 DEBUG nova.scheduler.filter_scheduler [req-e36b289c-510c-4f47-9500-73f9a91c5f0e admin admin] Weighed [WeighedHost [host: t4240-ubuntu1310, weight: 1.0]] _schedule /opt/stack/nova/nova/scheduler/filter_scheduler.py:336 2014-05-11 18:48:51.376 INFO nova.scheduler.filter_scheduler [req-e36b289c-510c-4f47-9500-73f9a91c5f0e admin admin] Choosing host WeighedHost [host: t4240-ubuntu1310, weight: 1.0] for instance 3946ee7f-d4a0-4c75-8ecc-0c32ec739c14 2014-05-11 18:49:22.558 20123 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 2014-05-11 18:49:22.565 20123 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 2014-05-11 18:49:22.565 20123 DEBUG nova.openstack.common.loopingcall [-] Dynamic looping call sleeping for 60.00 seconds _inner /opt/stack/nova/nova/openstack/common/loopingcall.py:130 2014-05-11 18:50:22.567 20123 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 2014-05-11 18:50:22.574 20123 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 2014-05-11 18:50:22.574 20123 DEBUG nova.openstack.common.loopingcall [-] Dynamic looping call sleeping for 60.00 seconds _inner /opt/stack/nova/nova/openstack/common/loopingcall.py:130 2014-05-11 18:51:22.577 20123 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 2014-05-11 18:51:22.584 20123 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 2014-05-11 18:51:22.585 20123 DEBUG nova.openstack.common.loopingcall [-] Dynamic looping call sleeping for 60.00 seconds _inner /opt/stack/nova/nova/openstack/common/loopingcall.py:130 2014-05-11 18:52:22.588 20123 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 2014-05-11 18:52:22.595 20123 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 2014-05-11 18:52:22.595 20123 DEBUG nova.openstack.common.loopingcall [-] Dynamic looping call sleeping for 60.00 seconds _inner /opt/stack/nova/nova/openstack/common/loopingcall.py:130 2014-05-11 18:53:22.597 20123 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 2014-05-11 18:53:22.604 20123 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 2014-05-11 18:53:22.605 20123 DEBUG nova.openstack.common.loopingcall [-] Dynamic looping call sleeping for 60.00 seconds _inner /opt/stack/nova/nova/openstack/common/loopingcall.py:130 Please help regarding this. Thanks Abhishek Jain ___ 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
Thanks Thierry for the help On Wed, May 7, 2014 at 1:31 PM, Thierry Carrez thie...@openstack.orgwrote: 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] q-agt error
Hi all I'm getting following error in q-agt service of compute node while booting VM from controller node onto it.. 14-05-04 08:56:53.508 13530 DEBUG neutron.agent.linux.utils [-] Command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip6tables-restore', '-c'] Exit code: 2 Stdout: '' Stderr: libkmod: ERROR ../libkmod/libkmod.c:554 kmod_search_moddep: could not open moddep file '/lib/modules/3.8.13-rt9-QorIQ-SDK-V1.4/modules.dep.bin'\nip6tables-restore v1.4.18: ip6tables-restore: unable to initialize table 'filter'\n\nError occurred at line: 2\nTry `ip6tables-restore -h' or 'ip6tables-restore --help' for more information.\n execute /opt/stack/neutron/neutron/agent/linux/utils.py:73 2014-05-04 08:56:53.510 13530 DEBUG neutron.openstack.common.lockutils [-] Released file lock iptables at /opt/stack/data/neutron/lock/neutron-iptables for method _apply... inner /opt/stack/neutron/neutron/openstack/common/lockutils.py:239 2014-05-04 08:56:53.512 13530 ERROR neutron.plugins.openvswitch.agent.ovs_neutron_agent [-] Error in agent event loop 2014-05-04 08:56:53.512 13530 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent Traceback (most recent call last): 2014-05-04 08:56:53.512 13530 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 1082, in rpc_loop Please help me regarding this. Thanks Abhishek Jain ___ 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
I changed the ebtables version i.e ebtables_2.0.9.2-2ubuntu3_powerpc.deb
from version 2.0.10-4 and the error just reduced to one as below...
2014-05-03 11:26:42.052 12065 TRACE nova.openstack.common.rpc.amqp if
ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed',
dom=self)
2014-05-03 11:26:42.052 12065 TRACE nova.openstack.common.rpc.amqp
libvirtError: Error while building firewall: Some rules could not be
created for interface tap9dafa3dd-7a: Failure to execute command '$EBT -t
nat -A libvirt-J-tap9dafa3dd-7a -j J-tap9dafa3dd-7a-mac' : 'The kernel
doesn't support a certain ebtables extension, consider recompiling your
kernel or insmod the extension.'.
2014-05-03 11:26:42.052 12065 TRACE nova.openstack.common.rpc.amqp
2014-05-03 11:26:42.052 12065 TRACE nova.openstack.common.rpc.amqp
2014-05-03 11:26:45.374 12065 DEBUG nova.openstack.common.rpc.amqp [-]
Making synchronous call on conductor ... multicall /opt/stack/nova/nova/o
I'm using ubuntu 13.10 with powerpc architeture.
Is there any other way of booting VM without the dependency of
ebtables.PLease let me know.
Thanks
On Sat, May 3, 2014 at 12:55 PM, abhishek jain ashujain9...@gmail.comwrote:
Hi all
I want to boot VM from controller node onto the compute node using
devstack.All my services such as nova,q-agt,nova-compute,neutron,etc are
running properly both on compute node as well on the controller node.I'm
also able to boot VMs on controller node from the openstack dashvoard
.However issue is coming when I'm booting VM from controller node onto
compute node.
Following is the error in the nova-compute logs when I'm trying to boot VM
on compute node from controller node
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp if
ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed',
dom=self)
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
libvirtError: Error while building firewall: Some rules could not be
created for interface tap74d2ff08-7f: Failure to execute command '$EBT -t
nat -A libvirt-J-tap74d2ff08-7f -j J-tap74d2ff08-7f-mac' : 'Unable to
update the kernel. Two possible causes:
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp 1.
Multiple ebtables programs were executing simultaneously. The ebtables
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
userspace tool doesn't by default support multiple ebtables programs
running
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
concurrently. The ebtables option --concurrent or a tool like flock can be
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqpused
to support concurrent scripts that update the ebtables kernel tables.
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp 2. The
kernel doesn't support a certain ebtables extension, consider
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
recompiling your kernel or insmod the extension.
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp .'.
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
2014-04-30 05:10:29.066 17049 DEBUG nova.openstack.common.rpc.amqp [-]
Making synchronous call on conductor ... multicall /opt/stack/nova/nova/o
From the logs it appears that the command $EBT -t nat -A
libvirt-J-tap74d2ff08-7f -j J-tap74d2ff08-7f-mac is not able to update the
kernel with the ebtables rules.I have also enabled the ebtables modules(*)
in my kernel.
Please help me regarding this.
Also is there any other way of booting the VM without updating the rules
in kernel .
Thanks
Abhisehk Jain
___
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 want to boot VM from controller node onto the compute node using
devstack.All my services such as nova,q-agt,nova-compute,neutron,etc are
running properly both on compute node as well on the controller node.I'm
also able to boot VMs on controller node from the openstack dashvoard
.However issue is coming when I'm booting VM from controller node onto
compute node.
Following is the error in the nova-compute logs when I'm trying to boot VM
on compute node from controller node
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp if
ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed',
dom=self)
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
libvirtError: Error while building firewall: Some rules could not be
created for interface tap74d2ff08-7f: Failure to execute command '$EBT -t
nat -A libvirt-J-tap74d2ff08-7f -j J-tap74d2ff08-7f-mac' : 'Unable to
update the kernel. Two possible causes:
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp 1.
Multiple ebtables programs were executing simultaneously. The ebtables
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
userspace tool doesn't by default support multiple ebtables programs
running
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
concurrently. The ebtables option --concurrent or a tool like flock can be
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqpused
to support concurrent scripts that update the ebtables kernel tables.
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp 2. The
kernel doesn't support a certain ebtables extension, consider
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
recompiling your kernel or insmod the extension.
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp .'.
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
2014-04-30 05:10:29.066 17049 DEBUG nova.openstack.common.rpc.amqp [-]
Making synchronous call on conductor ... multicall /opt/stack/nova/nova/o
From the logs it appears that the command $EBT -t nat -A
libvirt-J-tap74d2ff08-7f -j J-tap74d2ff08-7f-mac is not able to update the
kernel with the ebtables rules.I have also enabled the ebtables modules(*)
in my kernel.
Please help me regarding this.
Also is there any other way of booting the VM without updating the rules in
kernel .
Thanks
Abhisehk Jain
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] nova compute libvirtd error
Hi all
I'm trying too boot Vm from my controller node onto compute node and
getting following error in nova-compute service ...
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp if
ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed',
dom=self)
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
libvirtError: Error while building firewall: Some rules could not be
created for interface tap74d2ff08-7f: Failure to execute command '$EBT -t
nat -A libvirt-J-tap74d2ff08-7f -j J-tap74d2ff08-7f-mac' : 'Unable to
update the kernel. Two possible causes:
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp 1.
Multiple ebtables programs were executing simultaneously. The ebtables
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
userspace tool doesn't by default support multiple ebtables programs
running
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
concurrently. The ebtables option --concurrent or a tool like flock can be
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqpused
to support concurrent scripts that update the ebtables kernel tables.
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp 2. The
kernel doesn't support a certain ebtables extension, consider
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
recompiling your kernel or insmod the extension.
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp .'.
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp
2014-04-30 05:10:29.066 17049 DEBUG nova.openstack.common.rpc.amqp [-]
Making synchronous call on conductor ... multicall /opt/stack/nova/nova/o
However I'm able to boot the VM on controller node i.e the nova-compute on
cotroller node is no issue.
Following is the output of the commands related to ebtables on comppute
node..
lsmod
Module Size Used by
ebtable_filter 3194 0
ebtable_nat 3173 0
ebtables 32629 2 ebtable_nat,ebtable_filter
openvswitch62005 0
sudo service ebtables status
* Ebtables support available, number of installed
rules
[ OK ]
sudo ebtables -L
Bridge table: filter
Bridge chain: INPUT, entries: 0, policy: ACCEPT
Bridge chain: FORWARD, entries: 0, policy: ACCEPT
Bridge chain: OUTPUT, entries: 0, policy: ACCEPT
Please help regarding this.
Thanks..
Abhishek Jain
___
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 follwoing error when trying to run nova-compute service..
if ret is None: raise libvirtError ('virNodeListDevices() failed',
conn=self)
2014-04-29 00:51:47.153 28127 TRACE nova.openstack.common.threadgroup
libvirtError: this function is not supported by the connection driver:
virNodeNumOfDevices
2014-04-29 00:51:47.153 28127 TRACE nova.openstack.common.threadgroup
Please help regarding this.
Thanks
Abhishek Jain
___
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 Ricky Thanks.You are right. I'm getting following error after running the command ... sudo ip link add qvbb2fc7c52-ae type veth peer name qvob2fc7c52-ae RTNETLINK answers: Operation not supported Below is the description of my system.. uname -a Linux t4240-ubuntu1310 3.8.13-rt9-QorIQ-SDK-V1.4 #3 SMP Wed Apr 23 12:11:58 CDT 2014 ppc64 ppc64 ppc64 GNU/Linux Plaese help regarding this. On Sat, Apr 26, 2014 at 2:13 PM, Bohai (ricky) bo...@huawei.com wrote: It seems that the command “ip link add qvbb2fc7c52-ae type veth peer name qvob2fc7c52-ae” failed. Maybe you can try it manually and confirm whether it’s the reason. Best regards to you. Ricky *From:* abhishek jain [mailto:ashujain9...@gmail.com] *Sent:* Saturday, April 26, 2014 3:25 PM *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* [openstack-dev] nova compute error Hi all.. I'm getting following nova-compute error and thus not able to boot the VMs on my compute node... nova-ompute service stopped and started giving following error... [02:06:44] Abhishek Jain: 2014-04-25 15:32:00.112 6501 TRACE nova.openstack.common.threadgroup cmd=' '.join(cmd)) 2014-04-25 15:32:00.112 6501 TRACE nova.openstack.common.threadgroup ProcessExecutionError: Unexpected error while running command. 2014-04-25 15:32:00.112 6501 TRACE nova.openstack.common.threadgroup Command: ip link add qvbb2fc7c52-ae type veth peer name qvob2fc7c52-ae 2014-04-25 15:32:00.112 6501 TRACE nova.openstack.common.threadgroup Exit code: 2 2014-04-25 15:32:00.112 6501 TRACE nova.openstack.common.threadgroup Stdout: '' 2014-04-25 15:32:00.112 6501 TRACE nova.openstack.common.threadgroup Stderr: 'RTNETLINK answers: Operation not supported\n' 2014-04-25 15:32:00.112 6501 TRACE nova.openstack.common.threadgroup I'm able to run other services such as nova and q-agt on compute node and also the compute node is reflected on the controller node and vice versa. Please help me regarding this . Thanks Abhishek Jain ___ 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
Re: [openstack-dev] How to re-compile Devstack Code
Hi shiva You can reload the openstack services by following the below steps after making the desired changes.. i) Enter into the devstack directry i.e cd devstack ii) Execute rejoin-stackh.sh i.e ./rejoin-stack.sh iii) Press ctrl+a+shift+ iv) Select the appropriate service to restart Please let me know if further issues. Thanks On Thu, Apr 24, 2014 at 11:12 AM, shiva m anjane...@gmail.com wrote: Hi, I have Devstack havana setup on Ubuntu 13.10. I am trying to modify some files in /opt/stack/* folder. How do I re-compile the Devstack to make my changes get effect. Does unstacking and stacking works?. I see unstacking and stacking installs everything fresh. Correct me if wrong. Thanks, Shiva ___ 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] Fwd: Openstack Vms not able to abtain IP address from DHCP
Hi I'm following link for opendaylight openstack integration.. http://networkstatic.net/opendaylight-openstack-integration-devstack-fedora-20/ I'm able to interact opendaylight controller with the stack using ml2 plugin and boot the VMs at the controller node and at compute node. The problem which I'm facing now is that I'm not able to obtain IP address on the VM at compute node from the DHCP. However I'm able to abtain the IP address on the VM at controller node from DHCP I'm attaching my local.conf at the compute node as well as at the controller node Please help regarding this. Thanks Abhishek Jain local.conf_compute_node Description: Binary data local.conf_controller Description: Binary data ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Nova Live Migration issue
Hi all I'm following the below link for VM migration from one compute node to the another from the controller node using devstack .. http://www.mirantis.com/blog/tutorial-openstack-live-migration-with-kvm-hypervisor-and-nfs-shared-storage/ I'm able to migrate the instance from one compute node to the other compute node using the below command. nova live-migration b33b23f8-4510-4ed3-8cd1-2d68c8186e40 salaria1 The instance is able to migrate properly and that i have confirmed using the sudo virsh list command over the newer compute node. However the problem is when i type nova list at the same time.The status of instance is stuck at migrating and does not changes even after some time. Moreover when i type nova show instance -id command,the old host of the instance is reflected instead of the new one. Please help regarding this. Thanks Abhishek Jain ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Nova Live Migration issue
Thanks Nikolay and Parthipan I have confirmed that the instance is running on the newer compute node by using sudo virsh list command. I'm using below libvirt version .. libvirtd (libvirt) 0.9.8 Actually I will not be able to present the libvirt logs due to setup problem.I'll send logs as soon as possible. Please let me know if any thing needs to be taken care in libvirt during the configuration On Wed, Apr 2, 2014 at 3:00 PM, Parthipan, Loganathan parthi...@hp.comwrote: Can you confirm that it's no longer running on the source node and only running on the destination node? What's your libvirt version? Possibly the libvirt monitor lost connection and didn't complete the post-migration which would update the db. As Nikolay suggested, the libvirt.log would tell more, good if it also had debug turned on. *From:* Nikolay Starodubtsev [mailto:nstarodubt...@mirantis.com] *Sent:* 02 April 2014 09:01 *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] Nova Live Migration issue Hi! Can you show libvirt logs? Nikolay Starodubtsev Software Engineer Mirantis Inc. Skype: dark_harlequine1 2014-04-02 11:55 GMT+04:00 abhishek jain ashujain9...@gmail.com: Hi all I'm following the below link for VM migration from one compute node to the another from the controller node using devstack .. http://www.mirantis.com/blog/tutorial-openstack-live-migration-with-kvm-hypervisor-and-nfs-shared-storage/ I'm able to migrate the instance from one compute node to the other compute node using the below command. nova live-migration b33b23f8-4510-4ed3-8cd1-2d68c8186e40 salaria1 The instance is able to migrate properly and that i have confirmed using the sudo virsh list command over the newer compute node. However the problem is when i type nova list at the same time.The status of instance is stuck at migrating and does not changes even after some time. Moreover when i type nova show instance -id command,the old host of the instance is reflected instead of the new one. Please help regarding this. Thanks Abhishek Jain ___ 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
Re: [openstack-dev] Nova Live Migration issue
Hi Parthi I have confirmed on the destination node i.e( newer compute node on which the instance is migrated ) by using sudo virsh list and the instance is being reflected there. Moreover on the source node the sudo virsh list command reflects nothing. Also I'll try with libvirt 1.x and let you know the result. I'll also try to send you the libvirt logs whenever i try the setup again. Thanks On Wed, Apr 2, 2014 at 5:14 PM, Parthipan, Loganathan parthi...@hp.comwrote: Hello Abhishek, Did you check on the source node whether the instance is still running or even defined (virsh list -all). This is because nova notices that the migration is completed when the VM in the source is gone and then triggers the post-migration. IIRC, there's a bug in 0.x libvirt where the destination qemu disconnection is not picked up by the source libvirt, causing nova migration thread to wait. I don't know if libvirt 1.x works with nova properly yet. Cheers ~parthi *From:* abhishek jain [mailto:ashujain9...@gmail.com] *Sent:* 02 April 2014 12:28 *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] Nova Live Migration issue Thanks Nikolay and Parthipan I have confirmed that the instance is running on the newer compute node by using sudo virsh list command. I'm using below libvirt version .. libvirtd (libvirt) 0.9.8 Actually I will not be able to present the libvirt logs due to setup problem.I'll send logs as soon as possible. Please let me know if any thing needs to be taken care in libvirt during the configuration On Wed, Apr 2, 2014 at 3:00 PM, Parthipan, Loganathan parthi...@hp.com wrote: Can you confirm that it's no longer running on the source node and only running on the destination node? What's your libvirt version? Possibly the libvirt monitor lost connection and didn't complete the post-migration which would update the db. As Nikolay suggested, the libvirt.log would tell more, good if it also had debug turned on. *From:* Nikolay Starodubtsev [mailto:nstarodubt...@mirantis.com] *Sent:* 02 April 2014 09:01 *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] Nova Live Migration issue Hi! Can you show libvirt logs? Nikolay Starodubtsev Software Engineer Mirantis Inc. Skype: dark_harlequine1 2014-04-02 11:55 GMT+04:00 abhishek jain ashujain9...@gmail.com: Hi all I'm following the below link for VM migration from one compute node to the another from the controller node using devstack .. http://www.mirantis.com/blog/tutorial-openstack-live-migration-with-kvm-hypervisor-and-nfs-shared-storage/ I'm able to migrate the instance from one compute node to the other compute node using the below command. nova live-migration b33b23f8-4510-4ed3-8cd1-2d68c8186e40 salaria1 The instance is able to migrate properly and that i have confirmed using the sudo virsh list command over the newer compute node. However the problem is when i type nova list at the same time.The status of instance is stuck at migrating and does not changes even after some time. Moreover when i type nova show instance -id command,the old host of the instance is reflected instead of the new one. Please help regarding this. Thanks Abhishek Jain ___ 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 mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] OPENSTACK SERVICE ERROR
-8020-4f89-bd59-b9cb76126138 None None] DB_Driver.is_up
last_heartbeat = 2014-03-18 14:38:48 elapsed = 6.557583 is_up
/opt/stack/nova/nova/servicegroup/drivers/db.py:71
nova-compute fedora6 nova
enabled:-) 2014-03-18 14:38:48
2014-03-18 15:38:54.558 DEBUG nova.servicegroup.api
[req-84f2b3c1-8020-4f89-bd59-b9cb76126138 None None] Check if the given
member [{'binary': u'nova-compute', 'availability_zone': 'nova', 'deleted':
0L, 'created_at': datetime.datetime(2014, 3, 18, 11, 47, 9), 'updated_at':
datetime.datetime(2014, 3, 18, 14, 38, 48), 'report_count': 1029L, 'topic':
u'compute', 'host': u'fedora7', 'disabled': False, 'deleted_at': None,
'disabled_reason': None, 'id': 7L}] is part of the ServiceGroup, is up
service_is_up /opt/stack/nova/nova/servicegroup/api.py:94
2014-03-18 15:38:54.558 DEBUG nova.servicegroup.drivers.db
[req-84f2b3c1-8020-4f89-bd59-b9cb76126138 None None] DB_Driver.is_up
last_heartbeat = 2014-03-18 14:38:48 elapsed = 6.558705 is_up
/opt/stack/nova/nova/servicegroup/drivers/db.py:71
nova-compute fedora7 nova
enabled:-) 2014-03-18
Thanks
Abhishek Jain
On Tue, Mar 18, 2014 at 6:22 PM, Maldonado, Facundo N
facundo.n.maldon...@intel.com wrote:
Couple of questions,
- Do you have n-cpu running in every node? (controller and both
computes)
- Which services do you have enabled in both compute nodes?
- To which node corresponds the screen log provided?
- What is the output of nova-manage service list?
Facundo.
*From:* Ben Nemec [mailto:openst...@nemebean.com]
*Sent:* Monday, March 17, 2014 1:15 PM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [nova] OPENSTACK SERVICE ERROR
First, please don't use all caps in your subject. Second, please do use
tags to indicate which projects your message relates to. In this case,
that appears to be nova.
As far as the error, it looks like you may have some out of date code.
The line referenced in the backtrace is now line 1049 in api.py, not 953.
That suggests to me that there have been some pretty significant changes
since whatever git revision you're currently using.
-Ben
On 2014-03-15 08:15, abhishek jain wrote:
Hi all
I have installed openstack using devstack and nearly all the functionality
is working fine.
However I'm getting an issue during live migration .
I'm creating a stack of one controller node and two compute nodes i.e
Compute node 1 and compute node 2 .I'm booting one VM at compute node 1 and
need to migrate it over compute node 2.
For this I'm using NFS which is working fine.
Also I have enabled
live_migration_flag=VIR_MIGRATE_UNDEFINE_SOURCE,VIR_MIGRATE_PEER2PEER,VIR_MIGRATE_LIVE
in /etc/nova.conf over both the compute nodes and over controller node.
However when I apply nova live-migration command after restarting the
nova-compute service using screen session the VM is not able to migrate.
Below are the logs after restarting nova-compute service ..
16:33.500 2599 TRACE nova.openstack.common.rpc.amqp
2014-03-15 10:16:33.500 2599 TRACE nova.openstack.common.rpc.amqp File
/opt/stack/nova/nova/network/neutronv2/api.py, line 953, in
_nw_info_build_network
2014-03-15 10:16:33.500 2599 TRACE nova.openstack.common.rpc.amqp
label=network_name,
2014-03-15 10:16:33.500 2599 TRACE nova.openstack.common.rpc.amqp
2014-03-15 10:16:33.500 2599 TRACE nova.openstack.common.rpc.amqp
UnboundLocalError: local variable 'network_name' referenced before
assignment
2014-03-15 10:16:33.500 2599 TRACE nova.openstack.common.rpc.amqp
2014-03-15 10:16:33.500 2599 TRACE nova.openstack.common.rpc.amqp
10$(L) n-cpu* 11$(L) n-cond 12$(L) n-crt 13$(L) n-sch 14$(L) n-novnc
15$(L) n-xvnc 16$(L) n-cauth
Also find the attached screanshot describing the complete error.
Please help regarding this.
Thanks
Abhishek Jain
___
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
Re: [openstack-dev] Neutron error using devstack
Thanks for the help. I'm now able to proceed further with your suggestions. I'm now enabling live migration in /etc/nova/nova.conf by adding the below line live_migration_flag=VIR_MIGRATE_UNDEFINE_SOURCE,VIR_MIGRATE_PEER2PEER,VIR_MIGRATE_LIVE However now i need to restart nova-compute service, but whenever i try to do the same,I'm getting the below logs sudo systemctl restart nova-compute.service Failed to issue method call: Unit nova-compute.service failed to load: No such file or directory. See system logs and 'systemctl status nova-compute.service' for details. Please help regarding this. On Sun, Mar 2, 2014 at 12:42 AM, Elena Ezhova eezh...@mirantis.com wrote: If you want to use Neutron with devstack you have to add the related settings to localrc. Please see https://wiki.openstack.org/wiki/NeutronDevstack for detailed instructions. 01 марта 2014 г. 22:11 пользователь abhishek jain ashujain9...@gmail.com написал: Hi all I have installed devstack successfully from the following link... http://www.linux.com/learn/tutorials/721712-intro-to-openstack-part-two-how-to-install-and-configure-openstack-on-a-server However I'm not able to run the neutron services.The error which generally comes after running neutron command is as follows. neutron subnet-create vxlan-net 10.100.1.0/24 --name vxlan-net You must provide a username via either --os-username or env[OS_USERNAME] ashu@ashu $ ps -ef | grep neutron ashu31039 30660 0 18:09 pts/25 00:00:00 grep --color=auto neutron Please help regarding this ___ 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] Openstack live migration using devstack
Hi all
I have created one openstack using one controller node and one compute node
both installed using devstack.I'm running one instance on controller node
and want to migrate it to over compute node.
I'm using following link for this.
http://docs.openstack.org/grizzly/openstack-compute/admin/content/live-migration-usage.html
http://docs.openstack.org/grizzly/openstack-compute/admin/content/configuring-migrations.html
The output of nova-manage vm list on the compute node is as follows..
10 16:01:49.502 DEBUG nova.openstack.common.lockutils
[req-019d2337-143e-4157-9d6c-3c1f2207f63b None None] Semaphore / lock
released __get_backend inner
/opt/stack/nova/nova/openstack/common/lockutils.py:252
Command failed, please check log for more info
2014-03-10 16:01:49.507 CRITICAL nova
[req-019d2337-143e-4157-9d6c-3c1f2207f63b None None] Could not parse
rfc1738 URL from string ''
2014-03-10 16:01:49.507 9609 TRACE nova Traceback (most recent call last):
2014-03-10 16:01:49.507 9609 TRACE nova File /usr/bin/nova-manage, line
10, in module
2014-03-10 16:01:49.507 9609 TRACE nova sys.exit(main())
2014-03-10 16:01:49.507 9609 TRACE nova File
/opt/stack/nova/nova/cmd/manage.py, line 1378, in main
2014-03-10 16:01:49.507 9609 TRACE nova ret = fn(*fn_args, **fn_kwargs)
2014-03-10 16:01:49.507 9609 TRACE nova File
/opt/stack/nova/nova/cmd/manage.py, line 658, in list
2014-03-10 16:01:49.507 9609 TRACE nova context.get_admin_context(),
host)
2014-03-10 16:01:49.507 9609 TRACE nova File
/opt/stack/nova/nova/db/api.py, line 671, in instance_get_all_by_host
2014-03-10 16:01:49.507 9609 TRACE nova return
IMPL.instance_get_all_by_host(context, host, columns_to_join)
2014-03-10 16:01:49.507 9609 TRACE nova File
/opt/stack/nova/nova/db/sqlalchemy/api.py, line 112, in wrapper
2014-03-10 16:01:49.507 9609 TRACE nova return f(*args, **kwargs)
2014-03-10 16:01:49.507 9609 TRACE nova File
/opt/stack/nova/nova/db/sqlalchemy/api.py, line 2078, in
instance_get_all_by_host
2014-03-10 16:01:49.507 9609 TRACE nova
use_slave=use_slave).filter_by(host=host).all(),
2014-03-10 16:01:49.507 9609 TRACE nova File
/opt/stack/nova/nova/db/sqlalchemy/api.py, line 2066, in
_instance_get_all_query
2014-03-10 16:01:49.507 9609 TRACE nova use_slave=use_slave)
2014-03-10 16:01:49.507 9609 TRACE nova File
/opt/stack/nova/nova/db/sqlalchemy/api.py, line 200, in model_query
2014-03-10 16:01:49.507 9609 TRACE nova session = kwargs.get('session')
or get_session(slave_session=use_slave)
2014-03-10 16:01:49.507 9609 TRACE nova File
/opt/stack/nova/nova/openstack/common/db/sqlalchemy/session.py, line 423,
in get_session
2014-03-10 16:01:49.507 9609 TRACE nova engine =
get_engine(sqlite_fk=sqlite_fk, slave_engine=slave_session)
2014-03-10 16:01:49.507 9609 TRACE nova File
/opt/stack/nova/nova/openstack/common/db/sqlalchemy/session.py, line 561,
in get_engine
2014-03-10 16:01:49.507 9609 TRACE nova sqlite_fk=sqlite_fk)
2014-03-10 16:01:49.507 9609 TRACE nova File
/opt/stack/nova/nova/openstack/common/db/sqlalchemy/session.py, line 629,
in create_engine
2014-03-10 16:01:49.507 9609 TRACE nova connection_dict =
sqlalchemy.engine.url.make_url(sql_connection)
2014-03-10 16:01:49.507 9609 TRACE nova File
/usr/lib/python2.7/site-packages/sqlalchemy/engine/url.py, line 178, in
make_url
2014-03-10 16:01:49.507 9609 TRACE nova return
_parse_rfc1738_args(name_or_url)
2014-03-10 16:01:49.507 9609 TRACE nova File
/usr/lib/python2.7/site-packages/sqlalchemy/engine/url.py, line 219, in
_parse_rfc1738_args
2014-03-10 16:01:49.507 9609 TRACE nova Could not parse rfc1738 URL
from string '%s' % name)
2014-03-10 16:01:49.507 9609 TRACE nova ArgumentError: Could not parse
rfc1738 URL from string ''
2014-03-10 16:01:49.507 9609 TRACE nova
Please help me regarding the above error.
Thanks
Abhishek Jain
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Neutron error using devstack
Hi all I have installed devstack successfully from the following link... http://www.linux.com/learn/tutorials/721712-intro-to-openstack-part-two-how-to-install-and-configure-openstack-on-a-server However I'm not able to run the neutron services.The error which generally comes after running neutron command is as follows. neutron subnet-create vxlan-net 10.100.1.0/24 --name vxlan-net You must provide a username via either --os-username or env[OS_USERNAME] ashu@ashu $ ps -ef | grep neutron ashu31039 30660 0 18:09 pts/25 00:00:00 grep --color=auto neutron Please help regarding this ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
