Ask Your Question

mx-chilly's profile - activity

2017-07-05 18:49:41 -0600 received badge  Famous Question (source)
2017-03-08 18:35:14 -0600 received badge  Good Question (source)
2017-02-17 04:08:31 -0600 received badge  Nice Question (source)
2015-10-24 02:48:51 -0600 received badge  Notable Question (source)
2015-07-15 08:33:59 -0600 received badge  Student (source)
2015-07-08 15:05:59 -0600 received badge  Popular Question (source)
2014-12-07 23:55:21 -0600 received badge  Famous Question (source)
2014-11-11 08:08:40 -0600 received badge  Famous Question (source)
2014-11-11 08:08:40 -0600 received badge  Popular Question (source)
2014-11-11 08:08:40 -0600 received badge  Notable Question (source)
2014-10-22 05:07:53 -0600 received badge  Notable Question (source)
2014-10-22 05:07:53 -0600 received badge  Popular Question (source)
2012-07-25 11:36:54 -0600 asked a question Snapshots stay in queued status

I've got an Openstack setup with one controller node (glance, keystone, horizon, nova-* (except nova-compute)) and three compute nodes. I wanted to create a snapshot of a vm running on one of the compute nodes, by using the option in the horizon dashboard.

What happens is that the snapshot gets listed as a snapshot, but with the status queued. And from there on nothing happens anymore.

In the nova-compute.log on the compute host I can see these entries: 2012-07-25 12:45:56 TRACE nova.rpc.amqp Traceback (most recent call last): 2012-07-25 12:45:56 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/rpc/amqp.py", line 253, in _process_data 2012-07-25 12:45:56 TRACE nova.rpc.amqp rval = node_func(context=ctxt, *node_args) 2012-07-25 12:45:56 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/exception.py", line 114, in wrapped 2012-07-25 12:45:56 TRACE nova.rpc.amqp return f(args, *kw) 2012-07-25 12:45:56 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 183, in decorated_function 2012-07-25 12:45:56 TRACE nova.rpc.amqp sys.exc_info()) 2012-07-25 12:45:56 TRACE nova.rpc.amqp File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__ 2012-07-25 12:45:56 TRACE nova.rpc.amqp self.gen.next() 2012-07-25 12:45:56 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 177, in decorated_function 2012-07-25 12:45:56 TRACE nova.rpc.amqp return function(self, context, instance_uuid, *args, *kwargs) 2012-07-25 12:45:56 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 952, in snapshot_instance 2012-07-25 12:45:56 TRACE nova.rpc.amqp self.driver.snapshot(context, instance_ref, image_id) 2012-07-25 12:45:56 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/exception.py", line 114, in wrapped 2012-07-25 12:45:56 TRACE nova.rpc.amqp return f(args, *kw) 2012-07-25 12:45:56 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py", line 714, in snapshot 2012-07-25 12:45:56 TRACE nova.rpc.amqp image_file) 2012-07-25 12:45:56 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/image/glance.py", line 306, in update 2012-07-25 12:45:56 TRACE nova.rpc.amqp _reraise_translated_image_exception(image_id) 2012-07-25 12:45:56 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/image/glance.py", line 304, in update 2012-07-25 12:45:56 TRACE nova.rpc.amqp image_meta = client.update_image(image_id, image_meta, data) 2012-07-25 12:45:56 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/glance/client.py", line 195, in update_image 2012-07-25 12:45:56 TRACE nova.rpc.amqp res = self.do_request("PUT", "/images/%s" % image_id, body, headers) 2012-07-25 12:45:56 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 58, in wrapped 2012-07-25 12:45:56 TRACE nova.rpc.amqp return func(self ... (more)

2012-07-24 16:31:31 -0600 answered a question libvirrt error: Connection reset by peer

I'm also no expert in debugging nova and had quite some troubles with it. I knew that libvirt was used, so I located the instances on the compute node and tried to start them manually using virsh ( https://help.ubuntu.com/community/KVM/Virsh (https://help.ubuntu.com/community/KVM...) ). Didn't work, but so I could be sure it's a problem with libvirt and the xml file that defines the instance.

Well it turned out that there was an entry in the xml file for the vnc server which was not correct. After it was removed, I could start the machines.

2012-05-31 19:25:35 -0600 answered a question the nova endpoint URL is throwing error

Sorry, I didn't realize you were using an older version. I have no experience with that, so I can't help you there.

At least from the debug message it looks to me like keystone is working correctly, you get you're authentication token. The GET message that results in you 401 is to the nova api. So it looks like the the nova api does not accept your token.

