Tuesday, 2023-06-20

fricklerI'm a bit confused by the discussion earlier, xena-em isn't a branch anywhere, just a tag. and I see that tag for designate-dashboard just like for e.g. designate itself07:20
jrosserjamesdenton: there seems to be https://opendev.org/openstack/designate-dashboard/src/tag/xena-em and https://opendev.org/openstack/octavia-dashboard/src/tag/xena-em - have you got an example of what error occurred?08:21
fricklerjrosser: jamesdenton: actually the tag seems indeed to be missing on github, maybe some issue in our replication. I'll take this to #opendev. https://github.com/openstack/designate-dashboard/tags08:31
kleiniI discovered no issues upgrading to 24.6.1, which should be xena-em.08:35
fricklerkleini: do you use github as source or opendev?08:36
kleiniI use the default. I think, that is opendev.08:36
fricklerthen you wouldn't be affected by tags missing on github08:37
opendevreviewSimon Hensel proposed openstack/openstack-ansible-galera_server master: Add optional compression to mariabackup  https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/88618009:03
noonedeadpunkmornings09:17
noonedeadpunkthanks frickler for checking on that09:18
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-ceph_client stable/2023.1: Fix permissions for ceph cache directories  https://review.opendev.org/c/openstack/openstack-ansible-ceph_client/+/88647109:46
noonedeadpunkwe should also merge that fix for ceph client https://review.opendev.org/c/openstack/openstack-ansible-ceph_client/+/88639809:59
admin12i am on 26.1.0 and getting this  on a new build ..  https://paste.opendev.org/raw/bI9XZNtrrz8YbDj8DjYl/ 10:59
admin1i fixed my nick .. 11:00
admin1ceph is external 11:00
noonedeadpunkwell, at this stage it looks like you've got ceph repo misconfigured, though I'm not sure if you're supposed to have it for bare metal control plane host11:06
noonedeadpunkso it's obviously issue with gpg key for the ceph repo11:07
admin1hi noonedeadpunk .. one more .. based on your last advice, i have this .. https://gist.githubusercontent.com/a1git/cb8167e67e59670507d5831e3c106b9a/raw/6a43666eaa443f8b6df249094e8cf6360b93da4d/gistfile1.txt  , but this file alone did not created the necessary lxc container 11:10
noonedeadpunkadmin1: have you added `nfs_storage_hosts` definition into your openstack_user_config or conf.d? As now you should have a group in inventory, but you also need to assign hosts for the group11:12
noonedeadpunkor better say - where these containers should be created11:12
admin1i will give it a try 11:17
admin1added it .. run  --syntax-check and checked inventory list .. it did not add 11:20
admin1added like this: https://paste.opendev.org/raw/bQrMDlqqddtImO4gK1wq/11:20
noonedeadpunkthat should be enough ^11:25
noonedeadpunkadmin1: oh, well, you have `cinder_nfs_volumes_container` mentioned twice in env.d file11:35
noonedeadpunkmaybe that;s what causing the ignorance of it11:36
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-plugins master: Skip updating service password by default  https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/88645811:44
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-plugins master: Skip updating service password by default  https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/88645811:57
opendevreviewMerged openstack/openstack-ansible-ceph_client master: Fix retrievement keyrings from files  https://review.opendev.org/c/openstack/openstack-ansible-ceph_client/+/88639812:31
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-ceph_client stable/2023.1: Fix retrievement keyrings from files  https://review.opendev.org/c/openstack/openstack-ansible-ceph_client/+/88647712:32
anskiynoonedeadpunk: hey, any news from nova folks regarding https://bugs.launchpad.net/openstack-ansible/+bug/2023370 this thing? 12:48
noonedeadpunkI clean forgot to talk about that during PTG :(12:48
jamesdenton@jrosser @frickler Thanks for looking into it!12:49
noonedeadpunkLike was sooo many things to address that this one has slipped 12:49
anskiyno worries, should I open a bug in Nova? 12:50
noonedeadpunkThis patch can be just linked to nova as well12:50
noonedeadpunkthere's "also affects project" button12:51
noonedeadpunkBut I've asked them today in IRC, hoped to get some answer before doing that12:51
anskiynoonedeadpunk: ah, so, you're gonna link them whenever they'll answer you?12:57
noonedeadpunkwe're discussing right now in #openstack-nova fwiw :)12:59
NeilHanloni knew i needed more channels to be in ;) 12:59
fricklerjamesdenton: so can you confirm that you indeed use github as a source? is there a specific reason for doing so?13:11
jamesdentoni will double check both of those shortly13:11
anskiynoonedeadpunk: I have another question with this thing: https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/858271. I have some time to finish that (and as I saw, it was on PTG etherpad). What else needs to be done in here? Could you, please, add some comments?13:13
noonedeadpunknot to ddos infra mirrors could be one thing :)13:13
noonedeadpunkanskiy: yeah, I need to give that some reading13:13
jrosserwell yes we have several times that the preference was to switch to github and carry on, rather than debug excessive cloning13:14
anskiynoonedeadpunk: thank you :)13:14
jrosserand also there are geographic regions that have / have had severe connectivity trouble to opendev.org but were fine for github13:14
NeilHanlonopendev.org at least supports ipv6 /s13:15
* NeilHanlon makes a note to grumble at Github about that for the month of June13:15
noonedeadpunkanskiy: as I'm not sure about differences in implementation. I think that for OVN you need to setup only single az where it's running, comparing to how ovs does. but I'm not really sure about that13:15
noonedeadpunkbut then I'm not also sure how to make ovn spawn routers cross-AZ for example13:17
lowercasejust a heads up, I hope you all didn't use the ATM in the lobby of the convention center cause someone stole my and my cowokers credit card numbers lol.13:19
NeilHanlonoh, hey--I also had my card stolen after returning from vancouver...13:19
NeilHanlondid not use the ATM, though.13:19
NeilHanlonat least it's not just me? that somehow makes me feel slighlty better...13:20
noonedeadpunkoh damn13:20
NeilHanlonlast night I got a fraud alert for someone trying to use it for an electric scooter or some shit13:21
noonedeadpunkI think I used credit card directly only once when purchasing train ticket - rest were google pay13:21
lowercaseI knew i should have used my google pay.13:21
* NeilHanlon should really use google pay more13:21
mgariepymy wife got that without even have been to vancouver..13:22
mgariepythe only thing she was paying with her CC was patreon..13:22
lowercaseThe charges are RBC Bank for me13:23
anskiynoonedeadpunk: well, according to the doc I've linked, which is specifically for OVN, they are setting multiple AZs in OVS in examples. But in my deployment I'm only using it as: one node -- one AZ.13:24
noonedeadpunkyeah, haven't read it yet :(13:25
anskiyI think it could be related to the role of ovn-controller, as it is the service which claims LSPs on nodes.13:25
anskiynoonedeadpunk: I'll wait patiently :)13:26
* NeilHanlon also remembers to grumble about OVN folks overloading terminology used by MPLS...13:26
NeilHanlonI was like "I didn't know OVN had Label Switched Paths"13:27
opendevreviewSimon Hensel proposed openstack/openstack-ansible-galera_server master: Add optional compression to mariabackup  https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/88618013:35
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-os_cinder master: Use v3 service type in keystone_authtoken config  https://review.opendev.org/c/openstack/openstack-ansible-os_cinder/+/88649714:11
jrosser^ pretty messy in the os_cinder role with left overs from unversioned and v2 api14:12
jamesdentonfrickler I can confirm this environment was using an override to set the baseurl to github.com vs opendev.org, likely during the initial deployment... for reasons™14:15
fricklerjamesdenton: we've discussed this in #opendev, current status is that tags aren't immediately mirrored to github, only when another change happens in a repo14:18
jamesdentonthat's good to know, thank you. Not a huge deal for us, as I expect it's probably opendev.org for most of our deployments unless there's some issue (which might've been the case here during the initial deployment). But might be worth mentioning in docs?14:19
noonedeadpunk#startmeeting openstack_ansible_meeting15:08
opendevmeetMeeting started Tue Jun 20 15:08:41 2023 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.15:08
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:08
opendevmeetThe meeting name has been set to 'openstack_ansible_meeting'15:08
noonedeadpunksorry for being late15:08
noonedeadpunk#topic rollcall15:08
noonedeadpunko/15:08
NeilHanlonhiya 15:08
jrossero/ hello15:09
noonedeadpunk#topics bug triage15:10
noonedeadpunkwe've been reported quite some bugs lately, including 2023.1 release15:10
noonedeadpunkThe first one related to ceph_client has been already merged and backport proposed15:11
noonedeadpunk#link https://bugs.launchpad.net/openstack-ansible/+bug/202433915:11
noonedeadpunkNext one, is that I clean forgot to bump plugins collection version to match 2023.115:11
noonedeadpunk#link https://bugs.launchpad.net/openstack-ansible/+bug/202440715:11
noonedeadpunkI plan to do that during bump for next release15:12
damiandabrowskihi15:12
noonedeadpunkBut good to mention that now, as in case I will forget about it again someone would stop bump during review15:12
jrosserhow did that 15:12
jrossersorry - where should we have bumped that? in a-r-r?15:13
noonedeadpunka-c-r15:13
jrosserok15:13
noonedeadpunkas we install it as a collection15:13
noonedeadpunkand I didn't touch collections as didn't want to bring in untested things15:13
noonedeadpunkand it works in CI as we take version from zuul required-projects rather then clone I believe15:14
jrosserhmm ok15:14
noonedeadpunkand last, but not least this one regarding nova failing on password update15:15
noonedeadpunk#link https://bugs.launchpad.net/openstack-ansible/+bug/202337015:15
noonedeadpunkas a solution to that I've proposed to just add a variable that will control if password should be forcefully set or not.15:16
noonedeadpunkwith changing default behaviour15:16
noonedeadpunkalso worth updating doc I believe - I can recall we've stated somewhere that password rotation is not supported15:18
noonedeadpunkso might be worth adding details in there15:18
noonedeadpunkhave hard times finding where it was15:18
noonedeadpunkAlso, during summit I've promised to create a bugs for irrelevant documentation, so that contributors could step in fixing it15:19
noonedeadpunk#action noonedeadpunk to create bug reports for irrelevant documentation15:19
noonedeadpunk#topic office hours15:21
noonedeadpunkI think main things we might wanna do now, is to kill focal tests, and finally update ansible-core version15:22
noonedeadpunkalong with collections15:22
jrosseryes that would be good15:23
noonedeadpunkI've started looking into where we use focal explicitly and using topic:osa/sunset-focal15:24
noonedeadpunkwas checking integrated repo right now15:24
noonedeadpunkI've also tried to update doc on releasing activities, to make it more clear and somewhat a checklist of what we need to do when15:28
noonedeadpunkhttps://review.opendev.org/c/openstack/openstack-ansible/+/88537615:28
noonedeadpunkThe question is though - when we wanna have a new release for 2023.1?15:31
noonedeadpunkShould we make one right away once determined bugs are covered?15:31
noonedeadpunkor should we wait for some more reports?15:31
jrosserwe have usually made a .1.0 release when we think most things are shaken down15:32
jrossernot sure if we are early for that or not tbh15:32
noonedeadpunkI'm kinda in favor of a .0.1, but given we have a "feature" backports - releases team don't like making a bugfix release with such release notes15:33
noonedeadpunkand https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/886458 is smth worth backporting I believe15:34
jrosserfeels like that resolves a bug really15:34
noonedeadpunkbut also changes a behaviour15:35
noonedeadpunkso yeah...15:35
noonedeadpunkmaybe I can drop a release note for 2023.1 bump, but that's kinda nasty thing to do15:36
NeilHanlondo we have an incompatible upgrades policy ?15:36
noonedeadpunkyeah, kinda15:37
noonedeadpunkthough this specific change does not break anything per say15:37
NeilHanlonTrue...15:37
noonedeadpunkbut per say yes, we try to avoid doing incompatible upgrades15:39
noonedeadpunk*in general15:39
NeilHanlonno one deploys .0 releases anyways!!15:41
noonedeadpunkhehe, yeah, that's what we don't suggest for sure :D15:41
noonedeadpunkusually what we say is that .1.0 is usually good enough to upgrade to15:42
noonedeadpunk#endmeeting15:57
opendevmeetMeeting ended Tue Jun 20 15:57:21 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:57
opendevmeetMinutes:        https://meetings.opendev.org/meetings/openstack_ansible_meeting/2023/openstack_ansible_meeting.2023-06-20-15.08.html15:57
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/openstack_ansible_meeting/2023/openstack_ansible_meeting.2023-06-20-15.08.txt15:57
opendevmeetLog:            https://meetings.opendev.org/meetings/openstack_ansible_meeting/2023/openstack_ansible_meeting.2023-06-20-15.08.log.html15:57
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Remove Ubuntu 20.04 support  https://review.opendev.org/c/openstack/openstack-ansible/+/88651715:59
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Remove Ubuntu 20.04 support  https://review.opendev.org/c/openstack/openstack-ansible/+/88651716:04
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Remove Ubuntu 20.04 support  https://review.opendev.org/c/openstack/openstack-ansible/+/88651716:07
lowercasescammers tried to hit my credit card again16:17
opendevreviewDamian Dąbrowski proposed openstack/openstack-ansible master: Allow to update AIO config prior to an upgrade  https://review.opendev.org/c/openstack/openstack-ansible/+/88519016:27
opendevreviewDamian Dąbrowski proposed openstack/openstack-ansible master: Allow to update AIO config prior to an upgrade  https://review.opendev.org/c/openstack/openstack-ansible/+/88519016:29
mgariepylowercase, usually here my bank cancel the card and send me another one.17:13
opendevreviewMerged openstack/openstack-ansible stable/yoga: Drop `else` condition in the container_skel_load loop  https://review.opendev.org/c/openstack/openstack-ansible/+/88614317:37
lowercasemgariepy: I froze my card last night when i received the initial fraud report from my bank. Since the transaction was declined, I just accepted the remaining payments and ordered a new card (and for my bank, also means i get a new card number)18:03
lowercaseIf I would have reported the fraud, they would have shut down my card and then I would have to wait for a new card to begin using transactions. By freezing the card I can unfreeze at any time and process a payment and then re-freeze it again.18:04
noonedeadpunkyeah, that makes sense18:05
lowercaseFrom the thieves perspective, the convention is a fantastic place to place a skimmer. A lot of foot traffic, many of which are boarding a cruise ship. While aboard the cruise ship, the card owner will not have internet and won't be able to contest the charges until they get back to land. This gives the thieves a small window of uncontested withdrawals. Both transactions were for $100 CAN so they aren't messing around un18:08
lowercaseless its big bucks too.18:08
noonedeadpunkactually, ATM in the convention center was shut down at all on Saturday, just recalled `out of service` paper on it...18:10
noonedeadpunkno idea if that's related though18:10
lowercaseThere is a story i read where a pair of thieves placed their own ATM in a shopping mall, and all it did was say that it was unable to complete the transaction. Please try again. The customers reported a fault to the owners, the owners then came back and carted their atm away. Collecting all the card data with it too. Waited 6 months, and then processed transactions.18:12
lowercaseBy doing it this way, it took authorities a long time to trace the common thread of all this fraud to this single ATM that never worked in the first place.18:13
noonedeadpunksounds quite realistic to have that said18:18
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Bump ansible-core to 2.15.1 and collections  https://review.opendev.org/c/openstack/openstack-ansible/+/88652718:44
noonedeadpunklet's see how dramatically it will fail....18:45
NeilHanlonlowercase: well I'm not saying it was me, but I _did_ have my Flipper Zero with me at the convention...18:48
noonedeadpunkdoh... Old good CentOS.... `package glusterfs-server-9.6-1.el9s.x86_64 from @System requires liburing.so.2(LIBURING_2.0)(64bit) - package qemu-img-17:8.0.0-4.el9.x86_64 from appstream requires liburing.so.1()(64bit) - cannot install both liburing-0.7-7.el9.x86_64 from appstream and liburing-2.0-1.el9s.x86_64 from @System`18:49
noonedeadpunkhttps://zuul.opendev.org/t/openstack/build/e9737f42f5274be284cfbe9c2408dd8218:50
* NeilHanlon adjusts his eyes18:50
NeilHanlonreally? a soname bump? :\18:50
* NeilHanlon finds the virt sig18:51
noonedeadpunkyup, looks like this...18:51
noonedeadpunkJust /o\18:51
NeilHanlontableflip.jpg.exe18:56
noonedeadpunk.exe concerns me even more though :D18:58
NeilHanlonnoonedeadpunk: re glusterfs/liburing... it seems this was "unintentional" or so... will update w/ more info when I have it lol22:03
NeilHanlonthough it does seem there are also el9 repos instead of el9s; will have a look if we are using them already for rocky22:07

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!