Ask Your Question

vgdub's profile - activity

2019-01-23 12:27:51 -0500 answered a question how neutron dhcp allocates ip

May be anyone who were able to solve the issue can update the below thread , because in my kilo network this recently started and I am not sure what is literally causing this. I would appreciate the help.

https://ask.openstack.org/en/question...

2019-01-23 08:19:21 -0500 answered a question liberty: dhcp agent not updating dnsmasq hosts file without restart of agent

Hey guys @dbaxps @jkilborn I am facing the same issue in my environment , I have to the point same issue , whenever I restart the neutron-dhcp-agent.service it updates the dnsmasq hosts file from database and all new VMs get the IP.

The funny part with my environment is that this is only happening very randomly , so like I have 120 namespaces and among this very randomly any 1 or 2 tenant network reports this issue nad it's not always the same tenant it's very random. I am just not sure what the issue is neutron-dhcp-agent is not able to do that and just give away this. any pointers would be appreciated.

I am aware of the fact that once neutron creates the port , dhcp agent which is talking to database has to update it's namespace files/records , but I am just not sure why randomly someday this doesn't happen for 1 or 2 tenant network.

I have controller which hosts API services and Neutron server on separate node and multiple compute nodes. Please help.

"DHCPDISCOVER(tapXXX) fa:16:3e:ec:bd:ad "no address available" dnsmasq-dhcp[3633]: 3621066038 available DHCP subnet: 172.17.x.x/255.255.255.0

Also every time when I bounce the neutron-dhcp-agent service it reloads the files in dhcp namespace and all works fine. It also happened with me that when I tried to bounce the neutron-dhcp-agent service it also rebooted the neutron server itself.

2018-11-27 04:09:01 -0500 received badge  Necromancer (source)
2018-11-27 04:09:01 -0500 received badge  Teacher (source)
2018-11-17 12:00:54 -0500 asked a question cinder-volume service not able to talk to cinder-scheduler , new volume creation failing

I have recently started seeing issues on the storage node where I have rbd driver configured as well as this node also act as a compute node for vms. This node was working perfectly fine for sometime back but I just did some cleaning on my ceph storage cluster by removing the bad osd's out of the cluster and post that I restarted some of my cinder services on controller and storage node and I started to see all issues on this node with below error. I can confirm that my controller node is absolutely fine as I have other zones using cinder-volume service and they are working fine using the same controller.

I also tried below options already. 1. restarted storage node physically as well as all relevant services. 2. I also checked in cinder service-list and the volume service is enabled and up in the controller. 3. I also tried direct command line and cinder-api accepts the request and creates the volume but it goes from creating --> error state and just ends there. 4. Regularly checking the cinder-scheduler service to identify cinder-volume host update but it's not able to see the host. 5. I also tried to manually create a volume in ceph on the same node using rbd driver commands and it works so connectivity from cinder-volume to ceph is also good.

I don't know what has gone wrong all of a sudden , below are the logs I am seeing, I would sincerely appreciate any help.

Openstack Version: Kilo ceph storage cluster: ceph cluster Glance is working too.