So the first step would be to find out if the nova api is correctly configured, so that it uses keystone for authorization or not. One way to do this could be to manipulate the database. I suspect that the nova authentication token will be checked against the table "nova.auth_tokens" where as the keystone tokens are checked against "keystone.token". So for example you create your keystone token and use this to create a nova.auth_token. If the requests then work you know at least what's going wrong.

2012-05-30 08:39:40 -0600 answered a question nova-compute on cloud controller??

I only have eth0, but it's trunked so i've got 3 eth0.X and a bridge for each of it.

--root_helper=sudo nova-rootwrap --auth_strategy=keystone --allow_admin_api=true ############

nova.flags

--api_paste_config=/etc/nova/api-paste.ini --connection_type=libvirt --ec2_host=10.0.2.21 --glance_api_servers=10.0.2.21:9292 --image_service=nova.image.glance.GlanceImageService --lock_path=/var/lock/nova #--log-config=<none> --logdir=/var/log/nova --my_ip=10.0.2.21 --rabbit_host=10.0.2.21 --rabbit_password=guest --resume_guests_state_on_host_boot=true --s3_host=10.0.2.21 --start_guests_on_host_boot=true --state_path=/var/lib/nova --zombie_instance_updated_at_window=172800 ############

nova.log

publish_errors=True

############

nova.network.linux_net

--dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --routing_source_ip=10.0.2.21 --network_manager=nova.network.manager.FlatDHCPManager --network_host=10.0.2.21 --flat_network_dhcp_start=192.168.2.2 --flat_network_bridge=br232 --flat_interface=eth0.232 --flat_injected=false --force_dhcp_release --public_interface=eth0.235 --floating_range=10.0.5.128/25 --fixed_range=192.168.2.0/24 --network_size=255 ############

nova.service

osapi_compute_listen="0.0.0.0"

osapi_compute_listen_port=8774

osapi_volume_listen="0.0.0.0"

osapi_volume_listen_port=8776

############

nova.test

--use_deprecated_auth=false ############

nova.api.ec2

--keystone_ec2_url=http://10.0.2.21:5000/v2.0/ec2tokens ############

nova.vnc

--vnc_enabled=true --vncserver_proxyclient_address=10.0.2.22 --novncproxy_base_url=http://10.0.2.21:6080/vnc_auto.html --vncserver_listen=10.0.2.22 ###########

nova.virt.libvirt.connection

--libvirt_type=kvm --libvirt_use_virtio_for_bridges=true ###########

nova.scheduler.manager

--scheduler_driver=nova.scheduler.simple.SimpleScheduler --sql_connection=mysql://nova:nova@10.0.2.21/nova

2012-05-30 08:26:46 -0600 answered a question libvirrt error: Connection reset by peer

Thanks Igor Laskovy, that solved my question.

2012-05-26 18:12:44 -0600 answered a question libvirrt error: Connection reset by peer

I tried that workaround and I updated the ubuntu on the host for the 100st time (sure feels like it) and now the error is gone. For me this doesn't make sense. Why should vnc settings have an influence on libvirt? And these were settings I copied from a working setup...

I also tried to reproduce the error by adding those lines again and restarting nova-compute. Well, it now works even with vns settings. But I would still love to hear an explanation of what the error actually was...

2012-05-26 17:32:56 -0600 answered a question nova-compute on cloud controller??

I'm not using the multi-host option for nova-network. The controller node is the only one having nova-network running.

Though I had really a hard time getting the instances to be able to connect to the outside world, incoming with floating ips and outgoing from the instances themselves, I never ran into trouble with the meta-data. But I worked most of the time with the custom built images and added the use-images later on.

2012-05-26 10:23:32 -0600 answered a question the nova endpoint URL is throwing error

Ok, there are a couple of issues here.

First you've got some errors in your service catalog entries, namely the internal urls of your services. They all direct to the nova api, please check that you create your endpoints according to this link: http://docs.openstack.org/essex/openstack-compute/starter/content/Creating_Endpoints-d1e469.html (http://docs.openstack.org/essex/opens...)

The next thing is your curl itself to get the token. You use: curl -d '{"auth": {"tenantName": "openstackDemo", "passwordCredentials":{"username": "adminUser", "password": "secretword"}}}' -H "Content-type: application/json" http://XX.XX.XX.XX:35357/v2.0/tokens | python -mjson.tool

It should work, but you're actually using the admin url here. Usually one would use either the internal or the public url for authentication: "http://XX.XX.XX.XX:5000/v2.0"

When you try to validate the glance and nova endpoints, why don't you use the "glance index" and "nova list" commands? Use them with the "--debug" option and they'll show you the http requests they make. Also remember that glance and nova will use their respective users from the service tenant to make those requests. So if you want to check that glance and nova are working correctly using curl than use the credentials of their users.

