September 2020 - openstack-discuss

watchdog fed successfully event of 6300esb
by ligang (P) 07 Sep '20

07 Sep '20

Hi folks, I have an question to discuss about the 6300esb watchdog. I think is it possible that qemu can send an event while the watchdog successfully fed by the vm at the first time. Here is the situation: Qemu will send an VIR_DOMAIN_EVENT_ID_WATCHDOG event while watch dog timeout, and if the action of the watchdog in xml of the vm was set to "reset", the vm will be rebooted while timeout. I have an monitor process that register callback function of the VIR_DOMAIN_EVENT_ID_WATCHDOG event, the callback function will send an alarm to my upper layer monitor platform indicate that the vm is fault, and the cluster deployed business on the vm will isolate the vm by the alarm. And after the vm rebooted , the monitor process will receive an reboot event and send it to the platform, the upper layer monitor platform will clear the alarm, and business continue to run on the vm. In most cases ,the watch dog process in vm will feed the watchdog after vm rebooted and all things go back on track. In some other cases,the guestos may failed to start (in my environment vm start failed by io error), but the reboot event will still be received and the alarm will be cleared and the vm is still fault. So the this may not a good idea to clear the alarm by the reboot event. So, I think it will be helpful that the qemu can send an event while the watchdog successfully fed by the vm at the first time. So I can exactly know that the guest os go back on running and the watch dog initialized successfully. Or any other opintion about this situation. Thanks.

1 0

New deployed packstack openstack, Failed create instance due to volume failed to created
by dangerzone ar 07 Sep '20

07 Sep '20

Hi, my clean install openstack queens are not able to create simple instance. Got error *Error: Failed to perform requested operation on instance "test1", the instance has an error status: Please try again later [Error: Build of instance 18c607fd-e919-4022-be7d-d178d7ab410e aborted: Volume 8a3b3e80-1593-46e5-8aa8-a5083bfbb46f did not finish being created even after we waited 9 seconds or 4 attempts. And its status is error.].* Filesystem Size Used Avail Use% Mounted on devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 4.0K 3.9G 1% /dev/shm tmpfs 3.9G 25M 3.8G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/mapper/centos-root 48G 34G 15G 71% / /dev/sda1 1014M 182M 833M 18% /boot /dev/mapper/centos-home 24G 33M 24G 1% /home tmpfs 783M 0 783M 0% /run/user/1000 /dev/loop1 1.9G 6.1M 1.7G 1% /srv/node/swiftloopback tmpfs 783M 0 783M 0% /run/user/0 pvs PV VG Fmt Attr PSize PFree /dev/loop0 cinder-volumes lvm2 a-- <20.60g 1012.00m /dev/sda2 centos lvm2 a-- <79.00g 4.00m vgs VG #PV #LV #SN Attr VSize VFree centos 1 3 0 wz--n- <79.00g 4.00m cinder-volumes 1 1 0 wz--n- <20.60g 1012.00m seems my cinder volume no free space. I install VM with 80G storage but cinder volume no space. I tried extend cinder volume as follows *lvm vgextend "cinder-volumes" /dev/loop3 Physical volume "/dev/loop3" successfully created. Volume group "cinder-volumes" successfully extendedpvscan PV /dev/loop0 VG cinder-volumes lvm2 [<20.60 GiB / 1012.00 MiB free] PV /dev/loop3 VG cinder-volumes lvm2 [<30.00 GiB / <30.00 GiB free] PV /dev/sda2 VG centos lvm2 [<79.00 GiB / 4.00 MiB free] Total: 3 [<129.59 GiB] / in use: 3 [<129.59 GiB] / in no VG: 0 [0 ]* *vgs VG #PV #LV #SN Attr VSize VFree centos 1 3 0 wz--n- <79.00g 4.00m cinder-volumes 2 1 0 wz--n- 50.59g 30.98g* When try to create new instance I keep getting the same volume error... Please help and advise what should I do...Please help...why 80G still not enough for cinder volume. Appreciate help. Thank you

3 5

[kolla] Kolla klub break
by Mark Goddard 07 Sep '20

07 Sep '20

Hi, We agreed in Wednesday's IRC meeting to take a short summer break from the klub. Let's meet again on 10th September. Thanks to everyone who has taken part in these meetings so far, we've had some really great discussions. As always, if anyone has ideas for topics, please add them to the Google doc. Looking forward to some more great sessions in September. https://docs.google.com/document/d/1EwQs2GXF-EvJZamEx9vQAOSDB5tCjsDCJyHQN5_… Thanks, Mark

1 1

[kolla] virtual PTG
by Mark Goddard 07 Sep '20

07 Sep '20

Hi, The next PTG will be virtual again, and held from Monday October 26th to Friday October 30th. For those who have not attended before, the PTG is where we discuss various aspects of the project, and eventually decide on priorities for the next development cycle. I have provisionally booked the same slots as last time: * Monday 26th 13:00 - 17:00 UTC (kolla & kolla ansible) * Tuesday 27th 13:00 - 17:00 UTC (kolla & kolla ansible) * Wednesday 28th 13:00 - 15:00 UTC (kayobe) Please get in touch if you would like to attend but these slots are not suitable for you. In particular, if you are in a time zone where these times are unsociable, we could consider running some sessions during a different 4 hour block. Thanks, Mark

1 0

[neutron][policy] Admin user can do anything without the control of policy.json?
by Zhi CZ Chang 07 Sep '20

07 Sep '20

2 1

[neutron] Bug deputy report (week starting on 2020-08-31)
by Bernard Cafarelli 07 Sep '20

07 Sep '20