2018-11-17 17:45:40.444 32054 INFO cinder.volume.manager [req-d4d12536-3d95-423e-869f-836178cfcc83 - - - - -] Updating volume status 2018-11-17 17:45:40.445 32054 WARNING cinder.volume.manager [req-d4d12536-3d95-423e-869f-836178cfcc83 - - - - -] Unable to update stats, RBDDriver -1.1.0 (config name ceph06) driver is uninitialized. 2018-11-17 17:45:45.349 32044 DEBUG cinder.openstack.common.periodic_task [req-065127a6-a147-4737-9ffc-9a86a69da51a - - - - -] Running periodic task VolumeManager._publish_service_capabilities run_periodic_tasks /usr/lib/python2.7/site-packages/cinder/openstack/common/periodic_task.py:219 2018-11-17 17:45:45.350 32044 DEBUG cinder.openstack.common.periodic_task [req-065127a6-a147-4737-9ffc-9a86a69da51a - - - - -] Running periodic task VolumeManager._report_driver_status run_periodic_tasks /usr/lib/python2.7/site-packages/cinder/openstack/common/periodic_task.py:219 2018-11-17 17:45:45.351 32044 INFO cinder.volume.manager [req-065127a6-a147-4737-9ffc-9a86a69da51a - - - - -] Updating volume status 2018-11-17 17:45:45.352 32044 WARNING cinder.volume.manager [req-065127a6-a147-4737-9ffc-9a86a69da51a - - - - -] Unable to update stats, RBDDriver -1.1.0 (config name ceph04) driver is uninitialized. 2018-11-17 17:46:01.622 32058 DEBUG cinder.openstack.common.periodic_task [req-b2cc861b-0524-4f27-982e-069ab9095b3a - - - - -] Running periodic task VolumeManager._publish_service_capabilities run_periodic_tasks /usr/lib/python2.7/site-packages/cinder/openstack/common/periodic_task.py:219 2018-11-17 17:46:01.623 32058 DEBUG cinder.openstack.common.periodic_task [req-b2cc861b-0524-4f27-982e-069ab9095b3a - - - - -] Running periodic task VolumeManager._report_driver_status run_periodic_tasks /usr/lib/python2.7/site-packages/cinder/openstack/common/periodic_task.py:219 2018-11-17 17:46:01.624 32058 INFO cinder.volume.manager [req-b2cc861b-0524-4f27-982e-069ab9095b3a - - - - -] Updating volume status 2018-11-17 17:46:01.625 32058 WARNING cinder.volume.manager [req-b2cc861b-0524-4f27-982e-069ab9095b3a - - - - -] Unable to update stats, LVMISCSIDriver -3.0.0 (config name ceph) driver is uninitialized. 2018-11-17 17:46 ...

(more)
2018-11-17 11:50:34 -0500 commented answer cinder LVMISCSIDriver Unable to update stats, driver is uninitialized

I have the very same issue and I have the above driver for rbd added correctly but I am not able to create a new volume from the option(create a new volume) from nova and I can confirm that rbd driver is perfectly working fine.