2012-05-25 06:19:31 -0600 answered a question the nova endpoint URL is throwing error

Instead of admin_token in the api-paste.ini try those lines:

admin_tenant_name = service admin_user = nova admin_password = nova

Make sure that you enter your service tentant and the credentials for your nova user.

If you haven't done so already, create at least the admin role according to this link: http://docs.openstack.org/essex/openstack-compute/starter/content/Creating_Keystone_Roles-d1e460.html (http://docs.openstack.org/essex/opens...)

And after that add the admin role to the nova user, as explained in this link: http://docs.openstack.org/essex/openstack-compute/starter/content/Adding_Roles_to_Users-d1e465.html (http://docs.openstack.org/essex/opens...)

2012-05-25 06:11:10 -0600 answered a question nova-compute on cloud controller??

Actually I've got both types running, uec-images and customized CentOs images.

2012-05-24 20:59:32 -0600 answered a question nova-compute on cloud controller??

Hi Juan,

first things first: I've got the same setup up and running, which is why I said that you don't need nova-compute on the cloud controller.

I suppose you checked "nova-manage service list" and you have smileys on your compute services?

There was an issue when images need to fetch meta data, so you might have a look here: https://answers.launchpad.net/nova/+question/159317 (https://answers.launchpad.net/nova/+q...)

2012-05-24 13:49:14 -0600 answered a question the nova endpoint URL is throwing error

Just to check: - you entered your service tenant, nova user and password at the end in the api-paste.ini? - you granted the nova user the admin role in keystone?

2012-05-24 07:11:08 -0600 answered a question nova-compute on cloud controller??

No, you don't need to install nova-compute on the controller node in such a setup.

2012-05-24 07:06:07 -0600 answered a question nova-network unable to run normally due to Command: sudo nova-rootwrap iptables-save -t filter

Looks like nova trys to use 'sudo'. Did you allow root-wrap: http://wiki.openstack.org/Packager/Rootwrap (http://wiki.openstack.org/Packager/Ro...)

2012-05-24 06:58:20 -0600 asked a question libvirrt error: Connection reset by peer

I'm using a two node setup with Ubuntu 12.04, one cloud controller and one compute node. I'm using kvm and whenever I try to start an instance the compute node throws a libvirrt error:

2012-05-24 08:47:30 TRACE nova.compute.manager [instance: b0d33c8a-9bf6-4e39-b26c-5f9b382f2766] Traceback (most recent call last): 2012-05-24 08:47:30 TRACE nova.compute.manager [instance: b0d33c8a-9bf6-4e39-b26c-5f9b382f2766] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 592, in _spawn 2012-05-24 08:47:30 TRACE nova.compute.manager [instance: b0d33c8a-9bf6-4e39-b26c-5f9b382f2766] self._legacy_nw_info(network_info), block_device_info) 2012-05-24 08:47:30 TRACE nova.compute.manager [instance: b0d33c8a-9bf6-4e39-b26c-5f9b382f2766] File "/usr/lib/python2.7/dist-packages/nova/exception.py", line 114, in wrapped 2012-05-24 08:47:30 TRACE nova.compute.manager [instance: b0d33c8a-9bf6-4e39-b26c-5f9b382f2766] return f(args, *kw) 2012-05-24 08:47:30 TRACE nova.compute.manager [instance: b0d33c8a-9bf6-4e39-b26c-5f9b382f2766] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py", line 922, in spawn 2012-05-24 08:47:30 TRACE nova.compute.manager [instance: b0d33c8a-9bf6-4e39-b26c-5f9b382f2766] self._create_new_domain(xml) 2012-05-24 08:47:30 TRACE nova.compute.manager [instance: b0d33c8a-9bf6-4e39-b26c-5f9b382f2766] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py", line 1575, in _create_new_domain 2012-05-24 08:47:30 TRACE nova.compute.manager [instance: b0d33c8a-9bf6-4e39-b26c-5f9b382f2766] domain.createWithFlags(launch_flags) 2012-05-24 08:47:30 TRACE nova.compute.manager [instance: b0d33c8a-9bf6-4e39-b26c-5f9b382f2766] File "/usr/lib/python2.7/dist-packages/libvirt.py", line 581, in createWithFlags 2012-05-24 08:47:30 TRACE nova.compute.manager [instance: b0d33c8a-9bf6-4e39-b26c-5f9b382f2766] if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self) 2012-05-24 08:47:30 TRACE nova.compute.manager [instance: b0d33c8a-9bf6-4e39-b26c-5f9b382f2766] libvirtError: Unable to read from monitor: Connection reset by peer

