July 2021 - openstack-discuss - lists.openstack.org

[powervmstackers][multi-arch-sig][stable] periodic-stable errors
by Előd Illés 30 Jul '21

30 Jul '21

Hi PowerVMStackers and Multi-Arch SIG members, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've collected the recent failures with examples that are failing constantly. Please take a look at them and try to fix them wherever it is possible. Since the old branches seem quite abandoned in some cases, they might need maintainers to step up to keep those gates healthy, or in case there are no maintainers, then it might worth to think of transitioning those broken old branches to End of Life. :/ And the list: * ocata is mostly End of Life -- (also there is a patch to EOL ocata of the *-powervm: https://review.opendev.org/c/openstack/releases/+/801123 ) ceilometer-powervm: ocata - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/151e90c3c3eb48779759f469d76f02d7 nova-powervm: ocata - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/535ffa6750c74ab7a886f6fb3838ff4f * unit tests are broken: nova-powervm: pike - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/27bd093f615341e7a5563e3b9ea86f31 * dependency version conflict: nova-powervm: train - openstack-tox-py36 -- https://zuul.opendev.org/t/openstack/build/f9afc55de6dc452cbc88d98c837ab58f nova-powervm: train - openstack-tox-py37 -- https://zuul.opendev.org/t/openstack/build/0ea69ad9be8c4a269613573fa5014fe4 [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

1 0

[telemetry][stable] periodic-stable errors
by Előd Illés 30 Jul '21

30 Jul '21

Hi Telemetry Team, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've collected the recent failures with examples that are failing constantly. Please take a look at them and try to fix them wherever it is possible. Since the old branches seem quite abandoned in some cases, they might need maintainers to step up to keep those gates healthy, or in case there are no maintainers, then it might worth to think of transitioning those broken old branches to End of Life. :/ And the list (with possible root causes): * tenacity should be constrained for py27: ceilometer: pike - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/4bcb7e71d507465ea799cd289e6cc920 ceilometer: queens - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/583d52b6096745ddbb18da23cf79fa75 ceilometer: rocky - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/03279061fddd4d14819c04feda3a1806 * kombu version should be constrained for py27: ceilometer: stein - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/219139b1814b4fd591ee7dc199f2e3da [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

1 0

[oslo][stable] periodic-stable errors
by Előd Illés 30 Jul '21

30 Jul '21

1 0

[centos][kolla-ansible][wallaby][vpnaas] I need Help
by Franck VEDEL 30 Jul '21

30 Jul '21

Hello. I try one last time to get some help, answers to my questions because I have been trying for 2 weeks to get the vpnaas service to work under Wallaby, without success. Still, I have no problem under Victoria with vpnaas. However, on my last installation which must work in September (to be used by students), without my understanding why, the horizon container of my centos (rocky) / kolla-ansible / victoria installation does not want to launch and I do not have no logs. So, can't use Victoria. I am trying Wallaby, everything works except vpnaas. My questions: how to get the logs of this hoorizon container which does not start (restart every 20 seconds)? how to know if it is a bug in wallaby with vpnaas? Really thank you if anyone can help me move forward. Franck

5 22

RE: [ops][nova][victoria] Unable to Migrate: Host filter ignoring hosts
by DHilsbos＠performair.com 29 Jul '21

29 Jul '21

All; Thank you for reading my previous email, despite its poor Subject. I have attached a subset of the Nova Scheduler log, with debugging enabled. I have added line numbers to the beginning, in order to facilitate referencing. At line 18 it appears to select the requested server for the migration, but then at line 38, it rejects it. Am I missing something here? Is it unable to assign the resources through placement? Dominic L. Hilsbos, MBA Vice President – Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com -----Original Message----- From: melanie witt [mailto:melwittt@gmail.com] Sent: Wednesday, July 28, 2021 1:24 PM To: Dominic Hilsbos; openstack-discuss(a)lists.openstack.org Subject: Re: [ops][nova] On Wed, 28 Jul 2021, 20:10 +0000, <DHilsbos(a)performair.com> wrote: > All; > > I'm having a problem, though I'm not certain of the full scope. > > The most obvious issue is that I can't live migrate instances. The server I want to send the instance to gets filtered out, though I don't see any logs that tell me why it's being filtered out. > > It might be related that all of my new instances seems to land on a single host. > > An pointers on where to look for logs for Host Filters? You'll want to set [DEFAULT]debug = True in the nova.conf for your nova-scheduler service and restart or HUP the service. And then the logging per scheduler filter (each one will show the starting and ending number of hosts) will be included at DEBUG log level in the nova-scheduler log. -melwitt

