August 2022 - openstack-discuss - lists.openstack.org

resize or migrate problem
by fereshteh loghmani 03 Aug '22

03 Aug '22

hello I use OpenStack and I create some VMs in different compute in one region. when I resize the VM. if the compute doesn't have enough space, automatically the vm will be migrated to another compute. but my problem is here that when it migrated, the _base file doesn't migrate and remains in the first compute that it doesn't have enough space. because of this, the VM appears with an error status in OpenStack. if I move the _base from first compute to final compute and reboot the server this problem has been solved. so i need to not transfer _base manually and if it migrated to another compute the disk and _base transfer with each other. could you please help me to solve this problem? thanks in advance

2 3

[cinder] Bug deputy report for week of 08-03-2022
by Sofia Enriquez 03 Aug '22

03 Aug '22

This is a bug report from 07-27-2022 to 08-03-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1983237 "Cannot retype volume of lvm to volume of fujitsu." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1983287 "Infinidat Cinder driver fails to backup attached volume." Fix proposed to master. Cheers, Sofia -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[security-sig] Any interest in getting together at the PTG?
by Jeremy Stanley 02 Aug '22

02 Aug '22

I was going to bring this up during the monthly meeting, but since I'll be unavailable the next best solution is to raise it here... Are any of the Security SIG participants planning or at least hoping to be in Columbus for the PTG this October? And if so, is there any interest in carving out some spacetime in the schedule for security discussions? We still have another week to decide, but I'm happy to put in a request for us if anyone wants that. -- Jeremy Stanley

2 1

Reminder! PTG October 2022 Team Signup Deadline
by Kendall Nelson 02 Aug '22

02 Aug '22

Hello Everyone, Don't forget to sign your team up for the next Project Teams Gathering (PTG), which will be held in Columbus, OH from Monday, October 17 to Thursday, October 20th, 2022! If you haven't already done so and your team is interested in participating, please complete the survey[1] by August 12th, 2022 at 7:00 UTC. Then make sure to register[2] for the PTG before prices go up on August 15th! Also, please book in the official hotel block for a discounted rate[3]. Booking in the PTG hotel block helps us keep costs low for all attendees, so please encourage your teams to book here. Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2022_ptg_team_signup [2] PTG Registration: https://openinfra-ptg.eventbrite.com [3] Hotel Block: https://www.hyatt.com/en-US/group-booking/CMHRC/G-L0RT

1 0

[kolla][ops] Anyone using the collectd and/or telegraf?
by Radosław Piliszek 02 Aug '22

02 Aug '22

Hi Kolla-flavoured OpenStackers, Any of you using the collectd and/or telegraf with Kolla Ansible? The core team is looking to deprecate their support as it's not tested and collectd is now gone from Ubuntu Jammy. Please reply to this mail. Cheers, Radek -yoctozepto

2 2

[ceilometer][gnocchi][tacker] Internal Server Error in devstack for Zuul gate job
by ueha.ayumu＠fujitsu.com 02 Aug '22

02 Aug '22

