Ask Your Question

eblock's profile - activity

2019-04-18 07:59:43 -0500 commented question Do i need to shutdown live VMs to restart Cinder service?

In general you don't have to shutdown VMs to restart openstack services. But I don't know exactly if already established connections will break if you change the password or if this is only relevant for new connections.

2019-04-15 02:26:22 -0500 commented question No Domain table is created in mySql

Was your keystone-bootstrap command successful? Did you set the environment variables (export OS_USERNAME=admin etc.) to be able to run the administrator tasks (creating domains etc.)?

2019-04-10 07:07:04 -0500 commented question vm filesystem shutting down

Are the VMs on local file storage on the hypervisors? Have you monitored disk utilization of your compute nodes? Maybe your disks are too slow, especially if you run heavy i/o, maybe even in parallel?

2019-04-08 08:22:00 -0500 commented question how to add custom script in instance while deploying application using murano

I don't have experience with murano, I don't know how that works so hopefully someone else can chime in here.

2019-04-05 07:27:31 -0500 commented question cinder mysql connection failed errno 113

It seems as if you can't resolve "controller", check your name resolution.

2019-04-03 09:27:40 -0500 commented question how to add custom script in instance while deploying application using murano

You can use cloud-init to inject all kinds of scripts and user-data into booting instances. Also there are plenty of answers on ask.openstack regarding cloud-init if you need more help.

2019-03-26 03:53:31 -0500 commented question Error when creating ubuntu 16.04 iso image on openstack queen in dashboard

Not sure if that's really the cause, but invalid visibility option is one clue. The other thing is Attempted scope to domain Default failed, will attemptto scope to another domain. You should check your configs, especially the keystone domain values.

2019-03-25 04:04:41 -0500 commented question After shutting down / powering up Ceph cluster, cannot start instances with encrypted volumes

Is the ceph cluster in a healthy state after the maintenance? Maybe the ceph logs reveal something helpful. Are the volumes accessible in the ceph cluster? Has anything changed in you configs, maybe something like rbd secret or anything else?

2019-03-13 03:32:24 -0500 commented question cinder instance launch trouble

This has been an issue for a couple of years now, see this bug I reported a while back. The comments in the bug also describe some workarounds, I'd recommend to read all of it, but maybe start trying the patches from the bottom first.

2019-03-07 07:54:42 -0500 commented answer How to remove compute Node.

Did you verify that the old compute node was indeed removed before adding the new one?

2019-03-07 02:30:08 -0500 commented answer How to remove compute Node.

I updated the answer. You should get an ID for each compute service, delete the one you don't need anymore (or want to replace). <...> is a placeholder, I assume you realize that.

2019-03-06 08:34:20 -0500 answered a question How to remove compute Node.

What have you tried so far? Have a look at this question. It's been a while since I did that, but I'd start with:

root@dfa-16-3e-14-27-0e:~ # openstack compute service list
+----+------------------+--------------------+----------+---------+-------+----------------------------+
| ID | Binary           | Host               | Zone     | Status  | State | Updated At                 |
+----+------------------+--------------------+----------+---------+-------+----------------------------+
|  3 | nova-scheduler   | dfa-16-3e-14-27-0e | internal | enabled | up    | 2019-03-07T08:26:12.000000 |
|  5 | nova-conductor   | dfa-16-3e-14-27-0e | internal | enabled | up    | 2019-03-07T08:26:16.000000 |
|  6 | nova-consoleauth | dfa-16-3e-14-27-0e | internal | enabled | up    | 2019-03-07T08:26:17.000000 |
|  7 | nova-compute     | dfa-16-3e-ec-08-35 | nova     | enabled | up    | 2019-03-07T08:26:12.000000 |
+----+------------------+--------------------+----------+---------+-------+----------------------------+

openstack compute service delete 7

After that I'd have a look at:

nova-manage cell_v2 list_hosts
nova-manage cell_v2 delete_host --cell_uuid <CELL_UUID> --host <HOST>

The last step should remove the host from the database. I'm not sure if more steps are required, but you can give it a try and report back. Is this a production environment or something you could break and start over?

2019-03-06 03:21:18 -0500 commented question Is it possible to resize a snapshot?

I might be wrong, but I'm not aware of such a feature and I've never heard of anything like that.

2019-03-05 01:56:35 -0500 received badge  Critic (source)
2019-03-05 01:56:29 -0500 answered a question How to resize VM root partition

You have to extend the respective partition(s) to your needs with tools like fdisk or parted etc. If you run fdisk -l /dev/vda you'll see that you have plenty of space but your partition table does not reflect that. To edit the partition table you can use fdisk /dev/vda without the -l.