3 5

[OSSA-2021-002] Nova: Open Redirect in noVNC proxy (CVE-2021-3654)
by Jeremy Stanley 29 Jul '21

29 Jul '21

=========================================== OSSA-2021-002: Open Redirect in noVNC proxy =========================================== :Date: July 29, 2021 :CVE: CVE-2021-3654 Affects ~~~~~~~ - Nova: <21.2.3, >=22.0.0 <22.2.3, >=23.0.0 <23.0.2 Description ~~~~~~~~~~~ Swe Aung, Shahaan Ayyub, and Salman Khan with the Monash University Cyber Security team reported a vulnerability affecting Nova's noVNC proxying implementation which exposed access to a well-known redirect behavior in the Python standard library's http.server.SimpleHTTPRequestHandler and thus noVNC's WebSockifyRequestHandler which uses it. By convincing a user to follow a specially-crafted novncproxy URL, the user could be redirected to an unrelated site under control of the attacker in an attempt to convince them to divulge credentials or other sensitive data. All Nova deployments with novncproxy enabled are affected. Patches ~~~~~~~ - https://review.opendev.org/791807 (Train) - https://review.opendev.org/791806 (Ussuri) - https://review.opendev.org/791805 (Victoria) - https://review.opendev.org/791577 (Wallaby) - https://review.opendev.org/791297 (Xena) Credits ~~~~~~~ - Swe Aung from Monash University Cyber Security team (CVE-2021-3654) - Shahaan Ayyub from Monash University Cyber Security team (CVE-2021-3654) - Salman Khan from Monash University Cyber Security team (CVE-2021-3654) References ~~~~~~~~~~ - https://launchpad.net/bugs/1927677 - https://bugs.python.org/issue32084 - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3654 Notes ~~~~~ - The stable/train branch is under extended maintenance and will receive no new point releases, but a patch for it is provided as a courtesy. -- Jeremy Stanley

1 0

[cinder] No Cinder Bug Meeting on 4 August
by Sofia Enriquez 29 Jul '21

29 Jul '21

I'll send the email report as usual. Please join the Cinder Xena R-9 virtual that day 1400-1600 UTC. Cheers, Sofia -- L. 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

[openstack-nova] Attached volume is not available in the VM
by Aleksander Wojtal 29 Jul '21

29 Jul '21

