Re: [Openstack] RFC: Thoughts on improving OpenStack GIT commit practice/history
At the very least it is always possible to describe what area of the code is being changed, so that you alert the reviewers you are familiar with that area. Yes, Makes sense. -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Devstack]Keystone authentication problem when installing
In my setup, I have SERVICE_TOKEN defined in localrc, which is used by stack.sh (via read_password function) to set the environment variable, eventually to be used by keystone_data.sh (But probably you know all that) and I don't see the error. (But I somehow still have prettytable 0.5 - so my guess given below - which may be incorrect and/or confusing - sorry about that) Re What I can't figure out is what changed in the last couple days - I am not sure :( -Mandar From: Gabriel Hurley [mailto:gabriel.hur...@nebula.com] Sent: Friday, June 29, 2012 2:02 AM To: Ke Wu; Vaze, Mandar Cc: openstack mail list Subject: RE: [Openstack] [Devstack]Keystone authentication problem when installing I'm seeing this error too. It appears that the environment variables (SERVICE_TOKEN, etc.) aren't getting exported, causing keystoneclient to not find them in the environment and triggering that error. What I can't figure out is what changed in the last couple days to make this suddenly stop working. :-/ I'm still looking into it on my end, but any other ideas would be helpful. - Gabriel From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.netmailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net [mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net]mailto:[mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of Ke Wu Sent: Thursday, June 28, 2012 10:28 AM To: Vaze, Mandar Cc: openstack mail list Subject: Re: [Openstack] [Devstack]Keystone authentication problem when installing Thanks Mandar, Yet could you please explain it in detail? I am pretty new to devstack and didn't see the relationship between the bugs you mentioned and the error I encountered. Appreciate it! -K On Jun 27, 2012, at 9:27 PM, Vaze, Mandar wrote: May be related to https://bugs.launchpad.net/keystone/+bug/995976 Check last comment at https://bugs.launchpad.net/keystone/+bug/995811 -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.netmailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.netmailto:nttdata@lists.launchpad.net] On Behalf Of Ke Wu Sent: Thursday, June 28, 2012 7:01 AM To: openstack mail list Subject: [Openstack] [Devstack]Keystone authentication problem when installing Hi, I can't find a mailing list of devstack so I choose to ask here, hope this doesn't spam you guys. I was trying to build Devstack on my VM (Ubuntu 12.04 server) to start a new environment for Horizon development. Everything went well until it hit the point to start Keystone service, the error msg was: Expecting authentication method via either a service token, --token or env[SERVICE_TOKEN], or credentials, --os_username or env[OS_USERNAME]. + NOVA_USER_ID= ++ get_field 1 ++ read data ++ grep ' service ' ++ keystone tenant-list Expecting authentication method via either a service token, --token or env[SERVICE_TOKEN], or credentials, --os_username or env[OS_USERNAME]. + NOVA_TENANT_ID= ++ keystone ec2-credentials-create --user --tenant_id usage: keystone ec2-credentials-create [--user_id user-id] [--tenant_id tenant-id] keystone ec2-credentials-create: error: argument --user_id: expected one argument + CREDS= ++ failed ++ local r=2 ++ set +o xtrace Anybody has an idea why this happened? Thanks! -Ke Wu __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] RFC: Thoughts on improving OpenStack GIT commit practice/history
I particularly hate the single-line Fixes bug 1234566-type commit messages. I assume your concern was regarding commits where Fixes bug 1234566 is the first and ONLY line. Fixes bug 1234566 comes from Wiki. Plus there is restriction on how long the first line of the commit message can be. Not everyone is able to describe their change in one short sentence. So typically *I* put Fixes bug 1234567 on the *first* line followed by additional lines describing the change. http://wiki.openstack.org/GerritWorkflow#Committing_Changes should be updated when this discussion is concluded. -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Devstack]Keystone authentication problem when installing
May be related to https://bugs.launchpad.net/keystone/+bug/995976 Check last comment at https://bugs.launchpad.net/keystone/+bug/995811 -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Ke Wu Sent: Thursday, June 28, 2012 7:01 AM To: openstack mail list Subject: [Openstack] [Devstack]Keystone authentication problem when installing Hi, I can't find a mailing list of devstack so I choose to ask here, hope this doesn't spam you guys. I was trying to build Devstack on my VM (Ubuntu 12.04 server) to start a new environment for Horizon development. Everything went well until it hit the point to start Keystone service, the error msg was: Expecting authentication method via either a service token, --token or env[SERVICE_TOKEN], or credentials, --os_username or env[OS_USERNAME]. + NOVA_USER_ID= ++ get_field 1 ++ read data ++ grep ' service ' ++ keystone tenant-list Expecting authentication method via either a service token, --token or env[SERVICE_TOKEN], or credentials, --os_username or env[OS_USERNAME]. + NOVA_TENANT_ID= ++ keystone ec2-credentials-create --user --tenant_id usage: keystone ec2-credentials-create [--user_id user-id] [--tenant_id tenant-id] keystone ec2-credentials-create: error: argument --user_id: expected one argument + CREDS= ++ failed ++ local r=2 ++ set +o xtrace Anybody has an idea why this happened? Thanks! -Ke Wu __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Nova image-list error
Try nova --debug image-list - It should give you more information/stack trace. -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Trinath Somanchi Sent: Tuesday, June 26, 2012 3:24 PM To: openstack@lists.launchpad.net Subject: [Openstack] Nova image-list error Hi- I have uploaded an image using glance. $ glance index command has given the output. But nova image-list is giving me error. root@OpenstackController:~# glance add name=Ubuntu_1204_Server is_public=true container_format=ovf disk_format=qcow2 ubuntu_server.img Uploading image 'Ubuntu_1204_Server' [100%] 24.9M/s, ETA 0h 0m 0s Added new image with ID: 5fde92d7-84da-49a5-b690-4ebdf7c1b2d4 root@OpenstackController:~# glance index ID Name Disk Format Container Format Size -- -- 5fde92d7-84da-49a5-b690-4ebdf7c1b2d4 Ubuntu_1204_Server qcow2 ovf 1544224768 root@OpenstackController:~# nova image-list ERROR: string indices must be integers, not str root@OpenstackController:~# Can any one help me out in resolving the issue. thanking you... -- Regards, -- Trinath Somanchi, +91 9866 235 130 __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Openstack Dashboard Error
See https://lists.launchpad.net/openstack/msg12548.html to get debug information on the webpage -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Trinath Somanchi Sent: Monday, June 25, 2012 5:16 PM To: Gabriel Hurley Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Openstack Dashboard Error Hi- I'm seeing this error, when I login to the Openstack Dashboard in the apache2 error logs .. [error] No handlers could be found for logger openstack_dashboard In the Webpage its displaying Internal Server Error An unexpected error occurred while processing your request. Please try your request again. Can any one help me out in resolving the issue... Thanking you... On Mon, Jun 25, 2012 at 10:48 AM, Gabriel Hurley gabriel.hur...@nebula.commailto:gabriel.hur...@nebula.com wrote: It sounds like your local_settings.py file is missing any logging configuration. The default config from the local_settings.py.example file is a good place to start. If that’s not the case, then it would be helpful to know how you installed OpenStack/Horizon, what you’ve done to configure it, etc. All the best, - Gabriel From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.netmailto:nebula@lists.launchpad.net [mailto:openstack-bounces+gabriel.hurleymailto:openstack-bounces%2Bgabriel.hurley=nebula@lists.launchpad.netmailto:nebula@lists.launchpad.net] On Behalf Of Trinath Somanchi Sent: Sunday, June 24, 2012 10:03 PM To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: [Openstack] Openstack Dashboard Error Hi- I'm seeing this error when I access the Openstack Dashboard through my browser. [error] No handlers could be found for logger openstack_dashboard. Please help me resolve this issue. -- Regards, -- Trinath Somanchi, +91 9866 235 130tel:%2B91%209866%20235%20130 -- Regards, -- Trinath Somanchi, +91 9866 235 130 __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Noob question about api client access
Based on the error, I think the machine where you are running nova client is unable to connect to nova-api server. You can try nova --debug list, This might give you some clue/help troubleshoot further. -Mandar -Original Message- From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Jonathan Proulx Sent: Sunday, June 24, 2012 8:40 PM To: openstack@lists.launchpad.net Subject: [Openstack] Noob question about api client access Hi All, I have a shiny new install of openstack and from the controller node (the one with keystone, glance, horizon and all the nova pieces) I can run everything as I expect using the nova cli tools upload images boot instances manage the network, etc. I can also use the Horizon wed interface from remote systems just fine (of course all the actual commands are run locally on the controller) Where it get weird is when I try to use the nova cli on a remote client. Using the same openrc to set up the environment nova credentials returns the expected result but all the other commands I've tried (mostly of the list variety) fail like this: $ nova list ERROR: n/a (HTTP 400) The install is Essex on Ubuntu Precise which I deployed using the Puppet OpenStack module. The example config puppet deployed for me was only listening on 127.0.0.1 so I had to change the bind_host in /etc/keystone/keystone.conf from 127.0.0.1 to 0.0.0.0 to get the 'nova credentials' to run. I've been sifting through the OpenStack Compute Starter Guide and greping for and replacing references to localhost or 127.0.0.1 in the various configs I alsoe tried adding --allow_admin_api=true to the nova.conf which was in the openstack docs but not in my conf, but I'm clearly still missing something. Hopefully this is obvious to some one more familiar with all the pieces? Thanks, -Jon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] HVM for KVM
Ø Does this Controller machine requires Hardware virtualization support for KVM libvirt ? Yes. To be accurate nova-compute needs hardware virtualization support . Otherwise you can use “libvirt_type=qemu” Check http://docs.openstack.org/trunk/openstack-compute/admin/content/kvm.html#checking-kvm -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Trinath Somanchi Sent: Thursday, June 21, 2012 11:44 AM To: openstack@lists.launchpad.net Subject: [Openstack] HVM for KVM Hi- I have setup a Controller with all openstack components but this server does'nt support Hardware virtuvalization for KVM. The other server which is the host where virtual machines are created supports HVM for KVM. Does this Controller machine requires Hardware virtualization support for KVM libvirt ? -- Regards, -- Trinath Somanchi, +91 9866 235 130 __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] ssh not authenticating
Default password for cirros is cubswin:) - including the smiley I hope you entered correct password (It is easy to ignore the last two characters thinking it is a smiley) Other options is to use password less ssh login using keypair. See http://docs.openstack.org/essex/openstack-compute/starter/content/Launch_and_manage_instances-d1e1885.html -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of udit agarwal Sent: Thursday, June 21, 2012 11:13 AM To: openstack@lists.launchpad.net Subject: [Openstack] ssh not authenticating Hi, I have setup openstack on my system using the manual http://docs.openstack.org/essex/openstack-compute/install/apt/content/. I tried to run the test image cirros on my system. While I can easily ping it, I faced some problems in authenticating via ssh. First, it asks for password, even providing the correct password for the same, it re asked the password 2 more times and finally denied me the permission. I couldn't resolve this issue then. Can anybody help me with this??? thanks in advance. --Udit __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Instances not starting after changing host flag
This may not be related to host flag. See similar problem being discussed in this thread : https://lists.launchpad.net/openstack/msg13314.html (Same symptoms as yours, error in allocate_for_instance, rpc timeouts) -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Czubak, Piotr Sent: Thursday, June 21, 2012 2:28 PM To: openstack@lists.launchpad.net Subject: [Openstack] Instances not starting after changing host flag Hi All, I have Essex set up and running, everything works fine till I try to change host flag in nova.conf: --host=test After reboot, instances don't start, only error is reported. Any ideas how to fix this? Logs from nova-compute and nova-network attached below. Regards, Piotr Czubak Logs from nova-compute.log: Timed out waiting for RPC response: timed out 2012-06-21 04:35:16 TRACE nova.rpc.common Traceback (most recent call last): 2012-06-21 04:35:16 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py, line 490, in ensure 2012-06-21 04:35:16 TRACE nova.rpc.common return method(*args, **kwargs) 2012-06-21 04:35:16 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py, line 567, in _consume 2012-06-21 04:35:16 TRACE nova.rpc.common return self.connection.drain_events(timeout=timeout) 2012-06-21 04:35:16 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/connection.py, line 175, in drain_events 2012-06-21 04:35:16 TRACE nova.rpc.common return self.transport.drain_events(self.connection, **kwargs) 2012-06-21 04:35:16 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line 238, in drain_events 2012-06-21 04:35:16 TRACE nova.rpc.common return connection.drain_events(**kwargs) 2012-06-21 04:35:16 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line 57, in drain_events 2012-06-21 04:35:16 TRACE nova.rpc.common return self.wait_multi(self.channels.values(), timeout=timeout) 2012-06-21 04:35:16 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line 63, in wait_multi 2012-06-21 04:35:16 TRACE nova.rpc.common chanmap.keys(), allowed_methods, timeout=timeout) 2012-06-21 04:35:16 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line 120, in _wait_multiple 2012-06-21 04:35:16 TRACE nova.rpc.common channel, method_sig, args, content = read_timeout(timeout) 2012-06-21 04:35:16 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line 94, in read_timeout 2012-06-21 04:35:16 TRACE nova.rpc.common return self.method_reader.read_method() 2012-06-21 04:35:16 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/amqplib/client_0_8/method_framing.py, line 221, in read_method 2012-06-21 04:35:16 TRACE nova.rpc.common raise m 2012-06-21 04:35:16 TRACE nova.rpc.common timeout: timed out 2012-06-21 04:35:16 TRACE nova.rpc.common Instance failed network setup 2012-06-21 04:35:16 TRACE nova.compute.manager [instance: acefc36d-81bf-4352-9cb6-ca0228315473] Traceback (most recent call last): 2012-06-21 04:35:16 TRACE nova.compute.manager [instance: acefc36d-81bf-4352-9cb6-ca0228315473] File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 559, in _allocate_network 2012-06-21 04:35:16 TRACE nova.compute.manager [instance: acefc36d-81bf-4352-9cb6-ca0228315473] requested_networks=requested_networks) 2012-06-21 04:35:16 TRACE nova.compute.manager [instance: acefc36d-81bf-4352-9cb6-ca0228315473] File /usr/lib/python2.7/dist-packages/nova/network/api.py, line 170, in allocate_for_instance 2012-06-21 04:35:16 TRACE nova.compute.manager [instance: acefc36d-81bf-4352-9cb6-ca0228315473] 'args': args}) 2012-06-21 04:35:16 TRACE nova.compute.manager [instance: acefc36d-81bf-4352-9cb6-ca0228315473] File /usr/lib/python2.7/dist-packages/nova/rpc/__init__.py, line 68, in call 2012-06-21 04:35:16 TRACE nova.compute.manager [instance: acefc36d-81bf-4352-9cb6-ca0228315473] return _get_impl().call(context, topic, msg, timeout) 2012-06-21 04:35:16 TRACE nova.compute.manager [instance: acefc36d-81bf-4352-9cb6-ca0228315473] File /usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py, line 674, in call 2012-06-21 04:35:16 TRACE nova.compute.manager [instance: acefc36d-81bf-4352-9cb6-ca0228315473] return rpc_amqp.call(context, topic, msg, timeout, Connection.pool) 2012-06-21 04:35:16 TRACE nova.compute.manager [instance: acefc36d-81bf-4352-9cb6-ca0228315473] File /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py, line 338, in call 2012-06-21 04:35:16 TRACE nova.compute.manager [instance: acefc36d-81bf-4352-9cb6-ca0228315473] rv = list(rv) 2012-06-21 04:35:16 TRACE nova.compute.manager [instance:
Re: [Openstack] AttributeError: virDomain instance has no attribute 'reset'
Found this bug (albeit for Fedora 16) https://bugs.launchpad.net/nova/+bug/1011863 I've updated the bug with my details Does that mean Folsom won't be supported on Ubuntu 11.10 ? -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Vaze, Mandar Sent: Friday, June 22, 2012 9:41 AM To: Vishvananda Ishaya Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] AttributeError: virDomain instance has no attribute 'reset' Vish, I'm running on Ubuntu 11.10 (GNU/Linux 3.0.0-12-server x86_64) When I tried to upgrade I got the following message libvirt-bin is already the newest version. libvirt0 is already the newest version. python-libvirt is already the newest version. Which package should I upgrade/install ? Thanks, -Mandar From: Vishvananda Ishaya [mailto:vishvana...@gmail.com]mailto:[mailto:vishvana...@gmail.com] Sent: Friday, June 22, 2012 12:13 AM To: Vaze, Mandar Subject: Re: AttributeError: virDomain instance has no attribute 'reset' the reset command was only recently added to libvirt, so your version is probably just to old. We have discussed adding a fallback of shutting down and restarting the domain if reset is not defined, but no one has implemented it yet. Vish On Jun 21, 2012, at 5:56 AM, Vaze, Mandar wrote: Vish, I recently merged my code with master after a few weeks. Now I'm getting the error mentioned in the subject line during reboot. I looked at the history and this change is done in the following commit by you. https://github.com/openstack/nova/commit/ae878fc8b9761d099a4145617e4a48cbeb390623 I also realized that you have defined reset() method in fakelibvirt for testing - so may be tests pass OK. I'm using libvirt_type=kvm Do I need to update any library (python or otherwise) for this change ? Any other suggestions to troubleshoot this ? Thanks, -Mandar Here is relevant snippet from my debug session : /opt/stack/nova/nova/virt/libvirt/connection.py(847)_hard_reboot() - virt_dom.reset(0) (Pdb) dir(virt_dom) ['ID', 'OSType', 'UUID', 'UUIDString', 'XMLDesc', '__del__', '__doc__', '__init__', '__module__', '_conn', '_o', 'abortJob', 'attachDevice', 'attachDeviceFlags', 'autostart', 'blkioParameters', 'blockInfo', 'blockPeek', 'blockStats', 'connect', 'coreDump', 'create', 'createWithFlags', 'destroy', 'detachDevice', 'detachDeviceFlags', 'hasCurrentSnapshot', 'hasManagedSaveImage', 'info', 'injectNMI', 'interfaceStats', 'isActive', 'isPersistent', 'isUpdated', 'jobInfo', 'managedSave', 'managedSaveRemove', 'maxMemory', 'maxVcpus', 'memoryParameters', 'memoryPeek', 'memoryStats', 'migrate', 'migrate2', 'migrateSetMaxDowntime', 'migrateSetMaxSpeed', 'migrateToURI', 'migrateToURI2', 'name', 'openConsole', 'pinVcpu', 'reboot', 'resume', 'revertToSnapshot', 'save', 'schedulerParameters', 'schedulerParametersFlags', 'schedulerType', 'screenshot', 'setAutostart', 'setBlkioParameters', 'setMaxMemory', 'setMemory', 'setMemoryFlags', 'setMemoryParameters', 'setSchedulerParameters', 'setSchedulerParametersFlags', 'setVcpus', 'setVcpusFlags', 'shutdown', 'snapshotCreateXML', 'snapshotCurrent', 'snapshotListNames', 'snapshotLookupByName', 'snapshotNum', 'state', 'suspend', 'undefine', 'updateDeviceFlags', 'vcpus', 'vcpusFlags'] (Pdb) type( virt_dom) type 'instance' (Pdb) type(virt_dom) type 'instance' (Pdb) n AttributeError: virDomain instance has no attribute 'reset' __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Nova scheduler
When I tried this on post-essex release code, I got : error: unrecognized arguments: --force_hosts=hostname Try --hint force_hosts=hostname instead -Mandar -Original Message- From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of heut2008 Sent: Tuesday, June 19, 2012 2:30 PM To: Neelakantam Gaddam Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Nova scheduler you should use admin credentials ,then run instances by adding an option --force_hosts=node1 to nova boot . 2012/6/19 Neelakantam Gaddam neelugad...@gmail.com: Hi All, Nova scheduler decides the compute host for the VM instances to run based on the selected scheduling algorithm. Is it possible to choose a particular compute host for each request where a VM instance should run ? -- Thanks Regards Neelakantam Gaddam ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [keystone] Keystone on port 5000 - proposing change default port to 8770
public_port is configurable via keystone.conf - so if port 5000 is blocked in specific setup, it is trivial to change it to some other port. why make so many changes (REST docs, XML docs, devstack, and the code) for a parameter that can be easily tweaked ? -Mandar -Original Message- From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Joseph Heck Sent: Thursday, June 21, 2012 4:46 AM To: openstack@lists.launchpad.net (openstack@lists.launchpad.net) Subject: [Openstack] [keystone] Keystone on port 5000 - proposing change default port to 8770 At the risk of a terrible public tar and feathering... I've learned that port 5000 (which Keystone is using for it's default public-token-auth stuff) is commonly blocked by many firewalls, as it's been registered as a Microsoft uPnP port. I thought I'd go ahead and propose changing the default to 8770. I picked this number because it's close to the Nova ports in common use (8773, 8774, 8775, and 8776). And yes, I'll submit updates to all REST docs, XML docs, devstack, and the code. So... how many people do I need to worry about murdering me for this next design summit? -joe ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Attribute error
Udit, What setup are you using ? devstack ? Did you start this getting error recently ? Did anything change on your system? This (https://lists.launchpad.net/openstack/msg11123.html) thread suggests code was updated without updating api-paste.ini (Not sure if it applies to you since you haven't provided details about your setup) -- pipeline_factory is referenced in /etc/nova/api-paste.ini as follows : [composite:openstack_compute_api_v2] use = call:nova.api.auth:pipeline_factory (There may be several instances of the last line, say for ec2cloud etc.) pipeline_factory is a method in nova/api/auth.py (which is what the above line signifies) You can open nova/api/auth.py in an editor and look at def pipeline_factory -- See if the above background helps you troubleshoot the issue. -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Udit Agarwal Sent: Thursday, June 14, 2012 1:57 PM To: openstack@lists.launchpad.net Subject: [Openstack] Attribute error Hi, On running 'service openstack-nova-api restart' I am getting error such as 'AttributeError : 'module' object has no attribute 'pipeline_factory''. Can anyone help me with this?? Thanks in advance. --Udit Agarwal __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [OpenStack][Nova]Start and Stop vm instances
Here is my question: 1. Is the stop operation of vm instance means to delete the vm and keep nothing except keep this record in databases ? 2. Is the start operation of vm means to creat a new vm instance according to the recorde in databases ? While some hypervisors like Xen (Look at _shutdown method in nova/virt/xenapi/vmops.py) seem to have shutdown functionality, for libvirt_type=kvm - there is no separate shutdown/stop. (Probably that’s why) compute manager calls self.driver.destroy from _shutdown_instance() method - Look at nova/compute/manager.py if interested. Hope this helps. -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Development/Debugging
Salman, I haven't used UI tools like Pydev and/or eclipse. I have a devstack installation running on linux box where I use ssh for all my development. TL;DR Version : I use pdb (aka Python Debugger) It is very easy to use if you have used gdb - (Refer to http://docs.python.org/library/pdb.html#debugger-commands if you are unfamiliar with pdb) Longer Version: * To trace how the allocate_for_instance works for Quantum - put pdb.set_trace() in method def allocate_for_instance in file nova/network/quantum/manager.py You also need import pdb somewhere at the top in the same file. * Stop and restart nova-network process from screen (So that modified nova/network/quantum/manager.py is used.) * Try to create an instance (which eventually needs to allocate fixed IP for the instance) Now go to nova-network console - as soon as RPC call is made to the method allocate_for_instance , execution will stop and you are presented with (pdb) interactive prompt - From here on you can debug using pdb commands -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Salman Malik Sent: Monday, June 11, 2012 10:49 PM To: openstack@lists.launchpad.net Subject: [Openstack] Development/Debugging Hi All, I have been trying to get my head around the OpenStack functionality for a while now but unfortunately haven't been able to grasp it. I am interested on working on Quantum (and may be creating new plugins) but I am still unable to debug my own problems. So I thought it would be best for me to learn from how code works. Although I have been looking at the code for quite some time but didn't get anywhere. Now I have installed Pydev on Eclipse and am wondering how to run the massive OpenStack code in debug mode (so as to learn the call/control flow) ? So I thought I could get some help from OpenStack gurus like how do you people develop/debug problems ? What environment are you using ? Any suggestions/tips are welcome. (Please note that I have read the nova and Quantum administration guides and also looked at the nova developer's guide) Any help would be much appreciated. Thanks, Salman __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Development/Debugging
... so it makes sense to go through each daemon at a time using pdb. Not sure what you mean, but you can easily put set_trace() in multiple daemons at the simultaneously, in fact it is useful to trace the flow across various openstack services. -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Examples of authentication using the glance REST API?
I think glance uses keystone for authentication (default setup) See https://lists.launchpad.net/openstack/msg12661.html and http://docs.openstack.org/api/openstack-compute/programmer/content/using-python-to-obtain-the-authentication-token.html for how to get auth token Once you use authenticate against keystone, you can get the auth-token and set it as X-Auth-Token http header -Mandar -Original Message- From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Michael Still Sent: Monday, June 11, 2012 9:16 AM To: openstack@lists.launchpad.net Subject: [Openstack] Examples of authentication using the glance REST API? Hi. I am trying to find an example of how to do authentication using the glance REST API. I assume there are some HTTP headers that I need to set, but a pointer to some existing code which does this would be appreciated. This is part of porting the glance replicator to use the REST API instead of the client library. Thanks heaps, Mikal ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Glance : How to inform user that snapshot has run into error ?
Hi, Related to instance being stuck in image_snapshot for extended period of time, it is easy to recover the instance (script uses pre-defined timeout to guess that snapshot has hung and will never complete) and bring it back to usable state, I also the *inform the user that their snapshot attempt has failed*. The image goes thru the following statuses during normal case : Queued - Saving - Active - Deleted If the upload of the image fails checksum verification, status is marked as killed (Using _safe_kill() - a private method) Neither of killed and deleted instances are shown to the user either in Dashboard (Horizon) or nova image-list So when recovering hung snapshot - what status should be set for the image ? (Such that user knows of the error) I'm thinking that we need to either Introduce a new status like error OR 1. Modify glance/registry/db/api.py : image_get_all() to return images with killed status (currently it is explicitly filtered out) AND 2. Expose an API to set the image status to killed (Currently _safe_kill is a private method) When I tried #1 above locally and set status of one of the images to killed directly in DB, manually then : 1. nova image-list showed this image status as ERROR 2. Dashboard/Horizon show the status as Killed Please suggest if you can think of better way to handle this. -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack :: Instance Spawning Error
Ø The Image is moving from the states Scheduling, Networking and to Spawning. In the Spawning phase, a Error is returned. What error do you see ? If you haven’t enabled logging, please do and see if there are any errors – especially in nova-compute log. Which hypervisor are you using ? (Since the error is during “spawning” – it could be related to hypervisor.) -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Understanding shutdown VM behavior
But the pickle is the case where a user initiates a shutdown inside the VM. What's the expected behavior after it's detected? Should it respect the shutdown_terminate flag or work more like an OS API? Right now when a shutdown in a VM is detected, the vm state is updated to SHUTOFF and that's pretty much it.. If you are referring to _sync_power_states periodic task, I think current behavior is correct - All it does it matches the real vm state with that in DB. The task is not invoked in response to any user action , just housekeeping task. -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] FW: Cannot access nova instances from dashboard
Sharing with the community, so that it would be useful for others as reference. From: Raghuram Bondalapati [mailto:raghuram.bondalap...@gmail.com] Sent: Thursday, May 31, 2012 11:16 AM To: Vaze, Mandar Subject: Re: [Openstack] Cannot access nova instances from dashboard I have enabled Debug and now understand what might be happening. Dashboard is expecting a service endpoint for volume service and i have not created one. I will try creating a volume service endpoint and retry. Thanks so much for providing the pointer. Exception Type: ServiceCatalogException Exception Value: Invalid service catalog service: volume On Wed, May 30, 2012 at 10:34 PM, Raghuram Bondalapati raghuram.bondalap...@gmail.commailto:raghuram.bondalap...@gmail.com wrote: Mandar, Thanks for the response. I will enable DEBUG and see if anyting pops up. Yes, i have a ':' between $my_ip and 5000. Have a typo in my paste below. On Wed, May 30, 2012 at 9:42 PM, Vaze, Mandar mandar.v...@nttdata.commailto:mandar.v...@nttdata.com wrote: Can you try setting DEBUG=True (For troubleshooting only) in openstack_dashboard/settings.py ? (and then restart Horizon/Dashboard) Then you may get more information when you run into the following error. -Mandar P.S: I assume that you have : between $my_ip and 5000 in OPENSTACK_KEYSTONE_URL From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.netmailto:nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vazemailto:openstack-bounces%2Bmandar.vaze=nttdata@lists.launchpad.netmailto:nttdata@lists.launchpad.net] On Behalf Of Raghuram Bondalapati Sent: Thursday, May 31, 2012 5:13 AM To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: [Openstack] Cannot access nova instances from dashboard Hello, when logged in as 'adminUser' [part of admin role] into dash board i cannot access 'Instances Volumes' tab. When i click on it i get the below error. However i can create instances as the same user from CLI usina 'nova boot' command. All my services and users are created in the same tenant. Not sure if that has any implications wrt to the below error. Internal Server Error An unexpected error occurred while processing your request. Please try your request again. I canmnot find anything usefull from the apache logs except for the below message. [Wed May 30 16:08:40 2012] [error] No handlers could be found for logger openstack_dashboard Dashboard configuration is pated below. OPENSTACK_HOST = 10.2.83.20 OPENSTACK_KEYSTONE_URL = http://$my_ip5000/v2.0; OPENSTACK_KEYSTONE_ADMIN_URL = http://$my_ip:35357/v2.0; OPENSTACK_KEYSTONE_DEFAULT_ROLE = admin Any ideas/suggestions are very much appreciated. Thanks! __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] release fixed_ip
Which IPAM ? This behavior is fixed for mélange IPAM . Please look at https://bugs.launchpad.net/melange/+bug/971504 Also see this : https://bugs.launchpad.net/nova/+bug/973442 -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Endre Karlson Sent: Tuesday, May 29, 2012 2:08 PM To: openstack@lists.launchpad.net Subject: Re: [Openstack] release fixed_ip Are you using Quantum? Endre. 2012/5/29 William Herry william.herry.ch...@gmail.commailto:william.herry.ch...@gmail.com Hi I noticed that when I delete a instance, the fixed ip that associate with it will not be used for other newly launched instance I want to know if there is a timeout for a fixed ip to be reused, how long this time is Thanks -- William Herry williamherrych...@gmail.commailto:williamherrych...@gmail.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] release fixed_ip
I want to know if there is a timeout for a fixed ip to be reused, how long this time is Parameter you are looking for is fixed_ip_disassociate_timeout. Set it to low value like 1 (This is number of seconds) Default value is 600 i.e. 10 minutes. -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] devstack installation failing
Salman,
Can you confirm that ALL your projects are up-to-date ? As I mentioned in my
original response, I got this error because my nova project was updated, and
keystone was not.
You can run the following command on the terminal from the directory that has
all your Openstack projects (e.g. from /opt/stack)
cd /opt/stack ; for d in `ls -1`; do echo updating $d; cd $d; git pull; cd
/opt/stack; done
-Mandar
From: Salman Malik [mailto:salma...@live.com]
Sent: Thursday, May 24, 2012 7:47 PM
To: dolph.math...@gmail.com; Vaze, Mandar
Cc: openstack@lists.launchpad.net
Subject: RE: [Openstack] devstack installation failing
Thanks guys. Here is the output of the curl command:
{error: {message: Invalid tenant, code: 401, title: Not Authorized}}
Seems like there is no such tenant in keystone database. I tried doing keystone
tenant-list but it keeps on asking for one extra argument each time (i.e after
keystone tenant-list, I tried keystone --os_username admin tenant-list and
keystone --os_username --os_password tenant-list ). Anyway, what could be th
cause of keystone's database problems?
Date: Thu, 24 May 2012 00:40:19 -0500
Subject: Re: [Openstack] devstack installation failing
From: dolph.math...@gmail.commailto:dolph.math...@gmail.com
To: mandar.v...@nttdata.commailto:mandar.v...@nttdata.com
CC: salma...@live.commailto:salma...@live.com;
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
The output to the curl command below should definitely point you in the right
direction -- devstack is expecting keystone to return an authentication
response there, but it's getting something else instead. Feel free to paste the
results to the list.
-Dolph
On Wed, May 23, 2012 at 11:47 PM, Vaze, Mandar
mandar.v...@nttdata.commailto:mandar.v...@nttdata.com wrote:
Last time when I ran into this error, I had updated (git pull) only nova, but
forgot to update keystone.
Once I updated (git pull) all the other projects, including keystone, the error
went away.
Few things you can use for troubleshooting :
1. Run this command from terminal - See if the outpur gives any clue :
curl -s -d '{auth:{passwordCredentials: {username: admin, password:
nova}, tenantName: admin}}' -H 'Content-type: application/json'
http://10.0.3.15:5000/v2.0/tokens;
2. Check the keystone database, see if user admin and tenant admin are
created OK
-Mandar
From:
openstack-bounces+mandar.vaze=nttdata@lists.launchpad.netmailto:nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vazemailto:openstack-bounces%2Bmandar.vaze=nttdata@lists.launchpad.netmailto:nttdata@lists.launchpad.net]
On Behalf Of Salman Malik
Sent: Thursday, May 24, 2012 9:48 AM
To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: [Openstack] devstack installation failing
Hi All,
While installing devstack, installation is failing with the error :
++ python -c 'import sys; import json; tok = json.loads(sys.stdin.read());
print tok['\''access'\'']['\''token'\'']['\''id'\''];'
++ curl -s -d '{auth:{passwordCredentials: {username: admin,
password: nova}, tenantName: admin}}' -H 'Content-type:
application/json' http://10.0.3.15:5000/v2.0/tokens
Traceback (most recent call last):
File string, line 1, in module
KeyError: 'access'
With some searching I know this has something to do with the keystone but I
have no clue how to resolve this one.
Thanks for your help.
Salman
__
Disclaimer:This email and any attachments are sent in strictest confidence for
the sole use of the addressee and may contain legally privileged, confidential,
and proprietary data. If you are not the intended recipient, please advise the
sender by replying promptly to this email and then delete and destroy this
email and any attachments without any further use, copying or forwarding
___
Mailing list:
https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack
Post to :
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Unsubscribe :
https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack
More help : https://help.launchpad.net/ListHelp
__
Disclaimer:This email and any attachments are sent in strictest confidence for
the sole use of the addressee and may contain legally privileged, confidential,
and proprietary data. If you are not the intended recipient, please advise the
sender by replying promptly to this email and then delete and destroy this
email and any attachments without any further use, copying or forwarding___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] nova state machine simplification and clarification
I'd like to understand the difference between a soft and hard delete. soft_delete is invoked when reclaim_instance_interval flag is set to non-zero. In this case, when delete command is fired, only the VM is powered off, and vm_state is set to SOFT_DELETE Other resources (like network, volume, and files created in instances_path etc) are cleaned up at later point via a periodic task. What exactly is a hard delete from the standpoint of a customer? Is this just a delete hard_delete is when vm is destroyed (As opposed to power off) and resources are cleaned up immediately. This is the default configuration -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] nova state machine simplification and clarification
Sorry for responding to old thread, I later realized that Yun had already responded to Gabe's query. -Original Message- From: Vaze, Mandar Sent: Friday, May 25, 2012 6:10 PM To: 'Gabe Westmaas'; Mark Washenberger; openstack@lists.launchpad.net; yun...@gmail.com Subject: RE: [Openstack] nova state machine simplification and clarification I'd like to understand the difference between a soft and hard delete. soft_delete is invoked when reclaim_instance_interval flag is set to non-zero. In this case, when delete command is fired, only the VM is powered off, and vm_state is set to SOFT_DELETE Other resources (like network, volume, and files created in instances_path etc) are cleaned up at later point via a periodic task. What exactly is a hard delete from the standpoint of a customer? Is this just a delete hard_delete is when vm is destroyed (As opposed to power off) and resources are cleaned up immediately. This is the default configuration -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] devstack installation failing
Last time when I ran into this error, I had updated (git pull) only nova, but
forgot to update keystone.
Once I updated (git pull) all the other projects, including keystone, the error
went away.
Few things you can use for troubleshooting :
1. Run this command from terminal - See if the outpur gives any clue :
curl -s -d '{auth:{passwordCredentials: {username: admin, password:
nova}, tenantName: admin}}' -H 'Content-type: application/json'
http://10.0.3.15:5000/v2.0/tokens;
2. Check the keystone database, see if user admin and tenant admin are
created OK
-Mandar
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On
Behalf Of Salman Malik
Sent: Thursday, May 24, 2012 9:48 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] devstack installation failing
Hi All,
While installing devstack, installation is failing with the error :
++ python -c 'import sys; import json; tok = json.loads(sys.stdin.read());
print tok['\''access'\'']['\''token'\'']['\''id'\''];'
++ curl -s -d '{auth:{passwordCredentials: {username: admin,
password: nova}, tenantName: admin}}' -H 'Content-type:
application/json' http://10.0.3.15:5000/v2.0/tokens
Traceback (most recent call last):
File string, line 1, in module
KeyError: 'access'
With some searching I know this has something to do with the keystone but I
have no clue how to resolve this one.
Thanks for your help.
Salman
__
Disclaimer:This email and any attachments are sent in strictest confidence for
the sole use of the addressee and may contain legally privileged, confidential,
and proprietary data. If you are not the intended recipient, please advise the
sender by replying promptly to this email and then delete and destroy this
email and any attachments without any further use, copying or forwarding___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] BadRequest: Can not find requested image (HTTP 400)
Milind, Nova boot command takes Image and Flavor IDs, not names Can you try nova boot -image 057f5695-7af5-4d42-ab17-2f0f36f99ee2 instead ? Similarly, you may need to use -flavor 2 instead of --flavor m1.small If you are interested in looking at code, see def do_boot in novaclient/v1_1/shell.py under python-novaclient repo. nova help boot usage: nova boot [--flavor flavor] [--image image] [--meta key=value] [--file dst-path=src-path] [--key_name key_name] [--user_data user-data] [--availability_zone availability-zone] [--security_groups security_groups] [--block_device_mapping dev_name=mapping] [--hint key=value] [--nic net-id=net-uuid,v4-fixed-ip=ip-addr] [--config-drive value] [--poll] name Boot a new server. Positional arguments: nameName for the new server Optional arguments: --flavor flavor Flavor ID (see 'nova flavor-list'). --image image Image ID (see 'nova image-list'). Hope this helps. -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Milind Sent: Friday, May 18, 2012 5:16 PM To: openstack@lists.launchpad.net Subject: [Openstack] BadRequest: Can not find requested image (HTTP 400) Hi, I am getting error while executing following command. root@ucmaster:/home/milindx/mil# nova boot --image tty-linux --flavor m1.small --key_name test my-first-server ERROR: Can not find requested image (HTTP 400) Following information will help root@ucmaster:/home/milindx/mil# cat /etc/nova/nova.conf | grep glance --image_service=nova.image.glance.GlanceImageService --glance_api_servers=10.253.59.152:9292http://10.253.59.152:9292 root@ucmaster:/home/milindx/mil# nova image-list +--+--+++ | ID | Name | Status | Server | +--+--+++ | 057f5695-7af5-4d42-ab17-2f0f36f99ee2 | tty-linux| ACTIVE || | 1cfd638b-1187-4f35-a0dd-76352742b762 | tty-kernel | ACTIVE || | 40c6e4ec-9b49-4f5c-989d-57cd2691fa12 | tty-linuxkernel | ACTIVE || | a726d350-c187-401b-823c-7bb1527aaa1d | tty-linuxramdisk | ACTIVE || | b1c79ba2-aef0-4dfc-8e0f-f1f223bea1f1 | tty | ACTIVE || | b3240f79-5b6f-450c-beff-5c8ecdabcf00 | tty-ramdisk | ACTIVE || +--+--+++ root@ucmaster:/home/milindx/mil# root@ucmaster:/home/milindx/mil# nova-manage service list 2012-05-18 17:15:30 DEBUG nova.utils [req-0997c625-ef9c-45ab-96a9-77a211d87459 None None] backend module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc' from (pid=15253) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658 Binary Host Zone Status State Updated_At nova-scheduler ucmaster nova enabled :-) 2012-05-18 11:45:25 nova-volume ucmaster nova enabled :-) 2012-05-18 11:45:25 nova-compute ucmaster nova enabled :-) 2012-05-18 11:45:21 nova-certucmaster nova enabled :-) 2012-05-18 11:45:25 nova-consoleauth ucmaster nova enabled :-) 2012-05-18 11:45:25 nova-network ucmaster nova enabled :-) 2012-05-18 11:45:25 I have deleted and added images using glance still problem persists, any one know what could be problem. Regards, Milind __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] How to access an instance from Dashboard using VNC (password)?
Ø But, from inside dashboard, I couldn't find where to get a similar information. From Dashboard, Click Edit Instance button on far right, and click on View Log Scroll at the end, you'll see the password. -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] BadRequest: Can not find requested image (HTTP 400)
Ø Is there any way to find out if image is exists with the help of glance command? glance image-list See my other email for your original problem -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Pending review
Yes, it should. I'll tag it for essex back-port once this review is approved and code is merged to master. -Mandar -Original Message- From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Christoph Thiel Sent: Wednesday, May 09, 2012 4:04 PM To: openstack@lists.launchpad.net Subject: Re: [Openstack] Pending review On Wed, May 09, 2012 at 05:38:44AM +, Vaze, Mandar wrote: https://review.openstack.org/#/c/6829/ Kevin Mitchell has reviewed as Looks good to me Additional reviews and approval required This looks like it should also go to stable/essex, once it got merged to master? Best Christoph -- Christoph Thiel, Project Manager, SUSE Cloud Infrastructure SUSE LINUX Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Pending review
https://review.openstack.org/#/c/6829/ Kevin Mitchell has reviewed as Looks good to me Additional reviews and approval required Thanks, -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Instance unreachable
Forwarding to ML so that others can suggest further troubleshooting points. From: ghassen ben hamida [mailto:ghassen.ben.ham...@gmail.com] Sent: Monday, May 07, 2012 5:36 PM To: Vaze, Mandar Subject: Re: [Openstack] Instance unreachable Hi, It is a single machine setup. There is nothing what is abnormal in the nova-network.log file. I configured my IPs staticly, and the IPs of VMs are assigned by FlatDhcpManager. 2012/5/7 Vaze, Mandar mandar.v...@nttdata.commailto:mandar.v...@nttdata.com 1. Have you enabled logging ? Do you see any errors in nova-network logs ? 2. Which network manager are you using ? 3. Some details about your setup will also help (Is it Single machine setup ?) -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.netmailto:nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vazemailto:openstack-bounces%2Bmandar.vaze=nttdata@lists.launchpad.netmailto:nttdata@lists.launchpad.net] On Behalf Of ghassen ben hamida Sent: Monday, May 07, 2012 5:49 AM To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: [Openstack] Instance unreachable Hi, I install openstack essex on ubuntu 12.04. everything seems running correctly, I can launch instances with nova boot command and also from the dashboard, an IP inside the range is assigned. The problem is that i can't ping or ssh the instances. I have configured the groupsecure rules to allow ping and ssh but the problem persist. any idea about that please ? thx __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Instance unreachable
Eric, Ghassen had posted the original query. Adding him to this email. Ghassen, As others have suggested can you login to VM say using VNC (From dashboard) You may be able to further troubleshoot from there ... -Mandar From: staywithmyhe...@gmail.com [mailto:staywithmyhe...@gmail.com] On Behalf Of Eric Luo Sent: Tuesday, May 08, 2012 7:04 AM To: Vaze, Mandar Subject: Re: [Openstack] Instance unreachable Hi , Mandar . I did have such problems before ,and I got things work at last . So ,I think my experience may have a little help. If you can ping (or ssh) to the VM on your HOST ,but can not ping with other computer in the network, then this is the floating ip problem. You should assign your VM a floating ip,so the outside world can talk to the VM (and also for the VM to talk to outside) but if you can not even ping the VM on your HOST ,then you should check if the VM is really running. I mean ,the Dashbaord may tell you that the VM is successfully running ,but this is only telling you that the Virtual Hardware of the VM is running ,it can not guarantee that the Operation System of the VM is loaded correctly and been booted! So ,you may need to check your image and other things. ps: Can you Plesase paste your nova config about the network? Hope my answer may have a little help . regards! Eric Luo 2012-05-08 On Mon, May 7, 2012 at 8:23 PM, Vaze, Mandar mandar.v...@nttdata.commailto:mandar.v...@nttdata.com wrote: Forwarding to ML so that others can suggest further troubleshooting points. From: ghassen ben hamida [mailto:ghassen.ben.ham...@gmail.commailto:ghassen.ben.ham...@gmail.com] Sent: Monday, May 07, 2012 5:36 PM To: Vaze, Mandar Subject: Re: [Openstack] Instance unreachable Hi, It is a single machine setup. There is nothing what is abnormal in the nova-network.log file. I configured my IPs staticly, and the IPs of VMs are assigned by FlatDhcpManager. 2012/5/7 Vaze, Mandar mandar.v...@nttdata.commailto:mandar.v...@nttdata.com 1. Have you enabled logging ? Do you see any errors in nova-network logs ? 2. Which network manager are you using ? 3. Some details about your setup will also help (Is it Single machine setup ?) -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.netmailto:nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vazemailto:openstack-bounces%2Bmandar.vaze=nttdata@lists.launchpad.netmailto:nttdata@lists.launchpad.net] On Behalf Of ghassen ben hamida Sent: Monday, May 07, 2012 5:49 AM To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: [Openstack] Instance unreachable Hi, I install openstack essex on ubuntu 12.04. everything seems running correctly, I can launch instances with nova boot command and also from the dashboard, an IP inside the range is assigned. The problem is that i can't ping or ssh the instances. I have configured the groupsecure rules to allow ping and ssh but the problem persist. any idea about that please ? thx __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Stay with me,stay with my heart,honey. __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Instance unreachable
1. Have you enabled logging ? Do you see any errors in nova-network logs ? 2. Which network manager are you using ? 3. Some details about your setup will also help (Is it Single machine setup ?) -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of ghassen ben hamida Sent: Monday, May 07, 2012 5:49 AM To: openstack@lists.launchpad.net Subject: [Openstack] Instance unreachable Hi, I install openstack essex on ubuntu 12.04. everything seems running correctly, I can launch instances with nova boot command and also from the dashboard, an IP inside the range is assigned. The problem is that i can't ping or ssh the instances. I have configured the groupsecure rules to allow ping and ssh but the problem persist. any idea about that please ? thx __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Instance IP assignment problem
Emilien, Please see https://answers.launchpad.net/quantum/+question/194111 Nova-compute and nova-network on two different machines seems to be the key here. Solution is proposed in the above thread. Hope that helps. -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Emilien Macchi Sent: Thursday, May 03, 2012 1:26 PM To: Salman Malik Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Instance IP assignment problem Hi, As I told you, I have also a problem for instance IP assignement. My architecture : I use Quantum with OVS plugin on 2 servers Essex-1 Essex-2. Essex-1 runs all services and Essex-2 runs OVS, Quantum-agent nova-compute only. You can see more details herehttps://github.com/EmilienM/doc-openstack/blob/master/Documentation/How%20to%20setup%20OpenStack%20Essex.pdf. My configurations files are herehttps://github.com/EmilienM/doc-openstack/tree/master/Configuration%20Files and in my documentation. Problem Description : When an instance is created in ESSEX-1, all is working (network). But when the VM is started on ESSEX-2, it does not get an IP address. (log filehttp://paste.openstack.org/show/14775/) I'm sure the problem comes from OVS connection with ESSEX-1. Do I need to configure something like a trunk or a tunnel between Essex-1 Essex-2 ? I miss something in my configuration, if you have any idea... Regards Emilien Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a écrit : It may help if you can share the log of your launched instance as well. There is a possibility that we both are having the same issue. Netstack developers can give a definitive answer to this, but it would be interesting to learn what goes wrong with a launched instance. Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.commailto:emilien.openst...@gmail.com To: salma...@live.commailto:salma...@live.com CC: jorge.delac...@stackops.commailto:jorge.delac...@stackops.com; openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:26:26 +0200 Le mardi 01 mai 2012 à 14:22 -0500, Salman Malik a écrit : Regarding L3 gateway, I believe its not necessary to have one (as the VM hasn't obtained an IP right now, so it can't talk to anything outside its net), but I am not sure. Regarding your problem, do you see any DHCP responses from the DHCP server ? I am asking this because I was having a similar problem earlier where I was getting assigned an IP address no in my desired fixed_network and I believe that was cause by another interfering DHCP server that was replying to discover messages before the nova-network could. Here my nova.conf and I don't have any interfering DHCP server : https://github.com/EmilienM/doc-openstack/blob/master/Configuration%20Files/Essex-1/nova.conf Thanks Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.commailto:emilien.openst...@gmail.com To: salma...@live.commailto:salma...@live.com CC: jorge.delac...@stackops.commailto:jorge.delac...@stackops.com; openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:06:01 +0200 Hi Salman, I'm thinking about a networking issue. Where is your L3 gateway in this architecture ? Maybe do you need an ip helper tool to redirect DHCP broadcast ? What do you think about my problem (follow up to my last e-mail) ? Thanks Emilien Le mardi 01 mai 2012 à 14:00 -0500, Salman Malik a écrit : Hi, Here is the error log: http://pastebin.com/KrNZDrvD and nova.conf: http://pastebin.com/Fvd6dSZs Emilien, I am trying to get an understanding of how different Quantum plugins work with OpenStack. Ryu plugin is particularly interesting as it uses an OpenFlow controller to configure Vswitches. The problem I am faced with is (I think ) that I already have a private network and Quantum should assign IP addresses to instances using DHCP. But instances send out discover message on laucnh but never find a DHCP server (although there are 2 dnsmasqs running). Any ideas? Thanks, Salman Date: Tue, 1 May 2012 20:43:44 +0200 Subject: Re: [Openstack] Instance IP assignment problem From: jorge.delac...@stackops.commailto:jorge.delac...@stackops.com To: emilien.openst...@gmail.commailto:emilien.openst...@gmail.com CC: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net; salma...@live.commailto:salma...@live.com Hi Emilien and Salman, Please, could you upload all the files, errors and conf in pastebin or something like that? I have troubles to open in phone :) Thank you El 01/05/2012 20:39, Emilien Macchi emilien.openst...@gmail.commailto:emilien.openst...@gmail.com escribió: Hi, I have a similar problem when I create a network per project_id
Re: [Openstack] Instance IP assignment problem
Please also see this : https://review.openstack.org/#/c/6829/ When nova-network is on remote host, dhcp requests need to go to remote server. I’ve proposed a fix above. -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Emilien Macchi Sent: Thursday, May 03, 2012 2:19 PM To: Bilel Msekni Cc: salma...@live.com; openstack@lists.launchpad.net Subject: Re: [Openstack] Instance IP assignment problem All seems alright but not working yet. http://paste.openstack.org/show/14791/ I have executed on both servers : ovs-vsctl add-port br-int eth1 Need I do something else ? How the DHCP is working in this case ? Le jeudi 03 mai 2012 à 09:29 +0100, Bilel Msekni a écrit : Then the problem isn't in the instance but in the nova-network service , please check if it is working well as well as give us the output log when you attempt to create a new instance. Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.commailto:emilien.openst...@gmail.com To: ski...@hotmail.frmailto:ski...@hotmail.fr CC: salma...@live.commailto:salma...@live.com; openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Date: Thu, 3 May 2012 10:21:37 +0200 Fixed IP Le jeudi 03 mai 2012 à 09:15 +0100, Bilel Msekni a écrit : Fixed IP or Floating IP ? From: emilien.openst...@gmail.commailto:emilien.openst...@gmail.com To: salma...@live.commailto:salma...@live.com Date: Thu, 3 May 2012 09:55:31 +0200 CC: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Instance IP assignment problem Hi, As I told you, I have also a problem for instance IP assignement. My architecture : I use Quantum with OVS plugin on 2 servers Essex-1 Essex-2. Essex-1 runs all services and Essex-2 runs OVS, Quantum-agent nova-compute only. You can see more details herehttps://github.com/EmilienM/doc-openstack/blob/master/Documentation/How%20to%20setup%20OpenStack%20Essex.pdf. My configurations files are herehttps://github.com/EmilienM/doc-openstack/tree/master/Configuration%20Files and in my documentation. Problem Description : When an instance is created in ESSEX-1, all is working (network). But when the VM is started on ESSEX-2, it does not get an IP address. (log filehttp://paste.openstack.org/show/14775/) I'm sure the problem comes from OVS connection with ESSEX-1. Do I need to configure something like a trunk or a tunnel between Essex-1 Essex-2 ? I miss something in my configuration, if you have any idea... Regards Emilien Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a écrit : It may help if you can share the log of your launched instance as well. There is a possibility that we both are having the same issue. Netstack developers can give a definitive answer to this, but it would be interesting to learn what goes wrong with a launched instance. Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.commailto:emilien.openst...@gmail.com To: salma...@live.commailto:salma...@live.com CC: jorge.delac...@stackops.commailto:jorge.delac...@stackops.com; openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:26:26 +0200 Le mardi 01 mai 2012 à 14:22 -0500, Salman Malik a écrit : Regarding L3 gateway, I believe its not necessary to have one (as the VM hasn't obtained an IP right now, so it can't talk to anything outside its net), but I am not sure. Regarding your problem, do you see any DHCP responses from the DHCP server ? I am asking this because I was having a similar problem earlier where I was getting assigned an IP address no in my desired fixed_network and I believe that was cause by another interfering DHCP server that was replying to discover messages before the nova-network could. Here my nova.conf and I don't have any interfering DHCP server : https://github.com/EmilienM/doc-openstack/blob/master/Configuration%20Files/Essex-1/nova.conf Thanks Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.commailto:emilien.openst...@gmail.com To: salma...@live.commailto:salma...@live.com CC: jorge.delac...@stackops.commailto:jorge.delac...@stackops.com; openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:06:01 +0200 Hi Salman, I'm thinking about a networking issue. Where is your L3 gateway in this architecture ? Maybe do you need an ip helper tool to redirect DHCP broadcast ? What do you think about my problem (follow up to my last e-mail) ? Thanks Emilien Le mardi 01 mai 2012 à 14:00 -0500, Salman Malik a écrit : Hi, Here is the error log: http://pastebin.com/KrNZDrvD and nova.conf: http://pastebin.com/Fvd6dSZs
[Openstack] Backporting to Essex-Stable
We've recently fixed some bugs that did not make it in time for Essex, so they are in master branch now. We would like these to be back-ported to Essex-stable branch. https://bugs.launchpad.net/nova/+bug/973194 https://bugs.launchpad.net/nova/+bug/977759 https://bugs.launchpad.net/nova/+bug/977875 Following are currently under review, but need to be back-ported when done: https://bugs.launchpad.net/nova/+bug/980685 https://bugs.launchpad.net/nova/+bug/973331 https://bugs.launchpad.net/nova/+bug/983024 What is the procedure to get these approved for back-porting ? Regards, -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] extending rootwrap securely
did the nova user /already/ have root access? nova-rootwrap uses sudo to execute certain commands that require root access. So yes, nova user already has root access via sudo. You can check /etc/sudoers file. stack.sh script from devstack adds the entry in sudoers list for the user running stack.sh Although stack.sh allows full root access to nova user, sudoers allows restricting the access to specific commands. (man sudoers) This can help alleviate your security concerns a little by allowing only certain commands to be executed by nova-user. (This might also restrict what the plugin can/can not do - but at least it would be secure) -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Backporting to Essex-Stable
Thanks !! -Mandar -Original Message- From: Alan Pevec [mailto:ape...@gmail.com] Sent: Monday, April 30, 2012 1:19 PM To: Vaze, Mandar Cc: d...@nicira.com; openstack@lists.launchpad.net Subject: Re: [Openstack] Backporting to Essex-Stable On Mon, Apr 30, 2012 at 8:14 AM, Vaze, Mandar mandar.v...@nttdata.com wrote: What is the procedure to get these approved for back-porting ? http://wiki.openstack.org/StableBranch#Workflow __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Question #194111]: Does quantum support multi-nic setup ?
Dan, I've updated the question (few more queries) Also, you didn't say exactly how you were running devstack. Can you send your config? I've described my two-machine setup in the original question itself. I didn't know how to add an attachment to the question, so here is my nova.conf for your reference (See attached) It is fairly standard one, generated by stack.sh -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding nova.conf Description: nova.conf ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Quantum and multi-nic
Dan, Can you help with this ? https://answers.launchpad.net/nova/+question/194111 Thanks, -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Using Foreign Keys
Vish, Thanks for the detailed explanation. I didn't mean to imply that fixing it is trivial. ( I did realize that since keystone could be using different DB server, it might not be trivial for nova-manage to validate the tenant_id) I was just supporting the argument in favor of data integrity :) -Mandar -Original Message- From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] Sent: Friday, April 20, 2012 11:47 AM To: Vaze, Mandar Cc: Philipp Wollermann; J. Daniel Schmidt; openstack Subject: Re: [Openstack] Using Foreign Keys On Apr 19, 2012, at 8:59 PM, Vaze, Mandar wrote: +1 for data integrity ... Here is an example that could use data integrity check : tenant information is managed in keystone DB ovs_quantum DB has tenant_id column for networks table. When I use stack.sh - it puts a string default in tenant_id column - when it creates network via nova-manage network create and it WORKS I see two problems here : 1. tenant_id are uuid - so string default should be rejected with check _is_like_uuid - but that is only partial solution. tenant_ids are strings. It is an implementation detail that keystone uses uuids. 2. tenant_id should be valid ID from keystone.tenants This would require nova-manage having logic to be able to connect to keystone which it doesn't have. One of the drawbacks of having decoupled services is everything isn't in one database where you can support foreign keys. We could in theory add logic to nova to allow it to verify things inside of keystone, but I'm not sure this makes sense from a security perspective. It would require nova to have administrative access to keystone to find out what tenants exist. Alternatively we could force administrative commands like network create to be done through the api using the context of the intended network. This has a drawback as well of making things administratively more difficult. An admin would have to get an administrative token for the intended tenant somehow before making the call. Vish __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Using Foreign Keys
+1 for data integrity ... Here is an example that could use data integrity check : tenant information is managed in keystone DB ovs_quantum DB has tenant_id column for networks table. When I use stack.sh - it puts a string default in tenant_id column - when it creates network via nova-manage network create and it WORKS I see two problems here : 1. tenant_id are uuid - so string default should be rejected with check _is_like_uuid - but that is only partial solution. 2. tenant_id should be valid ID from keystone.tenants -Mandar -Original Message- From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Philipp Wollermann Sent: Friday, April 20, 2012 7:36 AM To: J. Daniel Schmidt Cc: openstack Subject: Re: [Openstack] Using Foreign Keys Hi, On Apr 12, 2012, at 21:35, J. Daniel Schmidt wrote: One reviewer commented: i don't approve of adding foreign keys, and we should probably remove the existing ones (in UserTenantMembership and in Endpoint) and on we shouldn't be using foreign keys at all, they are a crutch that are not available everywhere what the ... !? I'm not actively participating in OpenStack development yet, so my opinion may carry no weight - but this is ridiculous. IMHO OpenStack is not some who needs data integrity anyway-web2.0 project, it's meant to provide a stable, robust platform where people run mission-critical production stuff. Calling our test cluster in the office BrokenStack is fun for a while and the 0 days since last exception sign wasn't bad either, but the fun stops when you actually need to depend on this software running. We should implement as many checks for integrity and validity of data as possible and if a foreign key actually catches something, that means that your last line of defense just stopped the worst and you should have failed much earlier. And someone is actually thinking about *removing* that? I'm all for a switch to the add as much foreign keys as we can policy. Actually, why are they not created automatically? If one uses an ORM correctly, there should be no way to actually *not* create them. -- Philipp Wollermann Infrastructure Engineer CyberAgent, Inc. (Tokyo) https://github.com/philwo ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] four reviews pending
Hi, I understand that most of you must be busy and enjoying the Design Summit in progress this week. It would be great if someone can spare some time to have a look at these : * https://review.openstack.org/#/c/6262/ : Both Vish and Padraig have said Looks good to me but the review still needs to be approved * https://review.openstack.org/#/c/6451/ : I've addressed comments from first review cycle - Second patch set needs to be reviewed and approved * https://review.openstack.org/#/c/6452/ : I have addressed changes suggested by Brad Hall in first review cycle. Second patch set needs to be reviewed * https://review.openstack.org/#/c/6481/ : Johannes Erdfelt has already said Looks good to me - Additional reviews and approval required Thanks !!! -Mandar P.S: I've requested the same on IRC as well, so please ignore if duplicate. __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] kombu / nova bug
I have also seen this when I execute run_tests.sh Since I haven't yet made changes related to these parts of code, I generally skip this test using @unit.skip decorator I've already clicked This bug also affects me on LP -Mandar -Original Message- From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Russell Bryant Sent: Tuesday, April 17, 2012 11:50 PM To: Ask Solem Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] kombu / nova bug On 04/17/2012 09:55 AM, Ask Solem wrote: On 17 Apr 2012, at 14:41, Bernhard M. Wiedemann wrote: Hi, I noticed that one test in the openstack-nova unit tests hangs indefinitely, bisected it to find that it started with kombu commit 9979ea0ac9cc4fd1c6339140b264e781e923d2be https://bugs.launchpad.net/nova/+bug/974411 and found that this change makes the test pass: however, I don't know whether this is a problem on the kombu or nova side. Please advise Hey Bernhard, Are the tests using the memory transport perhaps? Yes, it's using the memory transport. -- Russell Bryant ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Multiple nova-networks with QuantumManager (Was : Role of nova-manage network commands when using QuantumManager)
Dan, On similar lines - Currently if nova-network processes are running on two nodes, only way to set specific network on specific nova-network node is to execute nova-manage network create on respective nova-network node. Is that correct ? How is the above setup related to multi-host ? I found a code comment that Quantum Manager doesn't support multi-host I'm copying Vish, as he seems to be expert on multi-host - Reading http://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html , it looks like above is Option 2/Multi-Nic, but not really sure) If yes, how is multi-nic supported by Quantum ? Additionally - in the above document Vish suggested that each nova-compute must run nova-network - Is that why with QuantumManager - nova-manage executes networking commands like iptables, dnsmasq locally ? Thanks !! -Mandar From: Dan Wendlandt [mailto:d...@nicira.com] Sent: Thursday, April 12, 2012 9:44 PM To: Vaze, Mandar Cc: openstack@lists.launchpad.net; netst...@lists.launchpad.net Subject: Re: [Netstack] Role of nova-manage network commands when using QuantumManager Hi Mandar, Thanks for bringing this up. For Essex, nova-manage commands to create/delete Quantum networks must be run on the nova-network node. For Folsom this will all change, as all networks will be created directly against the Quantum API, rather than using nova-manage. I'll add a note to the administrator guide, as this is not called there. Thanks! Dan On Thu, Apr 12, 2012 at 1:38 AM, Vaze, Mandar mandar.v...@nttdata.commailto:mandar.v...@nttdata.com wrote: It is my understanding that in multi-node setup : * nova-manage can be executed from any machine which may not be running nova-network process. (Or should nova-manage always be run on nova-network node ?) * nova-manage does DB operations and delegates the actual networking calls to nova-network process ? Is this understanding correct ? I traced nova-manage network create and nova-manage network delete using FlatDHCPManager (default for devstack/stack.sh) Both these calls seem to be doing only DB operations. BTW, nova-network process was shutdown during both network create and network delete - Still both operations were successful. But when using QuantumManager as network manager - nova-manage seems to be doing networking operations like iptables-save (during network create) and kill_dhcp (during network delete) (via linux-net L3 driver) Since nova-manage command may be executed on a host which isn't running nova-network - network commands like iptables and kill -9 pid of dnsmasq on host running nova-manage seems incorrect. For the first scenario (iptables-save during network create - there is already a defect in LP : https://bugs.launchpad.net/nova/+bug/977738 and review : https://review.openstack.org/6451 I would like your comments and opinions which would help me understand What nova-manage should and should NOT do Thanks, -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding -- Mailing list: https://launchpad.net/~netstack Post to : netst...@lists.launchpad.netmailto:netst...@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.comhttp://www.nicira.com twitter: danwendlandt ~~~ __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Role of nova-manage network commands when using QuantumManager
It is my understanding that in multi-node setup : * nova-manage can be executed from any machine which may not be running nova-network process. (Or should nova-manage always be run on nova-network node ?) * nova-manage does DB operations and delegates the actual networking calls to nova-network process ? Is this understanding correct ? I traced nova-manage network create and nova-manage network delete using FlatDHCPManager (default for devstack/stack.sh) Both these calls seem to be doing only DB operations. BTW, nova-network process was shutdown during both network create and network delete - Still both operations were successful. But when using QuantumManager as network manager - nova-manage seems to be doing networking operations like iptables-save (during network create) and kill_dhcp (during network delete) (via linux-net L3 driver) Since nova-manage command may be executed on a host which isn't running nova-network - network commands like iptables and kill -9 pid of dnsmasq on host running nova-manage seems incorrect. For the first scenario (iptables-save during network create - there is already a defect in LP : https://bugs.launchpad.net/nova/+bug/977738 and review : https://review.openstack.org/6451 I would like your comments and opinions which would help me understand What nova-manage should and should NOT do Thanks, -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] ERROR: string indices must be integers, not str
You may have his this bug : https://bugs.launchpad.net/nova/+bug/965826 Says : this occurs When auth_host (in api-paste.ini) has the wrong IP address Something to check ... -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Guilherme Birk Sent: Wednesday, April 11, 2012 10:38 PM To: Openstack Mail List Subject: [Openstack] ERROR: string indices must be integers, not str I've got OpenStack working with this tutorial http://www.hastexo.com/resources/docs/installing-openstack-essex-20121-ubuntu-1204-precise-pangolin. Now I'm trying to deploy a new installation with the official manual, http://docs.openstack.org/trunk/openstack-compute/install/content/index.html. I can access dashboard, upload images and other things, but when I try to execute a nova list, or after connect to dashboard, I got this error: ERROR: string indices must be integers, not str. Anyone had this problem too? Maybe some wrong configuration? __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Instance can't reach dhcp or metadata
I have never been able to get to ssh to an instance with Quantum+mélange https://lists.launchpad.net/openstack/msg09206.html -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Nicolas de BONFILS Sent: Wednesday, April 11, 2012 1:45 AM To: Dan Wendlandt Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Instance can't reach dhcp or metadata Hi, I can't get the ssh connection,VNC doesn't respond and 10.0.0.1 go to localhost (ssh to server itself) --- Nicolas On Tue, Apr 10, 2012 at 21:42, Dan Wendlandt d...@nicira.commailto:d...@nicira.com wrote: On Tue, Apr 10, 2012 at 11:54 AM, Nicolas de BONFILS ndebonf...@gmail.commailto:ndebonf...@gmail.com wrote: Things starting to work ! When I boot boot cirros image with ip 10.0.0.1, I can ssh (even if it doesn't accept my password), but when I lauch tty-uec image (or other) with ip starting at 10.0.0.2, ssh tell no route to host If it works on one image, but not another, this is probably an issue with the image itself. The no route to host error is likely because the gateway interface 10.0.0.1 is arping for 10.0.0.2 and not getting a response. Perhaps the image is not configured to use DCHP on the interface? Or is not correctly launching? I'd use VNC to login and check it out. Dan I sum up the actual conf * br-int as bridge in OVS, no other conf (nothing in interfaces file), ifconfig show a 10.0.0.1 ip * nova conf got public_interface=br-int / flat_network_bridge=br-int / flat_interface=eth0 * quantum manage the assignation successfully Thanks --- Nicolas ___ Mailing list: https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.comhttp://www.nicira.com twitter: danwendlandt ~~~ __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Instance can't reach dhcp or metadata
Dan, Bug you referred to specifically says default tenant - which is not the case for me. I'm not using default tenant - I'm using uuid of demo tenant created by stack.sh BTW, stack.sh creates incorrect entries in quantum/mélange DB, it has tenant ID = default - This should be uuid of some valid tenant, not string default FWIW, this setup (although seems incorrect) works with quantum+nova_ipam - not with quantum+mélange i.e. With quantum+nova_ipam I can just create a VM and ssh to it. -Mandar From: Dan Wendlandt [mailto:d...@nicira.com] Sent: Wednesday, April 11, 2012 11:07 PM To: Vaze, Mandar Cc: Nicolas de BONFILS; openstack@lists.launchpad.net Subject: Re: [Openstack] Instance can't reach dhcp or metadata On Wed, Apr 11, 2012 at 5:24 AM, Vaze, Mandar mandar.v...@nttdata.commailto:mandar.v...@nttdata.com wrote: I have never been able to get to ssh to an instance with Quantum+mélange https://lists.launchpad.net/openstack/msg09206.html Looking at that thread, I suspect you may be hitting the same issue I mentioned above: https://bugs.launchpad.net/quantum/+bug/949234 If you try that fix and either do or don't have luck with it, please add a comment to the issue. Dan -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.netmailto:nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vazemailto:openstack-bounces%2Bmandar.vaze=nttdata@lists.launchpad.netmailto:nttdata@lists.launchpad.net] On Behalf Of Nicolas de BONFILS Sent: Wednesday, April 11, 2012 1:45 AM To: Dan Wendlandt Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Instance can't reach dhcp or metadata Hi, I can't get the ssh connection,VNC doesn't respond and 10.0.0.1 go to localhost (ssh to server itself) --- Nicolas On Tue, Apr 10, 2012 at 21:42, Dan Wendlandt d...@nicira.commailto:d...@nicira.com wrote: On Tue, Apr 10, 2012 at 11:54 AM, Nicolas de BONFILS ndebonf...@gmail.commailto:ndebonf...@gmail.com wrote: Things starting to work ! When I boot boot cirros image with ip 10.0.0.1, I can ssh (even if it doesn't accept my password), but when I lauch tty-uec image (or other) with ip starting at 10.0.0.2, ssh tell no route to host If it works on one image, but not another, this is probably an issue with the image itself. The no route to host error is likely because the gateway interface 10.0.0.1 is arping for 10.0.0.2 and not getting a response. Perhaps the image is not configured to use DCHP on the interface? Or is not correctly launching? I'd use VNC to login and check it out. Dan I sum up the actual conf * br-int as bridge in OVS, no other conf (nothing in interfaces file), ifconfig show a 10.0.0.1 ip * nova conf got public_interface=br-int / flat_network_bridge=br-int / flat_interface=eth0 * quantum manage the assignation successfully Thanks --- Nicolas ___ Mailing list: https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.comhttp://www.nicira.com twitter: danwendlandt ~~~ __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.comhttp://www.nicira.com twitter: danwendlandt ~~~ __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Laptop Demo Environment
Would http://devstack.org/guides/single-machine.html work for you ? (Or does it need to be installed from packages) -Mandar -Original Message- From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Lance Haig Sent: Tuesday, April 10, 2012 5:08 PM To: openstack@lists.launchpad.net Subject: [Openstack] Laptop Demo Environment Hi All, I am starting to build a laptop demo environment to be able to showcase OS to customers without having to get access to the outside world from their meeting rooms. My intention is to use kvm on my laptop and then build the environment from scratch. My last interaction with OS was during my course at Rackspace in Feb. Has anyone done something similar to this and is willing to share a config? Is Ubuntu still the preferred distribution for running OS on? Thanks Lance -- This message was scanned by Better Hosted and is believed to be clean. http://www.betterhosted.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Melange Unittests
Commenting line 32-EOF from setup.cfg didn't help
I also pip installed openstack.nose_plugin - still didn't help
Even if I try to run single test module, I still see same error(s) e.g. python
run_tests.py unit.test_ipam_models
I run these from /opt/stack/mélange
Here are the actual/detailed errors I see :
==
ERROR: nose.suite.ContextSuite context=melange.tests.functional
--
Traceback (most recent call last):
File /usr/lib/pymodules/python2.7/nose/suite.py, line 208, in run
self.setUp()
File /usr/lib/pymodules/python2.7/nose/suite.py, line 291, in setUp
self.setupContext(ancestor)
File /usr/lib/pymodules/python2.7/nose/suite.py, line 314, in setupContext
try_run(context, names)
File /usr/lib/pymodules/python2.7/nose/util.py, line 478, in try_run
return func()
File /opt/stack/melange/melange/tests/functional/__init__.py, line 32, in
setup
db_api.db_reset(conf, db_based_ip_generator, db_based_mac_generator)
File /opt/stack/melange/melange/db/sqlalchemy/api.py, line 259, in db_reset
db_sync(options)
File /opt/stack/melange/melange/db/sqlalchemy/api.py, line 246, in db_sync
migration.db_sync(options, version, repo_path)
File /opt/stack/melange/melange/db/sqlalchemy/migration.py, line 124, in
db_sync
upgrade(options, version=version, repo_path=repo_path)
File /opt/stack/melange/melange/db/sqlalchemy/migration.py, line 66, in
upgrade
return versioning_api.upgrade(sql_connection, repo_path, version)
File /usr/lib/python2.7/dist-packages/migrate/versioning/api.py, line 186,
in upgrade
return _migrate(url, repository, version, upgrade=True, err=err, **opts)
File string, line 2, in _migrate
File /usr/lib/python2.7/dist-packages/migrate/versioning/util/__init__.py,
line 159, in with_engine
return f(*a, **kw)
File /usr/lib/python2.7/dist-packages/migrate/versioning/api.py, line 365,
in _migrate
schema.runchange(ver, change, changeset.step)
File /usr/lib/python2.7/dist-packages/migrate/versioning/schema.py, line
91, in runchange
change.run(self.engine, step)
File /usr/lib/python2.7/dist-packages/migrate/versioning/script/py.py, line
145, in run
script_func(engine)
File
/opt/stack/melange/melange/db/sqlalchemy/migrate_repo/versions/002_device_id_to_uuid.py,
line 29, in upgrade
_db_connect()
File
/opt/stack/melange/melange/db/sqlalchemy/migrate_repo/versions/002_device_id_to_uuid.py,
line 62, in _db_connect
conf, app = config.Config.load_paste_app('melange', options, args)
File /opt/stack/melange/melange/common/config.py, line 37, in load_paste_app
conf, app = openstack_config.load_paste_app(*args, **kwargs)
File /opt/stack/melange/melange/openstack/common/config.py, line 283, in
load_paste_app
args, config_dir)
File /opt/stack/melange/melange/openstack/common/config.py, line 252, in
load_paste_config
Cannot load application %s % app_name)
RuntimeError: Unable to locate any configuration file. Cannot load application
mélange
-Mandar
-Original Message-
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On
Behalf Of Jason Kölker
Sent: Friday, April 06, 2012 8:21 PM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] Melange Unittests
On Fri, 2012-04-06 at 13:11 +, Vaze, Mandar wrote:
I tried to run ./run_tests.sh (without virtualenv) I kept on getting error
related to unable to find config file
I ran the tests from /opt/stack/mélange Same errors when I run python
run_tests.py
/opt/stack/mélange/etc/mélange/mélange.conf is present and valid.
How do I pass the config file to run_tests ? (Shouldn't it pick it up
automatically)
The nova test runner is busted. We had converted it to use tox, but as
Brian/James has found out there is an issue with the openstack.nose_plugin and
something in melange causing tests to not be picked up by the collector.
For the time being edit setup.cfg and comment out lines 32-EOF. Since melange
is merging with quantum, my plan is to fix them as I merge them into the
quantum tests.
Happy Hacking!
7-11
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
__
Disclaimer:This email and any attachments are sent in strictest confidence for
the sole use of the addressee and may contain legally privileged, confidential,
and proprietary data. If you are not the intended recipient, please advise the
sender by replying promptly to this email and then delete and destroy this
email and any attachments without any further use, copying or forwarding
Re: [Openstack] Melange Unittests
Copying /opt/stack/mélange/etc/mélange/mélange.conf to /etc resolved the
problem i.e. test cases started executing.
But that seems like BAD idea since running test cases trashed my DB ( I have
single box devstack installation)
-Mandar
-Original Message-
From: Vaze, Mandar
Sent: Monday, April 09, 2012 11:49 AM
To: 'Jason Kölker'; openstack@lists.launchpad.net
Subject: RE: [Openstack] Melange Unittests
Commenting line 32-EOF from setup.cfg didn't help I also pip installed
openstack.nose_plugin - still didn't help
Even if I try to run single test module, I still see same error(s) e.g. python
run_tests.py unit.test_ipam_models
I run these from /opt/stack/mélange
Here are the actual/detailed errors I see :
==
ERROR: nose.suite.ContextSuite context=melange.tests.functional
--
Traceback (most recent call last):
File /usr/lib/pymodules/python2.7/nose/suite.py, line 208, in run
self.setUp()
File /usr/lib/pymodules/python2.7/nose/suite.py, line 291, in setUp
self.setupContext(ancestor)
File /usr/lib/pymodules/python2.7/nose/suite.py, line 314, in setupContext
try_run(context, names)
File /usr/lib/pymodules/python2.7/nose/util.py, line 478, in try_run
return func()
File /opt/stack/melange/melange/tests/functional/__init__.py, line 32, in
setup
db_api.db_reset(conf, db_based_ip_generator, db_based_mac_generator)
File /opt/stack/melange/melange/db/sqlalchemy/api.py, line 259, in db_reset
db_sync(options)
File /opt/stack/melange/melange/db/sqlalchemy/api.py, line 246, in db_sync
migration.db_sync(options, version, repo_path)
File /opt/stack/melange/melange/db/sqlalchemy/migration.py, line 124, in
db_sync
upgrade(options, version=version, repo_path=repo_path)
File /opt/stack/melange/melange/db/sqlalchemy/migration.py, line 66, in
upgrade
return versioning_api.upgrade(sql_connection, repo_path, version)
File /usr/lib/python2.7/dist-packages/migrate/versioning/api.py, line 186,
in upgrade
return _migrate(url, repository, version, upgrade=True, err=err, **opts)
File string, line 2, in _migrate
File /usr/lib/python2.7/dist-packages/migrate/versioning/util/__init__.py,
line 159, in with_engine
return f(*a, **kw)
File /usr/lib/python2.7/dist-packages/migrate/versioning/api.py, line 365,
in _migrate
schema.runchange(ver, change, changeset.step)
File /usr/lib/python2.7/dist-packages/migrate/versioning/schema.py, line
91, in runchange
change.run(self.engine, step)
File /usr/lib/python2.7/dist-packages/migrate/versioning/script/py.py, line
145, in run
script_func(engine)
File
/opt/stack/melange/melange/db/sqlalchemy/migrate_repo/versions/002_device_id_to_uuid.py,
line 29, in upgrade
_db_connect()
File
/opt/stack/melange/melange/db/sqlalchemy/migrate_repo/versions/002_device_id_to_uuid.py,
line 62, in _db_connect
conf, app = config.Config.load_paste_app('melange', options, args)
File /opt/stack/melange/melange/common/config.py, line 37, in load_paste_app
conf, app = openstack_config.load_paste_app(*args, **kwargs)
File /opt/stack/melange/melange/openstack/common/config.py, line 283, in
load_paste_app
args, config_dir)
File /opt/stack/melange/melange/openstack/common/config.py, line 252, in
load_paste_config
Cannot load application %s % app_name)
RuntimeError: Unable to locate any configuration file. Cannot load application
mélange
-Mandar
-Original Message-
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On
Behalf Of Jason Kölker
Sent: Friday, April 06, 2012 8:21 PM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] Melange Unittests
On Fri, 2012-04-06 at 13:11 +, Vaze, Mandar wrote:
I tried to run ./run_tests.sh (without virtualenv) I kept on getting error
related to unable to find config file
I ran the tests from /opt/stack/mélange Same errors when I run python
run_tests.py
/opt/stack/mélange/etc/mélange/mélange.conf is present and valid.
How do I pass the config file to run_tests ? (Shouldn't it pick it up
automatically)
The nova test runner is busted. We had converted it to use tox, but as
Brian/James has found out there is an issue with the openstack.nose_plugin and
something in melange causing tests to not be picked up by the collector.
For the time being edit setup.cfg and comment out lines 32-EOF. Since melange
is merging with quantum, my plan is to fix them as I merge them into the
quantum tests.
Happy Hacking!
7-11
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
[Openstack] Gerrit review pending since 7 days ..
https://review.openstack.org/#change,6076 has been open since Apr 2nd. I understand everyone must have been busy with Essex release up to 5th. Can someone please take a look and approve ? (It is a trivial change) Thanks, -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Melange Unittests
I tried to run ./run_tests.sh (without virtualenv) I kept on getting error related to unable to find config file I ran the tests from /opt/stack/mélange Same errors when I run python run_tests.py /opt/stack/mélange/etc/mélange/mélange.conf is present and valid. How do I pass the config file to run_tests ? (Shouldn't it pick it up automatically) -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Brian Lamar Sent: Friday, April 06, 2012 5:35 AM To: openstack@lists.launchpad.net Subject: [Openstack] Melange Unittests Can anyone enlighten me as to why the gate-melange-unittests-python26 job is only running a single test? The first time it ran it correctly found all 500+ tests but now it seems to be just running one. :( This is happening locally for me too and I'm not quite sure where the disconnect is. I don't see any obvious changes in the code between the good/bad test runs that might account for this discrepancy. Any pointing in the right direction would be appreciated! Good Run: https://jenkins.openstack.org/job/gate-melange-unittests-python26/1/console Bad Run: https://jenkins.openstack.org/job/gate-melange-unittests-python26/2/console Brian __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Instance fails to spawn when instance_path is nfs mounted
I had a problem like this when the umask was locked down. Setting the umask
to 022 in the init script for nova-compute solved my problem.
I'm running from devstack setup - so I don't have an init-script. All the
processes run in a screen session.
Here is what I did :
1. Stopped nova-compute using Ctrl-C
2. Checked existing umask using umask command it was set to 0002
3. Updated umask using umask 022 - checked that it was indeed updated - this
time umask command returned 0022
4. Started nova-compute as follows :
mandar@ubuntu-dev-mandar:/opt/stack/nova$ cd /opt/stack/nova sg
libvirtd /opt/stack/nova/bin/nova-compute
5. Spawned an instance from Dashboard
Still getting same error.
-Mandar
On Tue, Apr 3, 2012 at 1:56 PM, Diego Parrilla Santamaría
diego.parrilla.santama...@gmail.com wrote:
We use nfs backed instances a lot, and this problem normally has to do
with wrong permission management in your filer and/or client.
Check if not only root can write on the nfs share (specially libvirt user).
Diego
--
Diego Parrilla
CEO
www.stackops.com | diego.parri...@stackops.com | +34 649 94 43 29
| skype:diegoparrilla
On Tue, Apr 3, 2012 at 6:43 PM, Mandar Vaze / मंदार वझे
mandarv...@gmail.com wrote:
I saw an old question posted here :
https://answers.launchpad.net/nova/+question/164689
But I am not trying live migration.
I have nfs mounted instances_path - so when I try to spawn an
instance I run into the above errors. Especially following :
File /usr/lib/python2.7/dist-packages/libvirt.py, line 372, in
createWithFlags
40842 2012-04-03 05:42:27 TRACE nova.rpc.amqp if ret == -1: raise
libvirtError ('virDomainCreateWithFlags() failed', dom=self)
40843 2012-04-03 05:42:27 TRACE nova.rpc.amqp libvirtError: internal
error Process exited while reading console log output: chardev:
opening backend file failed
But as you can see below, several files are created in this folder,
so I am not sure if mine if permissions issue (Else none of the files
would get created) The problem is reported when libvirt tries to
write to console.log (File itself is created with correct permissions
- just that this is zero byte file)
mandar@ubuntu-dev-mandar:/nfs_shared_instances_path/instance-0005
$ ll total 10944 drwxrwxr-x 2 mandar libvirtd 4096 2012-04-03
05:42 ./ drwxrwxrwx 4 root root 4096 2012-04-03 05:42 ../
-rw-rw 1 mandar libvirtd 0 2012-04-03 05:42 console.log
-rw-r--r-- 1 mandar libvirtd 6291968 2012-04-03 05:42 disk
-rw-rw-r-- 1 mandar libvirtd 4731440 2012-04-03 05:42 kernel
-rw-rw-r-- 1 mandar libvirtd 1067 2012-04-03 05:42 libvirt.xml
-rw-rw-r-- 1 mandar libvirtd 2254249 2012-04-03 05:42 ramdisk
I'm suspecting :
https://bugs.launchpad.net/ubuntu/maverick/+source/libvirt/+bug/63269
6 But I the above doesn't show itself in non-NFS setup
Please suggest !!!
-Mandar
___
Mailing list: https://launchpad.net/~openstack Post to :
openstack@lists.launchpad.net Unsubscribe :
https://launchpad.net/~openstack More help :
https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack Post to :
openstack@lists.launchpad.net Unsubscribe :
https://launchpad.net/~openstack More help :
https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
__
Disclaimer:This email and any attachments are sent in strictest confidence for
the sole use of the addressee and may contain legally privileged, confidential,
and proprietary data. If you are not the intended recipient, please advise the
sender by replying promptly to this email and then delete and destroy this
email and any attachments without any further use, copying or forwarding
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Instance fails to spawn when instance_path is nfs mounted
Ø Check if not only root can write on the nfs share (specially libvirt user).
It doesn’t look like permissions issue to me. Just to be doubly sure, I
“touched” a file, in that folder, edited and deleted the file. All operations
worked w/o error.
As I have listed below, several files got created with correct user/group
settings. In fact, “instance-0005” folder itself was created with correct
permissions.
mandar@ubuntu-dev-mandar:/nfs_shared_instances_path/instance-0005$ ll
total 10944
drwxrwxr-x 2 mandar libvirtd4096 2012-04-03 05:42 ./
drwxrwxrwx 4 root root4096 2012-04-03 05:42 ../
-rw-rw 1 mandar libvirtd 0 2012-04-03 05:42 console.log
-rw-r--r-- 1 mandar libvirtd 6291968 2012-04-03 05:42 disk
-rw-rw-r-- 1 mandar libvirtd 4731440 2012-04-03 05:42 kernel
-rw-rw-r-- 1 mandar libvirtd1067 2012-04-03 05:42 libvirt.xml
-rw-rw-r-- 1 mandar libvirtd 2254249 2012-04-03 05:42 ramdisk
I also moved the mount point from “/” to my home folder – still didn’t help
-Mandar
On Tue, Apr 3, 2012 at 6:43 PM, Mandar Vaze / मंदार वझे
mandarv...@gmail.commailto:mandarv...@gmail.com wrote:
I saw an old question posted here :
https://answers.launchpad.net/nova/+question/164689
But I am not trying live migration.
I have nfs mounted instances_path - so when I try to spawn an instance I
run into the above errors. Especially following :
File /usr/lib/python2.7/dist-packages/libvirt.py, line 372, in createWithFlags
40842 2012-04-03 05:42:27 TRACE nova.rpc.amqp if ret == -1: raise
libvirtError ('virDomainCreateWithFlags() failed', dom=self)
40843 2012-04-03 05:42:27 TRACE nova.rpc.amqp libvirtError: internal error
Process exited while reading console log output: chardev: opening backend
file failed
But as you can see below, several files are created in this folder, so I
am not sure if mine if permissions issue (Else none of the files would
get created) The problem is reported when libvirt tries to write to
console.log (File itself is created with correct permissions - just that
this is zero byte file)
mandar@ubuntu-dev-mandar:/nfs_shared_instances_path/instance-0005$ ll
total 10944
drwxrwxr-x 2 mandar libvirtd4096 2012-04-03 05:42 ./
drwxrwxrwx 4 root root4096 2012-04-03 05:42 ../
-rw-rw 1 mandar libvirtd 0 2012-04-03 05:42 console.log
-rw-r--r-- 1 mandar libvirtd 6291968 2012-04-03 05:42 disk
-rw-rw-r-- 1 mandar libvirtd 4731440 2012-04-03 05:42 kernel
-rw-rw-r-- 1 mandar libvirtd1067 2012-04-03 05:42 libvirt.xml
-rw-rw-r-- 1 mandar libvirtd 2254249 2012-04-03 05:42 ramdisk
I'm suspecting :
https://bugs.launchpad.net/ubuntu/maverick/+source/libvirt/+bug/632696
But I the above doesn't show itself in non-NFS setup
Please suggest !!!
-Mandar
___
Mailing list: https://launchpad.net/~openstack
Post to :
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
__
Disclaimer:This email and any attachments are sent in strictest confidence for
the sole use of the addressee and may contain legally privileged, confidential,
and proprietary data. If you are not the intended recipient, please advise the
sender by replying promptly to this email and then delete and destroy this
email and any attachments without any further use, copying or forwarding
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Instance fails to spawn when instance_path is nfs mounted
All,
On the link given below vish asked if I could “chown” the files in that folder
– turns out I couldn’t.
I’ve answered his query on the link below – but repeating the updates here for
larger audience (Unfortunately, I have revived a question that is marked as
“solved” – so not many people may refer/respond to the link)
Vish :
1) is it possible to chown files on your nfs mount?
Not sure whom should I give the ownership to ? As the dir listing shows above,
the files are created with correct owner/group settings. These files were
created by nova-compute process.
I touched a file for testing - which was created with mandar:mandar - I
tried changing the ownership, but I keep getting invalid argument - not sure
if that is what you were referring to ..
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ touch x
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ ll
total 16
drwxrwxrwx 4 root root 4096 2012-04-04 03:46 ./
drwxr-xr-x 15 mandar mandar 4096 2012-04-04 03:39 ../
drwxrwxr-x 2 mandar libvirtd 4096 2012-04-04 02:18 _base/
drwxr-xr-x 2 mandar libvirtd 4096 2012-04-04 03:41 instance-000f/
-rw-rw-r-- 1 mandar mandar 0 2012-04-04 03:46 x
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ chown root x
chown: changing ownership of `x': Invalid argument
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ ll
total 16
drwxrwxrwx 4 root root 4096 2012-04-04 03:46 ./
drwxr-xr-x 15 mandar mandar 4096 2012-04-04 03:39 ../
drwxrwxr-x 2 mandar libvirtd 4096 2012-04-04 02:18 _base/
drwxr-xr-x 2 mandar libvirtd 4096 2012-04-04 03:41 instance-000f/
-rw-rw-r-- 1 mandar mandar 0 2012-04-04 03:46 x
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ sudo chown root x
chown: changing ownership of `x': Invalid argument
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ chgrp libvirtd x
chgrp: changing group of `x': Invalid argument
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ sudo chgrp libvirtd x
chgrp: changing group of `x': Invalid argument
I also debugged the _chown_console_log_for_instance in
nova/virt/libvirt/connection.py
and with breakpoint before if os.path.exists(console_log) - I touched
console.log at the appropriate path from another terminal.
Over there also I am getting the same error:
2012-04-04 03:56:55 TRACE nova.rpc.amqp Command: sudo
/usr/local/bin/nova-rootwrap chown 1000
/home/mandar/nfs_shared_instances_path/instance-0010/console.log
2012-04-04 03:56:55 TRACE nova.rpc.amqp Exit code: 1
2012-04-04 03:56:55 TRACE nova.rpc.amqp Stdout: ''
2012-04-04 03:56:55 TRACE nova.rpc.amqp Stderr: /bin/chown: changing ownership
of `/home/mandar/nfs_shared_instances_path/instance-0010/console.log':
Invalid argument\n
So what is the fix for this ?
-Mandar
From: openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net] On
Behalf Of Mandar Vaze / ? ???
Sent: Tuesday, April 03, 2012 10:14 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] Instance fails to spawn when instance_path is nfs mounted
I saw an old question posted here :
https://answers.launchpad.net/nova/+question/164689
But I am not trying live migration.
I have nfs mounted instances_path - so when I try to spawn an instance I
run into the above errors. Especially following :
File /usr/lib/python2.7/dist-packages/libvirt.py, line 372, in createWithFlags
40842 2012-04-03 05:42:27 TRACE nova.rpc.amqp if ret == -1: raise
libvirtError ('virDomainCreateWithFlags() failed', dom=self)
40843 2012-04-03 05:42:27 TRACE nova.rpc.amqp libvirtError: internal error
Process exited while reading console log output: chardev: opening backend
file failed
But as you can see below, several files are created in this folder, so I
am not sure if mine if permissions issue (Else none of the files would
get created) The problem is reported when libvirt tries to write to
console.log (File itself is created with correct permissions - just that
this is zero byte file)
mandar@ubuntu-dev-mandar:/nfs_shared_instances_path/instance-0005$ ll
total 10944
drwxrwxr-x 2 mandar libvirtd4096 2012-04-03 05:42 ./
drwxrwxrwx 4 root root4096 2012-04-03 05:42 ../
-rw-rw 1 mandar libvirtd 0 2012-04-03 05:42 console.log
-rw-r--r-- 1 mandar libvirtd 6291968 2012-04-03 05:42 disk
-rw-rw-r-- 1 mandar libvirtd 4731440 2012-04-03 05:42 kernel
-rw-rw-r-- 1 mandar libvirtd1067 2012-04-03 05:42 libvirt.xml
-rw-rw-r-- 1 mandar libvirtd 2254249 2012-04-03 05:42 ramdisk
I'm suspecting :
https://bugs.launchpad.net/ubuntu/maverick/+source/libvirt/+bug/632696
But I the above doesn't show itself in non-NFS setup
Please suggest !!!
-Mandar
__
Disclaimer:This email and any attachments are sent in strictest confidence for
the sole use of the addressee and may contain legally privileged, confidential,
and
Re: [Openstack] Instance fails to spawn when instance_path is nfs mounted
I was able to resolve the problem – Thanks to hint Vish provided and suggestion
from Rohit (CC’ed)
Turns out there is some problem with nfs v4 – So we mounted the share using nfs
version 3 (mount –o vers=3)
Now we could “chown” the files in nfs folder, and the instance creation also
worked !!!
Thanks Rohit !!!
Thanks Vish !!
-Mandar
From: Vaze, Mandar
Sent: Wednesday, April 04, 2012 4:41 PM
To: openstack@lists.launchpad.net
Cc: 'vishvana...@gmail.com'
Subject: RE: [Openstack] Instance fails to spawn when instance_path is nfs
mounted
All,
On the link given below vish asked if I could “chown” the files in that folder
– turns out I couldn’t.
I’ve answered his query on the link below – but repeating the updates here for
larger audience (Unfortunately, I have revived a question that is marked as
“solved” – so not many people may refer/respond to the link)
Vish :
1) is it possible to chown files on your nfs mount?
Not sure whom should I give the ownership to ? As the dir listing shows above,
the files are created with correct owner/group settings. These files were
created by nova-compute process.
I touched a file for testing - which was created with mandar:mandar - I
tried changing the ownership, but I keep getting invalid argument - not sure
if that is what you were referring to ..
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ touch x
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ ll
total 16
drwxrwxrwx 4 root root 4096 2012-04-04 03:46 ./
drwxr-xr-x 15 mandar mandar 4096 2012-04-04 03:39 ../
drwxrwxr-x 2 mandar libvirtd 4096 2012-04-04 02:18 _base/
drwxr-xr-x 2 mandar libvirtd 4096 2012-04-04 03:41 instance-000f/
-rw-rw-r-- 1 mandar mandar 0 2012-04-04 03:46 x
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ chown root x
chown: changing ownership of `x': Invalid argument
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ ll
total 16
drwxrwxrwx 4 root root 4096 2012-04-04 03:46 ./
drwxr-xr-x 15 mandar mandar 4096 2012-04-04 03:39 ../
drwxrwxr-x 2 mandar libvirtd 4096 2012-04-04 02:18 _base/
drwxr-xr-x 2 mandar libvirtd 4096 2012-04-04 03:41 instance-000f/
-rw-rw-r-- 1 mandar mandar 0 2012-04-04 03:46 x
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ sudo chown root x
chown: changing ownership of `x': Invalid argument
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ chgrp libvirtd x
chgrp: changing group of `x': Invalid argument
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ sudo chgrp libvirtd x
chgrp: changing group of `x': Invalid argument
I also debugged the _chown_console_log_for_instance in
nova/virt/libvirt/connection.py
and with breakpoint before if os.path.exists(console_log) - I touched
console.log at the appropriate path from another terminal.
Over there also I am getting the same error:
2012-04-04 03:56:55 TRACE nova.rpc.amqp Command: sudo
/usr/local/bin/nova-rootwrap chown 1000
/home/mandar/nfs_shared_instances_path/instance-0010/console.log
2012-04-04 03:56:55 TRACE nova.rpc.amqp Exit code: 1
2012-04-04 03:56:55 TRACE nova.rpc.amqp Stdout: ''
2012-04-04 03:56:55 TRACE nova.rpc.amqp Stderr: /bin/chown: changing ownership
of `/home/mandar/nfs_shared_instances_path/instance-0010/console.log':
Invalid argument\n
So what is the fix for this ?
-Mandar
From:
openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.netmailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net]mailto:[mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net]
On Behalf Of Mandar Vaze / ? ???
Sent: Tuesday, April 03, 2012 10:14 PM
To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: [Openstack] Instance fails to spawn when instance_path is nfs mounted
I saw an old question posted here :
https://answers.launchpad.net/nova/+question/164689
But I am not trying live migration.
I have nfs mounted instances_path - so when I try to spawn an instance I
run into the above errors. Especially following :
File /usr/lib/python2.7/dist-packages/libvirt.py, line 372, in createWithFlags
40842 2012-04-03 05:42:27 TRACE nova.rpc.amqp if ret == -1: raise
libvirtError ('virDomainCreateWithFlags() failed', dom=self)
40843 2012-04-03 05:42:27 TRACE nova.rpc.amqp libvirtError: internal error
Process exited while reading console log output: chardev: opening backend
file failed
But as you can see below, several files are created in this folder, so I
am not sure if mine if permissions issue (Else none of the files would
get created) The problem is reported when libvirt tries to write to
console.log (File itself is created with correct permissions - just that
this is zero byte file)
mandar@ubuntu-dev-mandar:/nfs_shared_instances_path/instance-0005$ ll
total 10944
drwxrwxr-x 2 mandar libvirtd4096 2012-04-03 05:42 ./
drwxrwxrwx 4 root root4096 2012-04-03 05