Hi telemetry team, I’m Ueha from Tacker team, The Zuul gate job of Tacker failed with the following error. Do you know the solution? The gate job has failed, so we would appreciate it if you could deal it with high priority. Thanks! for reference, the same error occurring in the ceilometer patch. (https://review.opendev.org/c/openstack/ceilometer/+/851338 ‘s telemetry-dsvm-integration-centos-9s job) ------------------ ++ /opt/stack/ceilometer/devstack/plugin.sh:start_ceilometer:322 : /usr/local/bin/ceilometer-upgrade 2022-07-29 05:20:42.125 61523 DEBUG ceilometer.cmd.storage [-] Upgrading Gnocchi resource types upgrade /opt/stack/ceilometer/ceilometer/cmd/storage.py:42 2022-07-29 05:20:42.228 61523 CRITICAL ceilometer [-] Unhandled error: gnocchiclient.exceptions.ClientException: Internal Server Error (HTTP 500) 2022-07-29 05:20:42.228 61523 ERROR ceilometer Traceback (most recent call last): 2022-07-29 05:20:42.228 61523 ERROR ceilometer File "/usr/local/bin/ceilometer-upgrade", line 10, in <module> 2022-07-29 05:20:42.228 61523 ERROR ceilometer sys.exit(upgrade()) 2022-07-29 05:20:42.228 61523 ERROR ceilometer File "/opt/stack/ceilometer/ceilometer/cmd/storage.py", line 49, in upgrade 2022-07-29 05:20:42.228 61523 ERROR ceilometer tenacity.Retrying( ......... omit ......... 2022-07-29 05:20:42.228 61523 ERROR ceilometer File "/usr/local/lib/python3.8/dist-packages/gnocchiclient/client.py", line 52, in request 2022-07-29 05:20:42.228 61523 ERROR ceilometer raise exceptions.from_response(resp, method) 2022-07-29 05:20:42.228 61523 ERROR ceilometer gnocchiclient.exceptions.ClientException: Internal Server Error (HTTP 500) 2022-07-29 05:20:42.228 61523 ERROR ceilometer ------------------ Full log: https://zuul.opendev.org/t/openstack/build/71262e66ecf34827a8a3435657aa9b3f Best Regards, Ueha

4 4

[horizon][security-sig][tc] XStatic and JS dependencies
by Jeremy Stanley 02 Aug '22

02 Aug '22

We discussed this at the PTG, and sending out a recap has been on my to do list for a few months. Sorry about the delay! The tl;dr here is that OpenStack is effectively serving as the upstream distributor for (often vulnerable versions of) JavaScript software we didn't make, and downstream consumers like GNU/Linux distributions are then directly repackaging our copies of these things, and assuming we've taken care of any security vulnerabilities for them. In the early days, we needed a way to make it possible for Horizon to consume JavaScript libraries installed on systems, typically supplied by Linux distros via system level package management. XStatic was and still is a good framework for this, providing a means of bundling up metadata which can be adjusted in deployments to tie in local copies of JS libs so that Horizon can find them, and also allowing us to conveniently use the same sorts of mappings for upstream testing as well. The original idea was that we were shipping XStatic metadata packages, and distributions would take care of supplying the actual JS bits since that's not our specialty as a community. To make our own testing easier, we embedded copies of the actual JS within our XStatic packages, which is where all of this started going horribly wrong. The rationale at the time was that distro package maintainers would know to devendor (unbundle and replace) the JS inside our XStatic packages, substituting standard ones from their distribution. What has happened instead, likely due to a confluence of convenience and lack of clear communication on our part, is that the distros took the entirety of these XStatic packages and redistributed them, JS and all. Why is that bad? Well, our approach to Python dependencies is that we freeze the versions we use at the time of our coordinated release, on the assumption that distros backport any relevant security fixes for them. That's generally okay because we're not shipping those dependencies ourselves, someone else does and takes care of fixing and communicating vulnerabilities in them. For many of the XStatic packages Horizon relies on, however, distros are treating us as the upstream supplier of that software, including the JS bundled inside it. We don't (and really can't reliably) track security vulnerabilities in our dependencies, and JS is no exception in this regard. Unfortunately, when it comes to the outdated versions of JS libs we're redistributing inside those packages, many distros assume we are doing exactly that. Worse, it's not just the Linux distros, but even our own deployment projects following the same pattern. How can we address this? The first and fastest thing we should do is to start clearly communicating that we make no effort to track or fix vulnerabilities for JS inside our XStatic packages. Readme files in all of them should get a big disclaimer added, as visible as possible, that the included "convenience" copies of JS libs in them are not for production use and should be considered insecure, to be replaced at deployment time with actual upstream copies instead (this will be noticed not just when browsing our source code, but for any subsequent releases on PyPI too). Also update any places in our documentation where XStatic packages are mentioned to point this situation out. Ideally, we should reach out to distros and deployment projects we know are installing our copies of the embedded JS libs to make sure they're aware of this problem too. In the long term, we really need to gut the JS content from the source trees of our XStatic packages and make our test jobs use something like NPM or Yarn to fetch the relevant versions at deployment time, installing them into the expected locations pointed to by the XStatic metadata. This will make it more obvious that we're not taking responsibility for the security of those libraries, since we're no longer directly supplying them. I've only got the loosest understanding of how XStatic integration works, and not much familiarity with Horizon or its testing, so am relying on Horizon's contributors to weigh in on whether this course of action is sensible and, more importantly, achievable. -- Jeremy Stanley

1 1

[TripleO], Undercloud deployment is failing with with the NTP error
by Veronika Fisarova 02 Aug '22

02 Aug '22

Good day everyone, I was trying to deploy TripleO via tripleo-quickstart following this guide <https://docs.openstack.org/tripleo-quickstart/latest/getting-started.html#>. Working environment has satisfactory requirements following specifications in the guide. Python 3.6.8. is installed. The following deployment script was used: bash quickstart.sh --tags all -R wallaby -X --teardown all -v $VIRTHOST and the deployment is failing with the following error: 2022-08-02 13:05:13,693 p=21797 u=root n=ansible | 2022-08-02 13:05:13.692871 | 008acbda-7e58-575b-6e97-00000000078a | TASK | Ensure system is NTP time synced 2022-08-02 13:10:04,147 p=21797 u=root n=ansible | 2022-08-02 13:10:04.146932 | 008acbda-7e58-575b-6e97-00000000078a | FATAL | Ensure system is NTP time synced | undercloud | error={"changed": true, "cmd": ["chronyc", "waitsync", "30"], "delta": "0:04:50.254002", "end": "2022-08-02 13:10:04.121815", "msg": "non-zero return code", "rc": 1, "start": "2022-08-02 13:05:13.867813", "stderr": "", "stderr_lines": [], "stdout": "try: 1, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 2, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 3, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 4, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 5, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 6, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 7, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 8, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 9, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 10, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 11, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 12, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 13, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 14, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 15, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 16, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 17, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 18, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 19, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 20, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 21, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 22, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 23, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 24, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 25, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 26, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 27, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 28, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 29, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 30, refid: 00000000, correction: 0.000000000, skew: 0.000", "stdout_lines": ["try: 1, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 2, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 3, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 4, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 5, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 6, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 7, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 8, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 9, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 10, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 11, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 12, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 13, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 14, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 15, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 16, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 17, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 18, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 19, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 20, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 21, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 22, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 23, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 24, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 25, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 26, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 27, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 28, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 29, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 30, refid: 00000000, correction: 0.000000000, skew: 0.000"]} 2022-08-02 13:10:04,178 p=21797 u=root n=ansible | PLAY RECAP ********************************************************************* 2022-08-02 13:10:04,178 p=21797 u=root n=ansible | localhost : ok=1 changed=0 unreachable=0 failed=0 skipped=2 rescued=0 ignored=0 2022-08-02 13:10:04,179 p=21797 u=root n=ansible | undercloud : ok=209 changed=110 unreachable=0 failed=1 skipped=50 rescued=0 ignored=2 For more information, please see the copy of the partially deployed undercloud here <https://paste.opendev.org/show/bxKvk87Y8ZH1RdboQaa3/> and here <https://paste.opendev.org/show/banD6k2R1gReYvBjN8bx/>. As far as I know, I can SSH to the deployed undercloud, but I cannot ensure if the undercloud is working properly and how many functions are missing. If you would need any additional information, please email me or use the IRC nick: deydra Any help or suggestions appreciated. -- *Veronika Fisarova* Openstack Validation Framework - Intern Red Hat <http://www.redhat.com>

1 0

[security-sig] Cancelling our August meeting
by Jeremy Stanley 02 Aug '22

02 Aug '22

Apologies for the late notice, but I have travel for an appointment conflicting with our meeting and will be unable to chair it this month. If someone else wants to run the meeting please feel free, though we don't have any pressing agenda items so it's probably fine to skip. I'm also open to holding the meeting next week instead, if anybody is interested in rescheduling. Barring any ad hoc meetings in the interim, our next scheduled meeting is 15:00 UTC on Thursday, September 1. In the meantime, Security SIG folks can be found in the #openstack-security channel on OFTC or by prepending subjects to this ML with [security-sig] of course! -- Jeremy Stanley

1 0

Horizon dashboard query
by KK CHN 02 Aug '22

02 Aug '22

Hi everyone! I need a guide or advice or anything. I am administering a private cloud in openstack. As I am using the Horizon dashboard for the VM provisioning and administering activities. But the users are sending requests in mail and creating the VMs for them. can we make workflow automation for the request and approval and provisioning automatically in the Horizon dashboard on approval? Has anyone already done /have idea on these kinds of solutions for your openstack cloud ??. Is there some kind of documentation that could help me?. Any guidance much appreciated, where to start, what to refer and which tool/programming language best if I need to code from scratch. thanks in advance. Krish

5 6