Hello, During our testing we perform reboot of compute during volume attached task. Result is as follows. Volume is marked as attached to VM (also in DB) ceeinfra@lcm1:~> openstack volume list +--------------------------------------+-----------------------------------------------------------------------------+-----------+------+--------------------------------------------------------------------------------------------------------------+ | ID | Name | Status | Size | Attached to | +--------------------------------------+-----------------------------------------------------------------------------+-----------+------+--------------------------------------------------------------------------------------------------------------+ | c52d406c-5587-445d-9da1-436ffbbe3541 | vol_neXt-488 | available | 10 | | | f3e45efc-35eb-4f95-8e71-f50b5cb69028 | RebootOfComputeHostWhilePerformingVolumeOperations-Volume-0618_19_45_12_669 | in-use | 20 | Attached to neXt-377_VM1--RebootOfComputeHostWhilePerformingVolumeOperations--0618_19_44_16_775 on /dev/vdb | | 1bd81392-e2c9-4725-93c8-baa484924f21 | vol_neXt-488 | available | 10 | | | 919db17c-0729-409c-bf59-74539edcea47 | vol_neXt-488 | available | 10 | | +--------------------------------------+-----------------------------------------------------------------------------+-----------+------+--------------------------------------------------------------------------------------------------------------+ >From VM perspective too. ceeinfra@lcm1:~> openstack server show neXt-377_VM1--RebootOfComputeHostWhilePerformingVolumeOperations--0618_19_44_16_775 +-------------------------------------+-------------------------------------------------------------------------------------+ | Field | Value | +-------------------------------------+-------------------------------------------------------------------------------------+ | OS-DCF:diskConfig | MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | compute-0-11.k2.ericsson.se | | OS-EXT-SRV-ATTR:hypervisor_hostname | compute-0-11.k2.ericsson.se | | OS-EXT-SRV-ATTR:instance_name | instance-00001edc | | OS-EXT-STS:power_state | Running | | OS-EXT-STS:task_state | None | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2021-06-18T14:14:58.000000 | | OS-SRV-USG:terminated_at | None | | accessIPv4 | | | accessIPv6 | | | addresses | NovaController-Network-0618_19_44_16_852=10.0.0.5 | | config_drive | True | | created | 2021-06-18T14:14:19Z | | flavor | m1.small (2) | | hostId | 5078bfd4fabd8b2e7c9f4554b3ac08d536ceebb5f393db4d38c8ff60 | | id | 95ed49ed-b3f8-46ae-80a0-544b939c50b7 | | image | JCAT_Common_CirrOS_i386 (b71f3fbd-59f1-4c29-a296-5065fe0406f7) | | key_name | None | | name | neXt-377_VM1--RebootOfComputeHostWhilePerformingVolumeOperations--0618_19_44_16_775 | | progress | 0 | | project_id | b63725c8ebaf43ebabbed497f41eb71c | | properties | ha-policy='managed-on-host' | | scheduler_hints | {} | | security_groups | name='default' | | status | ACTIVE | | updated | 2021-06-18T14:22:07Z | | user_id | f490f07b813748698e56ca7641d46a72 | | volumes_attached | id='f3e45efc-35eb-4f95-8e71-f50b5cb69028' | +-------------------------------------+-------------------------------------------------------------------------------------+ >From Libvirt perspective, volume is not attached to VM compute-0-11:/var/log # virsh dumpxml instance-00001edc <domain type='kvm' id='1'> <name>instance-00001edc</name> <uuid>95ed49ed-b3f8-46ae-80a0-544b939c50b7</uuid> (...) <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='directsync'/> <source file='/var/lib/nova/instances/95ed49ed-b3f8-46ae-80a0-544b939c50b7/disk' index='2'/> <backingStore type='file' index='3'> <format type='raw'/> <source file='/var/lib/nova/instances/_base/af82cd8216adb002916bb9e422a3fbb637022ec6'/> <backingStore/> </backingStore> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw' cache='directsync'/> <source file='/var/lib/nova/instances/95ed49ed-b3f8-46ae-80a0-544b939c50b7/disk.config' index='1'/> <backingStore/> <target dev='hdd' bus='ide'/> <readonly/> <alias name='ide0-1-1'/> <address type='drive' controller='0' bus='1' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='piix3-uhci'> (...) </domain> System does not provide any indication of the problem. There should be some kind of indication to user that volume attachment was not completed. Pozdrawiam / Best regards, Aleksander Wojtal, Junior Software Engineer TietoEVRY BU Telco Cloud Infra & Applications email aleksander.wojtal(a)tietoevry.com al. Piastów 30, 71-064 Szczecin, tietoevry.com [cid:image001.png@01D77EE0.7C2AE900] Please note: The information contained in this message may be legally privileged, confidential and protected from disclosure. If you received this in error, please notify the sender immediately and delete the message from your computer. Thank you.

3 6

[TripleO] next irc meeting Tuesday 03 August @ 1400 UTC in OFTC #tripleo
by Marios Andreou 29 Jul '21

29 Jul '21

Reminder the next TripleO irc meeting is this coming Tuesday agenda: https://wiki.openstack.org/wiki/Meetings/TripleO one-off items: https://etherpad.opendev.org/p/tripleo-meeting-items (feel free to add any tripleo status/ongoing work etc to the etherpad). Our last meeting was on Jul 20 - you can find logs @ https://meetings.opendev.org/meetings/tripleo/2021/tripleo.2021-07-20-14.00… Hope you can make it on Tuesday, regards, marios

1 0

[sdk] keystone group members list
by Valéry Tschopp 29 Jul '21

29 Jul '21

Hi all, With the openstacksdk, how can list the members of a Keystone group? The Keystone API exists https://docs.openstack.org/api-ref/identity/v3/?expanded=list-users-in-grou… but I didn't find the corresponding SDK functions... Thanks in advance Cheers, Valery -- SWITCH Valéry Tschopp, Software Engineer Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland Email: valery.tschopp(a)switch.ch Phone: +41 44 268 1544 https://www.switch.ch/

1 0