I checked the bios, I checked "lsmod | grep kvm" and "lsmod | grep nbd". KVM is enabled in the bios and the modules are loaded.

When I try using "virsh start domain-name", I see the same error: "error: Unable to read from monitor: Connection reset by peer" . Any hints on what's wrong here?

2012-05-17 12:54:42 -0600 answered a question routing problem with floating ip addresses

I got it to work, but I still don't understand what the cause of the error was exactly.

My private vm network now uses br232 (VLAN 232). I deleted br235 and changed public_interface to eth0.235, because I was unsure what I was supposed to use there. Then I assigned eth0.235 an ip address (no dhcp in that vlan) and restartet the servers. The cloud controller now uses the default gateway of eth0.235 instead of the br233 (management vlan). And with that changes it worked.

2012-05-16 22:16:02 -0600 answered a question How to clean nova DB

I remember having a similar problem not long ago. You don't need to delete the entry from the "instance" table, just set "deleted=1" in this entry:

update instance set deleted=1 where id=XXX;

With XXX being the id of the entry you want to change.

That is just my "quick&dirty" solution, I'm not sure whether that's all nova changes in the db when it deletes an instance. For example I noticed that if you're instance had a floating ip you'll also need to modify that entry, so that the floating ip is available once more.

2012-05-14 15:28:38 -0600 asked a question routing problem with floating ip addresses

I've got a three machine setup running Essex. Host a runs Glance, Keystone, and nova-* except nova-compute. Host b and c only run nova-compute. For the most part everything seems to work, I'm able to create instances. I can ping them from the Network-Controller using the private ip addresses and the floating ip addresses.

I'm using a FlatDHCP configuration, but the enterprise network in which the hosts run heavily uses vlans. For the setup of OpenStack I was granted three vlans 232, 233, 235. VLAN 235 is the dmz vlan. All vlans were created with gateways on the first ip address of the ip space. I originally wanted to use VLAN 232 for the vms, VLAN 233 for the host ips and VLAN 235 for floating ip addresses that are accessible from the outside. I ran into problems using the ip space of VLAN 232 for the private ip addresses, so i changed that to local ip adresses.

Created vms can access the internet as long as they don't have a floating ip address. As soon as I assign a floating ip address to a vm, the vms cannot access the internet anymore.

We checked on the network controller that the floating ip addresses were assigned: br235: <broadcast,multicast,up,lower_up> mtu 1500 qdisc noqueue state UP link/ether 00:46:e9:25:b2:38 brd ff:ff:ff:ff:ff:ff inet 192.168.135.1/24 brd 192.168.135.255 scope global br235 inet 138.246.18.131/32 scope global br235 inet 138.246.18.132/32 scope global br235 inet6 fe80::236:b9ff:fe25:b448/64 scope link valid_lft forever preferred_lft forever

But we're not able to ping this address from another server on the network. The routes on the network controller look like this:

Destination Gateway Genmask Flags Metric Ref Use Iface default 10.144.233.1 0.0.0.0 UG 100 0 0 br233 10.144.233.0 * 255.255.255.0 U 0 0 0 br233 192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0 192.168.235.0 * 255.255.255.0 U 0 0 0 br235

Does anyone know how the network controller usually propagates the floating ip addresses to the connected switches/routers? Or how I can check that he's doing it correctly?

2012-05-10 11:37:34 -0600 answered a question Instance does not bring up network interfaces

Thanks Vish Ishaya, that solved my question.

2012-05-10 11:37:26 -0600 answered a question Instance does not bring up network interfaces

Thanks for the answer, it was part of the problem and helped to solve it. The other part being network interface configuration of CentOS, which I was not very familiar with.

2012-05-08 08:41:11 -0600 asked a question Instance does not bring up network interfaces

I've got a two server setup running Essex. One server solely runs nova-compute, the other runs the rest of the services. I can bring up instances and ssh into them using some Ubuntu Cloud Image, that I downloaded. I wanted to run a CentOs 6.2 image, which I managed to create and run after struggling a bit with the custom image creation.

The problem I encountered was that I was neither able to ping nor ssh into the CentOs instance. But with the vnc console I was able to login and have a look. There I noticed, that no eth* interface was up and I was not able to get eth0 up, which I had previously used when I created the image. I checked /etc/udev/rules.d/70-persistent-net.rules, which had two new eth* interfaces (I got two networks assigned). After creating eth1 and eth2 using "setup" in CentOs and a reboot I was able to ping and ssh into the instance.

Is there a way that OpenStack automatically can create the interfaces and bring them up correctly?