But before you do anything, please make a backup of your instance so you can roll back. Also make sure you edit the partition table correctly, here's one example of how to do it. You can extend a partition without unmounting it, but you'll have to reboot after the resize2fs command.

Some images are able to recognize the actual disk size and resize their partitions during first boot, but that's not relevant right now. So please be careful what you're doing, and if you're not sure, ask someone to help you. And again: make a backup before changing the partition table!

2019-03-04 05:56:07 -0500 commented answer Instance launched from a snapshot

Bernd already answered your question regarding download time, whatever that is. Each image that a compute node has to use will be copied from glance to each compute node that has instances based on that image. A snapshot is also a glance image, so it doesn't make a difference.

2019-03-04 05:26:42 -0500 commented answer Instance launched from a snapshot

Yes, this seems to be a temporary issue, see this bug report. I'm not sure how to resolve this for now.

2019-03-04 05:24:07 -0500 commented answer Instance launched from a snapshot

I have the same error in a Rocky (test) environment, although the docs still refer to glance-cache-manage. Seems like a bug to me. Regarding the snapshot download: this is something openstack does internally, not you. If promoting an image to the cache would work an instance would be launched faster

2019-03-04 04:34:03 -0500 commented answer Instance launched from a snapshot

diff file, so every nova instance on that compute node is put together by the base image file and the changes made to the instance stored as a different file. If you launch more instances of the same base image on the same compute node the download from glance can be skipped, so it takes less time.

2019-03-04 04:31:34 -0500 commented answer Instance launched from a snapshot

When using file based images (like you seem to use) nova needs to have a copy of the original glance image, so this download from glance to the compute node takes time, the file is stored under /var/lib/nova/instances/_base. Another qcow file is stored under /var/lib/nova/instances/<instance> as a..

2019-03-04 04:29:22 -0500 commented answer Instance launched from a snapshot

I thought you also used Ceph as storage backend, my mistake. So if you're using file based images and instances you probably should enable image-cache for both glance and nova. Bernd already provided the required information. I'll try to rephrase the conclusion, maybe it will get clearer for you...

2019-03-04 03:02:30 -0500 answered a question Instance launched from a snapshot

IIRC you're using ceph as storage backend, in that case you should disable cache management since it's not required, see this for more information, I had the same issue some time ago. Most important thing for ceph backend: use "raw" image format for your glance images. Otherwise glance will download the whole image to the compute node to /var/lib/nova/instances/_base and then upload it back to ceph as a flat image, this can take a long time. Check your image's disk_format.

2019-03-04 02:52:29 -0500 commented question Extra nova volume attachment after cinder reset-state detached

And if the token expiration really is an issue, can't you just increase it? It's still not quite clear to me what you actually are trying to achieve and why the workarounds don't work for you.

2019-03-04 02:51:25 -0500 commented question Extra nova volume attachment after cinder reset-state detached

I'm not sure why the token expiration should take effect here. 1 hour to detach a volume should be quite enough, shouldn't it? As I already said, how could a command over the API work if the compute node is down? The only way I can imagine is the manipulation of the DB. So the answer is probably no.

2019-02-28 06:43:46 -0500 commented question Extra nova volume attachment after cinder reset-state detached

If the compute node is down then the services (nova and cinder) can't execute commands, so your API calls can't take effect. What storage backend are you using? Can't you bring the compute node back up?

2019-02-28 06:41:15 -0500 commented question Instance launched from a snapshot

But most importantly for ceph: use "raw" image format for your glance images. Otherwise glance will download the whole image to the compute node to /var/lib/nova/instances/_base and then upload it back to ceph as a flat image, this can take a long time. Check your image's disk_format.

2019-02-28 06:35:12 -0500 commented question Instance launched from a snapshot

@najeh do I remember correctly that you also have ceph as storage backend? If that's true then first disable glance image-cache management, see this thread for more information.

2019-02-27 08:30:44 -0500 commented question I have 8 Physical host i want to setup OOO openstack setup with Ceph. Deatils as Below.

As already said, use dedicated servers. Ceph is supposed to be a highly available storage cluster, running other services will have impact on the availability and also on the performance. You can mix ceph services on one host (OSD & MON), but don't mix ceph and other services, you'll regret.

2019-02-26 08:06:22 -0500 commented answer Instance Fails to Launch

check if you can manually connect from compute node to the DB using the credentials from your nova.conf.