[kolla][keystone][openstack-ansible][deploy][sdk] enforcing scope in Kolla-Ansible deployment
by James Kirsch 29 Jul '21

29 Jul '21

I'm working on adding the option to enable enforce_scope in keystone during Kolla-Ansible deployment. I've revived this transaction to complete this work: https://review.opendev.org/c/openstack/kolla-ansible/+/692179 As part of that effort, I would like to also enable enforce_new_defaults in keystone. Deployment currently fails because the nova keystone user roles created during Kolla-Ansible deployment requires system scope. I can currently get around this using python-openstack: openstack role add --system all --user d7512be612454eff8a7f5bf5476b1531 admin Kolla-ansible relies on the OpenStack Ansible modules to create users and roles for deployment. Looking around the repositories, it does not appear that the openstack ansible module nor the openstacksdk supports granting system scope to a user role. Please let me know if this is not the case or if it is in current development. Otherwise, I could use guidance on what the next steps I could take or who I should talk to so I can move this forward. Thanks, James my awesome background music: http://www.generalfuzz.net about me: http://www.headphonejames.com

3 2

[kolla] Operator pain points
by Mark Goddard 29 Jul '21

29 Jul '21

Hi, The TC is looking at community goals for the Yoga release cycle, and has proposed resolving some operator pain points [1]. These pain points are naturally project-specific, and the first step is collecting some. They are looking for 1-2 points per project, but this is an interesting feedback exercise for us, so don't hold back. Please add any significant operator pain points you have for Kolla (or other projects) to the Etherpad [2]. Thanks, Mark [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023659.html [2] https://etherpad.opendev.org/p/pain-point-elimination

2 1

[Openstack][kolla][wallaby] swift installation
by Ignazio Cassano 28 Jul '21

28 Jul '21

Hello all, I want install swift but I do not have disks on controllers and on compute nodes. Is it possible to inventory a group of servers other than controllers or computes to install swift? In other words, I would like to insert in multinode inventory a new group of servers with disks for reinstalling swift. Thanks. Ignazio

2 2

[all][tc] Technical Committee next weekly meeting on July 29th at 1500 UTC
by Ghanshyam Mann 28 Jul '21

28 Jul '21

Hello Everyone, Technical Committee's next weekly meeting is scheduled for July 29th at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, June 28th, at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[tc][cinder] early removal of 'enable_v3_api' option
by Brian Rosmaita 28 Jul '21

28 Jul '21

Hello TC members, Cinder has asserted the 'assert:follows-standard-deprecation' tag. This cycle, the long-deprecated Block Storage API v2 has been removed [0], at which time the 'enable_v2_api' option was also removed (which was appropriate since the option had been deprecated since Mitaka [1]). It turns out, however, that the corresponding 'enable_v3_api' option had never been deprecated. It has been deprecated in the current development branch by [0], but the team would like to know whether it is permissible to simply remove it in Xena without deprecating it for the following reasons: - The option was introduced by [1] in Mitaka. It has always had the default value: True. - In the Xena release, if the option is False, you can deploy the Block Storage API, but the only reachable resource from the endpoint is '/versions', which returns an empty list of available versions. This doesn't seem to be something that anyone would do on purpose. - If someone wants to deploy only the Block Storage API v2, this cannot be done in Xena by setting 'enable_v3_api' to False. So for that purpose, this option is already effectively a no-op in Xena. In short, we could leave the 'enable_v3_api' option as deprecated in the Xena release, but we can't imagine any circumstances under which someone would intentionally use it in its non-default value, so it seems pointless to keep it around ... except to satisfy the 'assert:follows-standard-deprecation' tag. To be clear, the Cinder team has no intention of violating or removing the 'assert:follows-standard-deprecation' tag. The point of this email is to ask the TC whether it would be permissible to simply remove the 'enable_v3_api' option in Xena (as opposed to deprecating the option in Xena and then waiting until Yoga development to remove it). Thanks for thinking about this! [0] https://review.opendev.org/c/openstack/cinder/+/792299 [1] https://review.opendev.org/c/openstack/cinder/+/224910

2 1

[ops][nova]
by DHilsbos＠performair.com 28 Jul '21

28 Jul '21

All; I'm having a problem, though I'm not certain of the full scope. The most obvious issue is that I can't live migrate instances. The server I want to send the instance to gets filtered out, though I don't see any logs that tell me why it's being filtered out. It might be related that all of my new instances seems to land on a single host. An pointers on where to look for logs for Host Filters? Thank you, Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