Hello neutrinos, back to school week in some parts of the world, and new bug deputy rotation for us! Here is the bug list for week 36 A relatively quiet week on the new numbers count, all urgent bugs were handled Critical * openstack-tox-py36-with-ovsdbapp-master periodic job is failing everyday since 28.08.2020 - https://bugs.launchpad.net/neutron/+bug/1893965/ Patch merged in neutron https://review.opendev.org/#/c/749537/ High * [OVN Octavia Provider] OVN provider fails during listener delete - https://bugs.launchpad.net/neutron/+bug/1894136 Assigned to Brian Medium * [ovn] Limit the number of metadata workers - https://bugs.launchpad.net/neutron/+bug/1893656 Aims to use a separate config option than metadata_workers one, unassigned in neutron (working in tripleo and fixed in charm) * neutron-ovn-db-sync-util: Unhandled error: oslo_config.cfg.NoSuchOptError: no such option keystone_authtoken in group [DEFAULT] - https://bugs.launchpad.net/neutron/+bug/1894048 This was fixed previously in bug 1882020, but is observed again, unassigned * ovn: filtering hash ring nodes is not time zone aware - https://bugs.launchpad.net/neutron/+bug/1894117 Timezone fun, unassigned Wishlist * For neutron-l3-agent, after the execution of the linux command fails, it is not displayed which command failed to execute - https://bugs.launchpad.net/neutron/+bug/1893627 Add failed command to error log Patch merged: https://review.opendev.org/#/c/749076/ Incomplete * Upgrading from train(el7) to ussuri(el8): Packet sequence number wrong - got 2 expected 1 - https://bugs.launchpad.net/neutron/+bug/1894077 Migration error on port forwarding description Undecided * Get domain name for dhcp from neutron db - https://bugs.launchpad.net/neutron/+bug/1893802 This one needs confirmation from subject experts, but as described in comment I think this was attempted and reverted before - and this marked as invalid (or to fix in another way) -- Bernard Cafarelli

1 0

[mq][mariadb] What kind of reasons are considered when choosing the mq/mariadb version
by Brin Zhang(张百林) 07 Sep '20

07 Sep '20

Hi all We are using kolla to build the OpenStack, use kolla-ansible to deploy rabbitmq is v3.7.10, mariadb is v10.1.x when building Rocky release rabbitmq is v3.8.5, mariadb is v10.3.x when building Ussuri release what kind of reasons are considered as rabbitmq version is changed from v3.7.10 to v3.8.5 ? what kind of reasons are considered as mariadb version is changed from v10.1.x to v10.3.x ? If you can provide an explanation, or key explanation, we would be very grateful. Thanks. brinzhang

5 8

[kolla-ansible] prometheus.yml is empty
by Tony Liu 06 Sep '20

06 Sep '20

Hi, I deployed Prometheus with Kolla Ansible (10.1.0.dev36 from PIP). Given the following log, the change has been made on nodes. ============================= TASK [prometheus : Copying over prometheus config file] ************************ skipping: [os-control-2] => (item=/usr/local/share/kolla-ansible/ansible/roles/prometheus/templates/prometheus.yml.j2) skipping: [os-control-1] => (item=/usr/local/share/kolla-ansible/ansible/roles/prometheus/templates/prometheus.yml.j2) skipping: [os-control-3] => (item=/usr/local/share/kolla-ansible/ansible/roles/prometheus/templates/prometheus.yml.j2) skipping: [compute-1] => (item=/usr/local/share/kolla-ansible/ansible/roles/prometheus/templates/prometheus.yml.j2) changed: [monitor-2] => (item=/usr/local/share/kolla-ansible/ansible/roles/prometheus/templates/prometheus.yml.j2) changed: [monitor-1] => (item=/usr/local/share/kolla-ansible/ansible/roles/prometheus/templates/prometheus.yml.j2) changed: [monitor-3] => (item=/usr/local/share/kolla-ansible/ansible/roles/prometheus/templates/prometheus.yml.j2) ============================= But the /etc/kolla/prometheus-server/prometheus.yml on monitor-* nodes is empty. ============================= {} ============================= Anything I am missing here? Thanks! Tony

1 1

[sdk][python-openstackclient] Request the code review about the story: openstack CLI - Create an instance using --image-property filtering not working.
by Myeong Chul Chae 06 Sep '20

06 Sep '20

Hi. I researched the story 'openstack CLI - Create an instance using --image-property filtering not working' and modified the code to solve it. This is the issue that I opened. - Link <https://review.opendev.org/#/c/746405/> And the hyperlink of the story is here <https://storyboard.openstack.org/#!/story/2007860>. In addition, there is a review <https://review.opendev.org/#/c/740455/> posted before my review of the same story, so conflict resolution is necessary. Please check the commit message and history of the two reviews and continue the discussion.

1 0

[kolla-ansible] Difference between deploy and reconfigure?
by Tony Liu 06 Sep '20

06 Sep '20

Hi, What's the difference between deploy and reconfigure? I checked some roles, reconfigure.yml just include_tasks deploy.yml. And I didn't find reconfigure as a condition for any tasks or handlers. I checked kolla-ansible script, the difference is ANSIBLE_SERIAL is specified by reconfigure. I also see comment saying "Serial is not recommended and disabled by default.". Here are some cases. I'd like to know which should be used. #1 Add compute. After updating inventory with the new compute node, "deploy --limit new-compute" and "reconfigure --limit new-compute", do they have the same result? If not, what's the difference? #2 Change configuration. In case configuration is changed in global.yml or inventory, which of "deploy" or "reconfigure" should be executed to update the cluster? Same or any difference? #3 Fix the cluster I was told to rerun playbook to fix some problems, like a container was deleted. "deploy --limit host" or "reconfigure --limit host"? Same or any difference? Thanks! Tony

2 1