April 2022 - openstack-discuss - lists.openstack.org

[Kolla-ansible][Xena] Error deploying Cloudkitty
by wodel youchi 26 Apr '22

26 Apr '22

Hi, I am trying to deploy Cloudkitty, but I get this error message : TASK [cloudkitty : Creating Cloudkitty influxdb database] > ****************************************************** > task path: > /home/deployer/kollavenv/xenavenv/share/kolla-ansible/ansible/roles/cloudkitty/tasks/bootstrap.yml:36 fatal: [192.168.1.5 -> 192.168.1.5]: FAILED! => { > "action": "influxdb_database", > "changed": false, > "invocation": { > "module_args": { > "database_name": "cloudkitty", > "hostname": "dashint.cloud.cerist.dz", > "password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER", > "path": "", > "port": 8086, > "proxies": {}, > "retries": 3, > "ssl": false, > "state": "present", > "timeout": null, > "udp_port": 4444, > "use_udp": false, > "username": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER", > "validate_certs": true > } > }, > "msg": "('Connection aborted.', RemoteDisconnected('Remote end closed > connection without response',))" > } On the influxdb container I did this : > [root@controllerb ~]# docker ps | grep inf > 68b3ebfefbec > 192.168.1.16:4000/openstack.kolla/centos-source-influxdb:xena > "dumb-init --single-…" 22 minutes ago Up 22 minutes > influxdb > [root@controllerb ~]# docker exec -it influxdb /bin/bash > (influxdb)[influxdb@controllerb /]$ influx > Failed to connect to http://localhost:8086: Get http://localhost:8086/ping: > dial tcp [::1]:8086: connect: connection refused > Please check your connection settings and ensure 'influxd' is running. > (influxdb)[influxdb@controllerb /]$ ps -ef > UID PID PPID C STIME TTY TIME CMD > influxdb 1 0 0 Apr18 ? 00:00:00 dumb-init > --single-child -- kolla_start > influxdb 7 1 0 Apr18 ? 00:00:01 /usr/bin/influxd > -config /etc/influxdb/influxdb.conf > influxdb 45 0 0 00:12 pts/0 00:00:00 /bin/bash > influxdb 78 45 0 00:12 pts/0 00:00:00 ps -ef > (influxdb)[influxdb@controllerb /]$ I have no log file for influxdb, the directory is empty. Any ideas? Regards.

4 7

Setup infrastructure failing
by Derek O keeffe 26 Apr '22

26 Apr '22

Hi all, We get the following error in the openstack.osa.db_setup : Create database for service task: failed: [infra1_keystone_container-e54c8ba5 -> infra1_utility_container-1a1eb7ce(xx.xx.xx.xxx)] (item={'name': 'keystone', 'users': [{'username': 'keystone', 'password': 'PASSWORD'}]}) => {"ansible_loop_var": "item", "changed": false, "item": {"name": "keystone", "users": [{"password": "PASSWORD", "username": "keystone"}]}, "msg": "unable to connect to database, check login_user and login_password are correct or /root/.my.cnf has the credentials. Exception message: (2003, \"Can't connect to MySQL server on 'xx.xx.xx.xxx' ([Errno 111] Connection refused)\")"} Also, ansible galera_container -m shell -a "mysql -h localhost -e 'show status like \"%wsrep_cluster_%\";'" is different to the example output: infra1_galera_container-90dd1571 | CHANGED | rc=0 >>Variable_name Valuewsrep_cluster_weight 1wsrep_cluster_capabilities wsrep_cluster_conf_id 1wsrep_cluster_size 1wsrep_cluster_state_uuid c06b8107-c53a-11ec-a54c-a20664362f6cwsrep_cluster_status Primary We checked our infra node and all the containers are present and mysql is installed on the infra1-galera-container and port 3306 is open. MariaDB [(none)]> show databases;+--------------------+| Database |+--------------------+| information_schema || mysql || performance_schema || sys |+--------------------+4 rows in set (0.001 sec) We are not sure what is causing this and it could possibly be that we have forgotten/skipped/missed a configuration step but we have gone over the process multiple times and cannot see what we may have missed. The previous playbooks did have a lot of "skipped" results compute1 : ok=120 changed=2 unreachable=0 failed=0 skipped=31 rescued=0 ignored=0 compute2 : ok=120 changed=2 unreachable=0 failed=0 skipped=31 rescued=0 ignored=0 infra1 : ok=156 changed=3 unreachable=0 failed=0 skipped=31 rescued=0 ignored=0 infra1_aodh_container-7c703324 : ok=89 changed=36 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 infra1_ceilometer_central_container-7590db72 : ok=89 changed=36 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 infra1_cinder_api_container-91806531 : ok=89 changed=36 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 infra1_galera_container-90dd1571 : ok=89 changed=36 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 infra1_glance_container-fff39ac4 : ok=89 changed=36 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 infra1_gnocchi_container-ffd32a8b : ok=89 changed=36 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 infra1_heat_api_container-a4079838 : ok=89 changed=36 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 infra1_horizon_container-9c041ec0 : ok=89 changed=36 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 infra1_keystone_container-e54c8ba5 : ok=89 changed=36 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 infra1_memcached_container-dc50bcd8 : ok=89 changed=36 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 infra1_neutron_server_container-bfc4d0d2 : ok=92 changed=37 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 infra1_nova_api_container-f231bb13 : ok=89 changed=36 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 infra1_placement_container-108d79df : ok=89 changed=36 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 infra1_rabbit_mq_container-50ca98ed : ok=89 changed=36 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 infra1_repo_container-ccade01d : ok=89 changed=36 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 infra1_utility_container-1a1eb7ce : ok=89 changed=36 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 localhost : ok=19 changed=0 unreachable=0 failed=0 skipped=14 rescued=0 ignored=0 compute1 : ok=0 changed=0 unreachable=0 failed=0 skipped=10 rescued=0 ignored=0 compute2 : ok=0 changed=0 unreachable=0 failed=0 skipped=10 rescued=0 ignored=0 infra1 : ok=38 changed=0 unreachable=0 failed=0 skipped=35 rescued=0 ignored=0 infra1_galera_container-90dd1571 : ok=69 changed=3 unreachable=0 failed=0 skipped=12 rescued=0 ignored=0 infra1_memcached_container-dc50bcd8 : ok=16 changed=0 unreachable=0 failed=0 skipped=4 rescued=0 ignored=0 infra1_rabbit_mq_container-50ca98ed : ok=69 changed=33 unreachable=0 failed=0 skipped=14 rescued=0 ignored=0 infra1_utility_container-1a1eb7ce : ok=40 changed=18 unreachable=0 failed=0 skipped=11 rescued=0 ignored=0 A lot were around Galera tasks but we are not sure if they were skipped intentionally as the playbooks ran to completion.Any help or troubleshooting steps would be appreciated. Thanks in advance. Regards,Derek

2 1

[skyline] skyline-console whl package question
by Satish Patel 26 Apr '22

26 Apr '22

Folks, I am compiling skyline-apiserver on my bare metal server and found Makefile pulling skyline-console tarball from the following location but that package doesn't contain the latest merged patches. Does CI job is broken which compiles this tarball ? https://tarballs.opendev.org/openstack/skyline-console/

2 2

[oslo][ops] Change in default logging format
by Stephen Finucane 26 Apr '22

26 Apr '22

I'm not sure how many people read release notes for the various oslo libraries, so I'm posting this here since it might have a minor impact for some tooling operators are using. We've just merged [1] which changes the default logging format used by oslo.log, configured using the '[DEFAULT] logging_context_format_string' config option. Previously, our logging format was: %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user_identity)s] %(instance)s%(message)s This looks like e.g. 2022-04-26 10:49:14.629 4187413 WARNING nova.conductor.api [req-ffddccd3-8804-4fc3-a2f3-a05af1eb569f - - - - -] This has now been modified to include the global request ID as well as the local request ID: %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(global_request_id)s %(request_id)s %(user_identity)s] %(instance)s%(message)s This looks like e.g.: 2022-04-26 10:53:16.756 4187784 DEBUG nova.service [None req-f1698728-a2d6-4e02-a6b4-cf2cd398c02f - - - - -] Join ServiceGroup membership for this service compute This will affect pretty much all services using the out-of-the-box logging configuration. However, I suspect very few if any users are using the standard configuration. DevStack overrides '[DEFAULT] logging_context_format_string' for all services [2] and I suspect other installers probably do the same. If you are using the standard configuration, you might need to modify some log parsing/scraping tooling when this rolls around or manually set '[DEFAULT] logging_context_format_string' in your service configuration files. Cheers, Stephen [1] https://review.opendev.org/c/openstack/oslo.log/+/838190 [2] https://github.com/openstack/devstack/blob/3b0c035b9/functions#L677-L707

1 0

[all][neutron][neutron-vpnaas] Maintainers needed
by Lajos Katona 26 Apr '22

26 Apr '22

Hi, In the last few cycles neutron-vpnaas has no serious maintainers, and most patches merged were from Neutron core team or from Release team. Recently even neutron-vpnaas gate jobs started to fail. During the Zed PTG we discussed this topic (see [1]), For the maintenance we need someone to be the contact person for the project, who takes care of the project’s CI and review patches, answers bugs. Of course that’s only a minimal requirement. If the new maintainer works on new features for the project, it’s even better :) If we don’t have any new maintainer(s) before milestone Zed-2, which is July 11 - July 15 week according to [2], we will start marking neutron-vpnaas as deprecated and in the next cycle (AA, or perhapc 2023.1) we will propose to retire the project. So if You are using this project now, or if You have customers who are using it, please consider the possibility of maintaining it. Otherwise, please be aware that it is highly possible that the project will be deprecated and moved out from the official OpenStack projects. [1]: https://etherpad.opendev.org/p/neutron-zed-ptg#L201 [2]: https://releases.openstack.org/zed/schedule.html Lajos Katona (lajoskatona)

2 2

[cinder] how cinder gets the volume name when restore from a backup?
by Tony Liu 26 Apr '22

26 Apr '22

Hi, Here is what I do. * Create a volume. * Create a backup of this volume. * Delete the volume. * Restore the volume from backup. The restored volume has different UUID, but the same name. I don't see volume name is stored in backup metadata. How does Cinder know the volume name when restore it from backup, given the volume is already deleted? Thanks! Tony

2 2

retention policy for deleted resource in database
by Tony Liu 26 Apr '22

26 Apr '22

Hi, I see the record for deleted resource stay in database. What's the retention policy for those records? Is it configurable? Any manual cleanup is required? Thanks! Tony

2 2

[neutron] Bug Deputy Report Apr 18 - Apr 24
by Oleg Bondarev 25 Apr '22

25 Apr '22

Hello Team, Bug report for the week of Apr 18 is below. Two OVN bugs (including Invalid one) need triage from the OVN team. High ------ - https://bugs.launchpad.net/neutron/+bug/1969615 - OVS: flow loop is created with openvswitch version 2.16 - Opinion - seems more an issue in OVS rather than a bug in Neutron - Unassigned Undecided -------------- - https://bugs.launchpad.net/neutron/+bug/1969592 - [OVN] Frequent DB leader changes causes 'VIF creation failed' on nova side - New - Unassigned Invalid --------- - https://bugs.launchpad.net/neutron/+bug/1969354 - ovn-controller don't update new flows - Invalid - but reporter updated with additional info - Unassigned Thanks, Oleg

1 0

[ironic][ptg] Zed PTG Summary
by Iury Gregory 25 Apr '22

25 Apr '22

Hello Ironicers! Sorry for the delay to provide a summary about our PTG =) First of all, thank you to all contributors that took some time to join our sessions! During the sessions we had a peak of 13 attendees on the last three days. Day1 We only had two topics: Feedback about the Yoga Cycle and What should we do about specs. During the of we did a retrospective about the Yoga Cycle, we discussed the good and bad things that happened during the cycle and how we can make things better. In the discussion about what we should do about specs we come up with some ideas to improve our process when we think a spec should be required. Day2: On this day most of the discussions were around topics that can be managing machines. How we can decrease the cost of Data Centers that needs to keep all their machine on even if they are not active or taking minimal load, we would provide a way to power tuning nodes that are already deployed (in the ironic perspective this is a way to reconfigure a node that is already active), we also talked about turning down power usage if we are able to identify that IPA is idle. The custom deploy timeout topic had no strong objections, since we have a single configuration that handles the timeout for all steps we think we can improve this, we still need to define some details related to the implementation after we have the RFE. We discussed how we can generate the inspector.ipxe configuration if we notice some changes in the configuration of the deployment. Day3: We started this day looking at the survey results, this gave us some ideas on possible areas we should improve. The ironic safeguard topic was focusing on two main things: queuing (limit the max number of concurrent cleaning operations) and data disk protection (only clean the root disk (or give a list of skip-disks/disks-to-clean). The community decided that this seems like a good idea and we defined some of the possible paths forwards related to how it could be implemented. The redfish gateway and related ideas topic brought an interesting idea to have an ironic driver that can execute a "script" that is required for their HW to start working properly, there is a recording from the first meeting that can provide more details =). The per-node clean steps topic had no objections, we think this will improve the operators experience for scenarios where they would need specific steps for running on a node that has different disk configuration. Day4: Most of the topics on this day were focused on networking. We discussed the status of OVN DHCP support and how we will move forward on our side to make things work after Neutron and OVN have all the necessary bits in place. During the next topic we talked about adding device configuration capabilities for networking-baremetal since in multi-tenant BMaaS there is a need to configure the ToR network devices (Access/Edge Switches) and many vendors have abandoned their ML2 mechanism plug-ins to support this, so now we are looking to add support for new mechanisms that have more features that could improve the operators experience. We focused on discussing the pros/cons about Netconf and Yang but also other alternatives solutions. The other topic we discussed were: - netboot deprecation: we discussed how we should move forward with some of our testing for partition images + UEFI. - Bluefield DPU: not much discussion since we didn't have many folks interested on the topic. - Anaconda driver: we talked about how we can get a CI for testing the driver. You can find more information about the topics and the discussions in our etherpad: https://etherpad.opendev.org/p/ironic-zed-ptg -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 0

[largescale-sig] Skipping meeting this week
by Thierry Carrez 25 Apr '22

25 Apr '22

Hi everyone, Due to a shortage of participants and meeting chairs, we will skip the meeting planned this week for the Large Scale SIG. Our next meeting will be May 11th at 15UTC in #openstack-operators. You can add topics to discuss to our agenda etherpad: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez (ttx)

1 0