3 2

[nova] Early migrate error - pain point?
by DHilsbos＠performair.com 28 Jul '21

28 Jul '21

All; Yesterday I ran into an issue where a live migration errored before starting the migration itself (libvirt version incompatibility). This left the instance in an error state, even though it continued to run normally on the original host. Has anyone else run into this? Could this be a candidate for the current pain point hunt? Thank you, Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

2 4

[cinder] xena R-9 virtual mid-cycle on 4 August
by Brian Rosmaita 28 Jul '21

28 Jul '21

As mentioned at today's weekly meeting, the Cinder Xena R-9 virtual mid-cycle will be held: DATE: Wednesday 4 August 2021 TIME: 1400-1600 UTC LOCATION: https://bluejeans.com/3228528973 The meeting will be recorded. Please add topics to the mid-cycle etherpad: https://etherpad.opendev.org/p/cinder-xena-mid-cycles cheers, brian

1 0

[cinder] Bug deputy report for week of 2021-28-07
by Sofia Enriquez 28 Jul '21

28 Jul '21

Hello, This is a bug report from 2021-22-07 to 2021-28-07. You're welcome to join the Cinder Bug Meeting today. Weekly on Wednesday at 1500 UTC on #openstack-cinder Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/cinder/+bug/1937086 "extra_capabilities not added to pool stats". Assigned to Walt Boring. Medium - https://bugs.launchpad.net/cinder/+bug/1938196 "retype available volume fails with non root file access". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1938240 "when the backend does not support consistency groups, creating generic groups is successful". Unassigned. - https://bugs.launchpad.net/python-cinderclient/+bug/1938203 "misleading message about api version negotiation". Unassigned. Low - https://bugs.launchpad.net/cinder/+bug/1938254 "The cinder-volume service appears to run but does not respond to requests". Unassigned. Incomplete - https://bugs.launchpad.net/cinder/+bug/1937890 "when lack of resources backup status not update". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1938146 "Disabled NFS driver snapshots still appear in Error state". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1938256 "Can't delete the consistency group, which this group backend does not support .'' Unassigned. Cheers -- L. 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

Help : mount LVM issue
by KK CHN 28 Jul '21

28 Jul '21