2019-02-26 08:04:36 -0500 commented answer Add volumen group in cinder

Try to increase the volume creation timeouts in nova.conf (compute), the default won't suffice for such large volumes. Check the values for block_device_allocate_retries, block_device_allocate_retries_interval and block_device_creation_timeout. Increase them and restart the nova compute.

2019-02-22 08:18:01 -0500 commented answer How to enable audio on my instance?

This thread is rather old, but I'm still struggling with sound on a Windows VM. If I add <sound model='ich6'> <alias name='sound0'/> <address [...]/> </sound> to the xml of a running instance this works only if openstack is not involved. Is there still only the hacking way?

2019-02-22 04:19:00 -0500 commented question SSH key gets Injected to wrong user by cloud-init

Can you share more of your cloud.cfg? Do you attach any user-data file to the instance? I also recommend to delete all previous data from any cloud-init processes before uploading it as a new base image.

2019-02-22 04:16:09 -0500 commented question Rocky on CentOS7 - instance creation stuck in BUILD status

What is your storage backend for instances and volumes?

2019-02-22 04:15:51 -0500 commented question Rocky on CentOS7 - instance creation stuck in BUILD status

The "Final resource" message is not really related to a stuck build. If the compute node doesn't show any errors then the nova api doesn't even reach the point to actually build the instance. So you should look at nova-conductor and nova-scheduler logs on the control node, maybe also neutron logs.

2019-02-20 03:32:29 -0500 commented question ceph error during overcloud deploy

Unfortunately, I don't have experience with tripleo so I don't have an answer to that.

2019-02-20 03:28:38 -0500 commented question I have 8 Physical host i want to setup OOO openstack setup with Ceph. Deatils as Below.

For a production environment I would always recommend to use dedicated servers, mixing services like openstack and ceph is not a good idea. Performance impacts during Ceph recovery can be huge, especially if the compute nodes also run VMs.

2019-02-20 03:22:00 -0500 commented question Instance in compute node cannot get ip from dhcp

Did you enable DHCP in the base image? Have you verified that the subnet has DHCP enabled? openstack subnet show <SUBNET_ID> | grep enable_dhcp

2019-02-19 02:45:30 -0500 commented question ceph error during overcloud deploy

Have you tried to execute the ceph-volume command manually? The --prepare option is recognized in my Luminous cluster (12.2.10). But IIRC the 12.2.9 release you seem to be using was a very bad one. Do you have the option to use a later release? 12.2.11 has been released recently.

2019-02-18 02:42:25 -0500 commented question Receiving error NetworkNotFoundClient

What about neutron linuxbridge-agent logs from compute node? Can you check them, too? According to the docs the v3 entries are not required anymore, so I don't see that as a potential problem.

2019-02-18 02:04:22 -0500 commented question instance creation stuck on 'BUILD' state

What about nova-conductor.log? Are all nova and neutron services up and running?

2019-02-14 10:03:30 -0500 commented question How to bring up multiple interfaces up with cloud-init

That user-data can contain all kinds of commands, create network configs, restart services and so on. For example, we use that to enable salt-minion with a startup config and that minion registers itself at the salt-master and receives further configuration, everything we need is done via salt.

2019-02-14 10:01:52 -0500 commented question How to bring up multiple interfaces up with cloud-init

I might be wrong, but my understanding of cloud-init is to execute an initial configuration at first boot, just some basic stuff. The rest has to be handled by salt, puppet or other automatic configruation tools, or the admin user. You can add user-data for cloud-init to run after boot.

2019-02-14 08:01:39 -0500 commented question Receiving error NetworkNotFoundClient

Either your neutron config or the neutron section in the nova config(s) (more likely) is probably wrong. Can you verify if the network id actually exists? Run openstack network show 958824f7-cbf7-41b3-9700-d7c24860fa82 and paste the output. Also check neutron logs for more hints.

2019-02-14 04:04:28 -0500 commented question What is necessary to make Neutron changes?

Can you show output of openstack network agent list? You can edit your question and add the output to it. Also paste the output of systemctl status openstack-neutron-linuxbridge-agent.service and check /var/log/neutron/neutron-linuxbridge-agent.log. Is the device mapping valid on your nodes?

2019-02-14 02:45:55 -0500 commented question Openstack compute node not recognized as hypervisor

So in fact the compute node is discovered, then try running an instance on it:

openstack server create --image <IMAGE> --flavor <FLAVOR> --nic net-id=<NET_ID> --availability-zone nova:openstack-2 <VM_NAME>

Monitor nova logs on control and compute node during this to see if the instance fails.