2018-11-17 17:45:40.444 32054 INFO cinder.volume.manager [req-d4d12536-

2018-11-16 03:31:30 -0500 commented answer Unable to create cinder volume?

@amedeo @cloudlearer I am not sure what's the suggestion here , but I was running cinder-compute in controller and 1 compute node and it worked perfectly for me, but for some reason I am not able to get any stats from cinder-volume compute node to cinder-scheduler on controller....any ideas?

2018-11-15 19:15:49 -0500 commented answer Stuck while creating a volume in Cinder, AMQP seems broken

@Loick75 , I still didn't get it , how is attach and dettach the screen reoslved the issue of scheduler and volume , in my case controller runs scheduler service and cinder-volume service is run on compute nodes , how did you actually solve this problem ? The Attach and Dettach seems magical ?

2018-11-14 11:42:48 -0500 received badge  Editor (source)
2018-11-14 11:37:32 -0500 answered a question mariadb connection aborted

Hello All, I am not sure if this is ever fixed or if it was how was this fixed , I have been having the same issue on my Openstack kilo installation. This has severely impacted my entire platform as keystone,Glance,Cinder,Nova is showing this issue which is literally the whole platform and I am not able to create any new VM's/Volumes etc my backend ceph is working absolutely fine.

I would be grateful if you share the resolution for the same. Also my mariadb is quite old too.

Server version: 5.5.45-MariaDB-wsrep MariaDB Server, wsrep_25.11.r4026

181114 17:12:36 [Warning] Aborted connection 272732 to db: 'keystone' user: 'keystone' host: '' (Unknown error) 181114 17:13:41 [Warning] Aborted connection 271127 to db: 'keystone' user: 'keystone' host: '' (Unknown error) 181114 17:13:53 [Warning] Aborted connection 272971 to db: 'glance' user: 'glance' host: '' (Unknown error) 181114 17:13:53 [Warning] Aborted connection 272972 to db: 'glance' user: 'glance' host: '' (Unknown error) 181114 17:13:54 [Warning] Aborted connection 272964 to db: 'glance' user: 'glance' host: '' (Unknown error) 181114 17:13:54 [Warning] Aborted connection 267103 to db: 'glance' user: 'glance' host: '' (Unknown error) 181114 17:13:54 [Warning] Aborted connection 267104 to db: 'glance' user: 'glance' host: '' (Unknown error) 181114 17:13:55 [Warning] Aborted connection 267686 to db: 'nova' user: 'nova' host: '' (Unknown error) 181114 17:13:58 [Warning] Aborted connection 272070 to db: 'keystone' user: 'keystone' host: '' (Unknown error) 181114 17:14:35 [Warning] Aborted connection 273102 to db: 'keystone' user: 'keystone' host: '' (Unknown error) 181114 17:17:36 [Warning] Aborted connection 270964 to db: 'keystone' user: 'keystone' host: '' (Unknown error) 181114 17:17:37 [Warning] Aborted connection 272733 to db: 'keystone' user: 'keystone' host: '' (Unknown error) 181114 17:19:58 [Warning] Aborted connection 272989 to db: 'keystone' user: 'keystone' host: '' (Unknown error) 181114 17:19:58 [Warning] Aborted connection 274142 to db: 'keystone' user: 'keystone' host: '' (Unknown error) 181114 17:20:45 [Warning] Aborted connection 274285 to db: 'keystone' user: 'keystone' host: '' (Unknown error) 181114 17:22:20 [Warning] Aborted connection 274572 to db: 'glance' user: 'glance' host: ' (Unknown error) 181114 17:22:20 [Warning] Aborted connection 274573 to db: 'glance' user: 'glance' host: '' (Unknown error) 181114 17:22:20 [Warning] Aborted connection 269268 to db: 'glance' user: 'glance' host: '' (Unknown error) 181114 17:22:20 [Warning] Aborted connection 274576 to db: 'glance' user: 'glance' host: '' (Unknown error) 181114 17:22:20 [Warning] Aborted connection 274577 to db: 'glance' user: 'glance' host: '' (Unknown error) 181114 17:22:20 [Warning] Aborted connection 274578 to db: 'glance' user: 'glance' host: '' (Unknown error) 181114 17:22:20 [Warning] Aborted connection 274571 to db: 'glance' user: 'glance' host: '' (Unknown error) 181114 17:22:21 [Warning] Aborted connection 272969 to db: 'glance' user: 'glance' host: '' (Unknown error) 181114 17:22:21 [Warning] Aborted connection 272970 to db: 'glance' user: 'glance' host: '' (Unknown error) 181114 17:22:22 [Warning] Aborted connection 274585 to db: 'nova' user: 'nova' host ...

(more)
2018-09-05 15:50:56 -0500 commented answer Ceph-OpenStack integration "unable to update stats, RBDdriver -1.1.0 driver is uninitialized" error(Kilo Hammer)

I have never been able to solve this issue , But I could confirm that I am able to connect to the backend cluster but I am always getting RBD Driver (config XXX) is uninitialized. If anyone has any leads to troubleshoot this I would appreicate , I have already checked permissions in ceph.conf etc.

2018-09-05 15:48:20 -0500 received badge  Enthusiast
2018-09-03 13:55:31 -0500 commented answer cinder.volume.manager driver is uninitialized

Hi , did you solve this by changing the cinder user in Controller node or on the storage node where cinder-volume is running ?

2018-09-03 13:55:31 -0500 answered a question OPENSTACK KILO - VM's stuck in scheduling state

Were you able to resovle this error ? I am also getting the same in Openstack kilo version. please let me know.

2018-09-03 13:55:31 -0500 answered a question Cinder volume creation stuck in status "Creating" with openstack kilo on centos 7"

Was there ever a resolution to this ?? I know this was a bug but we never update how this was resolved.

Please update the thread it's never got resolved.

2018-09-03 13:55:29 -0500 answered a question cannot create volumes, stuck in creation

please folks if you were able to resolve this then update the post , we have been going mad about this "stuck in creating" state. Please help .