List, I am in the process of uploading OS and data LVM disk image from ovirt(KVM) files fo our OpenStack Ussuri setup with KVM and glance. I am able to upload the disk ( qcow2 images and profile the VM image). But I could not able to get the logical volume visible to the populated VM. Here the data volume is LVM partition as another disk image handed over to us by our service provider. here the steps I followed to get the LVM partition (/dev/vdc2) in question to get visible to our VM without success. Kindly help to solve this issue. ################################################## [root@ma-app ~]# fdisk -l Disk /dev/vda: 64.4 GB, 64424509440 bytes, 125829120 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x0009e4d7 Device Boot Start End Blocks Id System /dev/vda1 * 2048 125829086 62913519+ 83 Linux Disk /dev/vdb: 10.7 GB, 10737418240 bytes, 20971520 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/vdc: 53.7 GB, 53687091200 bytes, 104857600 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x000ac064 Device Boot Start End Blocks Id System /dev/vdc1 * 2048 2099199 1048576 83 Linux /dev/vdc2 2099200 104857599 51379200 8e Linux LVM [root@ma-app ~]# vgs VG #PV #LV #SN Attr VSize VFree rhel 1 2 0 wz--n- <49.00g 0 [root@ma-app ~]# vgs VG #PV #LV #SN Attr VSize VFree rhel 1 2 0 wz--n- <49.00g 0 [root@ma-app ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda1 59G 1.5G 56G 3% / devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 3.9G 8.5M 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 783M 0 783M 0% /run/user/0 [root@ma-app ~]# vgs VG #PV #LV #SN Attr VSize VFree rhel 1 2 0 wz--n- <49.00g 0 [root@ma-app ~]# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root rhel -wi------- <44.00g swap rhel -wi------- 5.00g [root@ma-app ~]# vgs VG #PV #LV #SN Attr VSize VFree rhel 1 2 0 wz--n- <49.00g 0 [root@ma-app ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda1 59G 1.5G 56G 3% / devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 3.9G 8.5M 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 783M 0 783M 0% /run/user/0 [root@ma-app ~]# lvdisplay --- Logical volume --- LV Path /dev/rhel/swap LV Name swap VG Name rhel LV UUID Q2X9BK-7VXr-g9BB-JA5v-K7yR-yRBf-G61vZV LV Write Access read/write LV Creation host, time localhost, 2018-04-19 12:01:04 -0400 LV Status NOT available LV Size 5.00 GiB Current LE 1280 Segments 1 Allocation inherit Read ahead sectors auto --- Logical volume --- LV Path /dev/rhel/root LV Name root VG Name rhel LV UUID laUf04-Ecwg-OHDc-vr1s-SB85-yN8O-Us116d LV Write Access read/write LV Creation host, time localhost, 2018-04-19 12:01:05 -0400 LV Status NOT available LV Size <44.00 GiB Current LE 11263 Segments 1 Allocation inherit Read ahead sectors auto [root@ma-app ~]# lvscan inactive '/dev/rhel/swap' [5.00 GiB] inherit inactive '/dev/rhel/root' [<44.00 GiB] inherit [root@ma-app ~]# pvscan PV /dev/vdc2 VG rhel lvm2 [<49.00 GiB / 0 free] Total: 1 [<49.00 GiB] / in use: 1 [<49.00 GiB] / in no VG: 0 [0 ] [root@ma-app ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda1 59G 1.5G 56G 3% / devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 3.9G 8.5M 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 783M 0 783M 0% /run/user/0 [root@ma-app ~]# lvscan inactive '/dev/rhel/swap' [5.00 GiB] inherit inactive '/dev/rhel/root' [<44.00 GiB] inherit [root@ma-app ~]# vgchange -ay rhel 2 logical volume(s) in volume group "rhel" now active [root@ma-app ~]# lvscan ACTIVE '/dev/rhel/swap' [5.00 GiB] inherit ACTIVE '/dev/rhel/root' [<44.00 GiB] inherit [root@ma-app ~]# fdisk -l Disk /dev/vda: 64.4 GB, 64424509440 bytes, 125829120 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x0009e4d7 Device Boot Start End Blocks Id System /dev/vda1 * 2048 125829086 62913519+ 83 Linux Disk /dev/vdb: 10.7 GB, 10737418240 bytes, 20971520 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/vdc: 53.7 GB, 53687091200 bytes, 104857600 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x000ac064 Device Boot Start End Blocks Id System /dev/vdc1 * 2048 2099199 1048576 83 Linux /dev/vdc2 2099200 104857599 51379200 8e Linux LVM Disk /dev/mapper/rhel-swap: 5368 MB, 5368709120 bytes, 10485760 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/rhel-root: 47.2 GB, 47240445952 bytes, 92266496 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes [root@ma-app ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda1 59G 1.5G 56G 3% / devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 3.9G 8.5M 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 783M 0 783M 0% /run/user/0 [root@ma-app ~]# mount /dev/vdc1 /mnt [root@ma-app ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda1 59G 1.5G 56G 3% / devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 3.9G 8.5M 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 783M 0 783M 0% /run/user/0 /dev/vdc1 1014M 178M 836M 18% /mnt [root@ma-app ~]# umount /mnt [root@ma-app ~]# mount /dev/vdc2 /mnt mount: unknown filesystem type 'LVM2_member' [root@ma-app ~]# How to make this /dev/vdc2(LVM partiton) attached to the VM. ? Thank you, Kris

3 2

[packstack] Error while trying to read parameter CONFIG_SSH_KEY from user.
by Mauricio Tavares 28 Jul '21

28 Jul '21

Installing openstack in workernodes using packstack. It errors out saying it cannot read the CONFIG_SSH_KEY parameter: [root@the-headnode ~]# packstack -d worker-answerfile Welcome to the Packstack setup utility The installation log file is available at: /var/tmp/packstack/20210727-183254-mfc0n4iv/openstack-setup.log ERROR : Error while trying to read parameter CONFIG_SSH_KEY from user. Please check log file /var/tmp/packstack/20210727-183254-mfc0n4iv/openstack-setup.log for more information [root@the-headnode ~]# [root@the-headnode ~]# fgrep CONFIG_SSH_KEY worker-answerfile CONFIG_SSH_KEY=/root/.ssh/id_rsa.pub [root@the-headnode ~]# I looked at the answerfile, exposing the codes to see if there was some funny business, but did not see anything suspicious (excerpt below is from vi and shows the linefeed char as "$"): [general]$ $ # Path to a public key to install on servers. If a usable key has not$ # been installed on the remote servers, the user is prompted for a$ # password and this key is installed so the password will not be$ # required again.$ CONFIG_SSH_KEY=/root/.ssh/id_rsa.pub$ $ # Default password to be used everywhere (overridden by passwords set$ # for individual services or users).$ CONFIG_DEFAULT_PASSWORD=$ $ [...] Path to public key looks fine and there should not be an issue in seeing it: [root@ the-headnode ~]# ls -l /root/.ssh/ total 16 -r--------. 1 root root 3402 Jul 22 12:47 authorized_keys -r--------. 1 root root 2610 Jul 6 19:42 id_rsa -rw-r--r--. 1 root root 573 Jul 6 19:42 id_rsa.pub -rw-r--r-- 1 root root 855 Jul 27 18:30 known_hosts [root@ the-headnode ~]# So I do not know what I should be looking for. Here is the beginning of the log file: [root@the-headnode ~]$ cat /var/tmp/packstack/20210727-183254-mfc0n4iv/openstack-setup.log 2021-07-27 18:32:55::DEBUG::run_setup::483::root:: Groups: GLOBAL, VMWARE, UNSUPPORTED, SERVERPREPARE, RHEL, RHSM, RHSM_PROXY, SATELLITE, SATELLITE_PROXY, SSL, AMQP, AMQPSSL, AMQPAUTH, MARIADB, KEYSTONE, KEYSTONE_LDAP, GLANCE, CINDER, CINDERVOLUMECREATE, CINDERVOLUMENAME, CINDERVOLUMESIZE, CINDERGLUSTERMOUNTS, CINDERNFSMOUNTS, CINDERNETAPPMAIN, CINDERNETAPPONTAPISCSI, CINDERNETAPPNFS, CINDERNETAPPISCSI7MODE, CINDERNETAPP7MODEFC, CINDERNETAPPVSERVER, CINDERNETAPPESERIES, CINDERSOLIDFIRE, IRONIC, NOVA, NEUTRON, NEUTRON_ML2_PLUGIN, NEUTRON_LB_AGENT, NEUTRON_OVS_AGENT, NEUTRON_OVS_AGENT_TUNNEL, NEUTRON_OVS_AGENT_VXLAN, NEUTRON_OVN_AGENT, NEUTRON_OVN_AGENT_TUNNEL, MANILA, MANILANETAPP, MANILANETAPPMULTISVM, MANILANETAPPSINGLESVM, MANILAGENERIC, MANILANETWORK, MANILANETWORKSTANDALONE, MANILAGLUSTERNATIVE, MANILAGLUSTERNFS, NOVACLIENT, OSHORIZON, OSSSL, OSSWIFT, Heat, PROVISION_INIT, PROVISION_DEMO, PROVISION_TEMPEST, PROVISION_OVS_BRIDGE, GNOCCHI, CEILOMETER, REDIS, AODH, PANKO, Trove, SAHARA, MAGNUM, PUPPET, POSTSCRIPT 2021-07-27 18:32:55::DEBUG::run_setup::487::root:: going over group GLOBAL 2021-07-27 18:32:55::ERROR::run_setup::154::root:: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/packstack/installer/run_setup.py", line 117, in _getInputFromUser userInput = raw_input(message.read()) NameError: name 'raw_input' is not defined 2021-07-27 18:32:55::ERROR::run_setup::532::root:: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/packstack/installer/run_setup.py", line 117, in _getInputFromUser userInput = raw_input(message.read()) NameError: name 'raw_input' is not defined During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/packstack/installer/run_setup.py", line 500, in _handleInteractiveParams input_param(param) File "/usr/lib/python3.6/site-packages/packstack/installer/run_setup.py", line 181, in input_param _getInputFromUser(param) File "/usr/lib/python3.6/site-packages/packstack/installer/run_setup.py", line 155, in _getInputFromUser raise Exception(output_messages.ERR_EXP_READ_INPUT_PARAM % (param.CONF_NAME)) Exception: Error while trying to read parameter CONFIG_SSH_KEY from user.

1 0

[scientific-sig] IRC meeting today - Yoga release cycle operator pain points
by Stig Telfer 28 Jul '21

28 Jul '21

Hi All - In today’s IRC meeting (1100 UTC in channel #openstack-meeting, agenda: https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_July_28th_2021 <https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_July_28th_2021>) I’d like to go through the operator pain points proposed by SIG members so far (gathered here: https://etherpad.opendev.org/p/scientific-sig-yoga-pain-points <https://etherpad.opendev.org/p/scientific-sig-yoga-pain-points>) and pick some contenders for the TC’s effort. Everyone is welcome. Cheers, Stig

1 0

oVirt(KVM) Multiple Disk images ( lvm and vhdx disks) question
by KK CHN 27 Jul '21

27 Jul '21

Members, We have a set of VMs running in KVM environment. Both Windows and Linux OS VMs with separate data storage disks attached to it. We are planning to migrate/populate all these VMs to Our New OpenStack setup using Ussuri version with KVM virtualizer and glance storage. The current service provider provides three image files for each VMs in question. Both for Linux ( CentOS and Redhat) and WIndows machines they are providing us three disk images for each VM 1. one for OS image 2. second for boot 3. third for attached disk for data volumes The third comes as LVMs (Linux) and Vhdx (Windows)image files. *Is there a way to combine all three files from our vendor* as a single qcow2 image/or any other supported format in openstack so that we can directly populate a VM in our Open Stack setup ( ussuri, glance with KVM) using horizon dashboard. Is thi is possible? If not whats the best way to do this if you were me. kindly share your expertise and thoughts for a solution. Thanks Kris

2 1

OpenInfra Live - July 29 at 9am CT
by Ashlee Ferguson 27 Jul '21

27 Jul '21

Hi everyone, This week’s OpenInfra Live episode is brought to you by the Open Infrastructure Foundation. The Kubernetes steering committee and OpenStack technical committee meet regularly to talk about cross-community learnings and collaboration opportunities. Join members of both governance bodies to ask questions about integration, cross-project support and how you can stay updated on the latest developments. Have a question you’d like them to answer live? Drop your question on this Twitter thread <https://twitter.com/openstack/status/1419734323608051718?s=21>, or email ashlee(a)openinfra.dev. Episode: Kubernetes and OpenStack Working Together Date and time: July 29 at 9am CT (1400 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=G1vplawafw4 <https://www.youtube.com/watch?v=G1vplawafw4> LinkedIn: https://www.linkedin.com/feed/update/urn:li:ugcPost:6823993987699937280/ <https://www.linkedin.com/feed/update/urn:li:ugcPost:6823993987699937280/> Facebook: https://www.facebook.com/104139126308032/posts/4173780696010501/ <https://www.facebook.com/104139126308032/posts/4173780696010501/> WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Jay Bryant, OpenStack Technical Committee Bob Killen, Kubernetes Steering Committee Ghanshyam Mann, OpenStack Technical Committee Kendall Nelson, OpenStack Technical Committee Davanum Srinivas, Kubernetes Steering Committee Have an idea for a future episode? Share it now at ideas.openinfra.live <https://openinfrafoundation.formstack.com/forms/openinfralive>. Thanks, Ashlee

1 0

[nova] Improvements in migration tracking via API
by Radosław Piliszek 27 Jul '21

27 Jul '21

Dears, In Masakari we have a spec [0] to track the issued evacuations. It could greatly use having more insight into the migrations details that Nova saves in its database. It seems there are two issues here. One is quite cosmetic one, in that Nova API does not allow getting migrations by UUID but just ID [1] (while UUIDs seem to be called the future and the internal objects support them as well). I think this one can be easily tackled by making that endpoint [1] more flexible. The other issue is a more complex one, but still not introducing a great deal of change to Nova, and it is that the Nova API returns neither migration ID nor UUID when asked to evacuate an instance [2] (to be more general, it does not do it for migrations and live migrations either). It seems, otherwise, we would have to call the listing API [3] and find the latest entry there but this is possibly error-prone and wasting resources. [0] https://review.opendev.org/c/openstack/masakari-specs/+/789432 [1] https://docs.openstack.org/api-ref/compute/?expanded=show-migration-details… [2] https://docs.openstack.org/api-ref/compute/?expanded=evacuate-server-evacua… [3] https://docs.openstack.org/api-ref/compute/?expanded=id312-detail#id312-det… -yoctozepto

3 9