frickler | I'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 itself | 07:20 |
---|---|---|
jrosser | jamesdenton: 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 |
frickler | jrosser: 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/tags | 08:31 |
kleini | I discovered no issues upgrading to 24.6.1, which should be xena-em. | 08:35 |
frickler | kleini: do you use github as source or opendev? | 08:36 |
kleini | I use the default. I think, that is opendev. | 08:36 |
frickler | then you wouldn't be affected by tags missing on github | 08:37 |
opendevreview | Simon Hensel proposed openstack/openstack-ansible-galera_server master: Add optional compression to mariabackup https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/886180 | 09:03 |
noonedeadpunk | mornings | 09:17 |
noonedeadpunk | thanks frickler for checking on that | 09:18 |
opendevreview | Jonathan 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/+/886471 | 09:46 |
noonedeadpunk | we should also merge that fix for ceph client https://review.opendev.org/c/openstack/openstack-ansible-ceph_client/+/886398 | 09:59 |
admin12 | i am on 26.1.0 and getting this on a new build .. https://paste.opendev.org/raw/bI9XZNtrrz8YbDj8DjYl/ | 10:59 |
admin1 | i fixed my nick .. | 11:00 |
admin1 | ceph is external | 11:00 |
noonedeadpunk | well, 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 host | 11:06 |
noonedeadpunk | so it's obviously issue with gpg key for the ceph repo | 11:07 |
admin1 | hi 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 |
noonedeadpunk | admin1: 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 group | 11:12 |
noonedeadpunk | or better say - where these containers should be created | 11:12 |
admin1 | i will give it a try | 11:17 |
admin1 | added it .. run --syntax-check and checked inventory list .. it did not add | 11:20 |
admin1 | added like this: https://paste.opendev.org/raw/bQrMDlqqddtImO4gK1wq/ | 11:20 |
noonedeadpunk | that should be enough ^ | 11:25 |
noonedeadpunk | admin1: oh, well, you have `cinder_nfs_volumes_container` mentioned twice in env.d file | 11:35 |
noonedeadpunk | maybe that;s what causing the ignorance of it | 11:36 |
opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-plugins master: Skip updating service password by default https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/886458 | 11:44 |
opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-plugins master: Skip updating service password by default https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/886458 | 11:57 |
opendevreview | Merged openstack/openstack-ansible-ceph_client master: Fix retrievement keyrings from files https://review.opendev.org/c/openstack/openstack-ansible-ceph_client/+/886398 | 12:31 |
opendevreview | Jonathan 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/+/886477 | 12:32 |
anskiy | noonedeadpunk: hey, any news from nova folks regarding https://bugs.launchpad.net/openstack-ansible/+bug/2023370 this thing? | 12:48 |
noonedeadpunk | I clean forgot to talk about that during PTG :( | 12:48 |
jamesdenton | @jrosser @frickler Thanks for looking into it! | 12:49 |
noonedeadpunk | Like was sooo many things to address that this one has slipped | 12:49 |
anskiy | no worries, should I open a bug in Nova? | 12:50 |
noonedeadpunk | This patch can be just linked to nova as well | 12:50 |
noonedeadpunk | there's "also affects project" button | 12:51 |
noonedeadpunk | But I've asked them today in IRC, hoped to get some answer before doing that | 12:51 |
anskiy | noonedeadpunk: ah, so, you're gonna link them whenever they'll answer you? | 12:57 |
noonedeadpunk | we're discussing right now in #openstack-nova fwiw :) | 12:59 |
NeilHanlon | i knew i needed more channels to be in ;) | 12:59 |
frickler | jamesdenton: so can you confirm that you indeed use github as a source? is there a specific reason for doing so? | 13:11 |
jamesdenton | i will double check both of those shortly | 13:11 |
anskiy | noonedeadpunk: 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 |
noonedeadpunk | not to ddos infra mirrors could be one thing :) | 13:13 |
noonedeadpunk | anskiy: yeah, I need to give that some reading | 13:13 |
jrosser | well yes we have several times that the preference was to switch to github and carry on, rather than debug excessive cloning | 13:14 |
anskiy | noonedeadpunk: thank you :) | 13:14 |
jrosser | and also there are geographic regions that have / have had severe connectivity trouble to opendev.org but were fine for github | 13:14 |
NeilHanlon | opendev.org at least supports ipv6 /s | 13:15 |
* NeilHanlon makes a note to grumble at Github about that for the month of June | 13:15 | |
noonedeadpunk | anskiy: 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 that | 13:15 |
noonedeadpunk | but then I'm not also sure how to make ovn spawn routers cross-AZ for example | 13:17 |
lowercase | just 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 |
NeilHanlon | oh, hey--I also had my card stolen after returning from vancouver... | 13:19 |
NeilHanlon | did not use the ATM, though. | 13:19 |
NeilHanlon | at least it's not just me? that somehow makes me feel slighlty better... | 13:20 |
noonedeadpunk | oh damn | 13:20 |
NeilHanlon | last night I got a fraud alert for someone trying to use it for an electric scooter or some shit | 13:21 |
noonedeadpunk | I think I used credit card directly only once when purchasing train ticket - rest were google pay | 13:21 |
lowercase | I knew i should have used my google pay. | 13:21 |
* NeilHanlon should really use google pay more | 13:21 | |
mgariepy | my wife got that without even have been to vancouver.. | 13:22 |
mgariepy | the only thing she was paying with her CC was patreon.. | 13:22 |
lowercase | The charges are RBC Bank for me | 13:23 |
anskiy | noonedeadpunk: 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 |
noonedeadpunk | yeah, haven't read it yet :( | 13:25 |
anskiy | I think it could be related to the role of ovn-controller, as it is the service which claims LSPs on nodes. | 13:25 |
anskiy | noonedeadpunk: I'll wait patiently :) | 13:26 |
* NeilHanlon also remembers to grumble about OVN folks overloading terminology used by MPLS... | 13:26 | |
NeilHanlon | I was like "I didn't know OVN had Label Switched Paths" | 13:27 |
opendevreview | Simon Hensel proposed openstack/openstack-ansible-galera_server master: Add optional compression to mariabackup https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/886180 | 13:35 |
opendevreview | Jonathan 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/+/886497 | 14:11 |
jrosser | ^ pretty messy in the os_cinder role with left overs from unversioned and v2 api | 14:12 |
jamesdenton | frickler 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 |
frickler | jamesdenton: we've discussed this in #opendev, current status is that tags aren't immediately mirrored to github, only when another change happens in a repo | 14:18 |
jamesdenton | that'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_meeting | 15:08 |
opendevmeet | Meeting 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 |
opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:08 |
opendevmeet | The meeting name has been set to 'openstack_ansible_meeting' | 15:08 |
noonedeadpunk | sorry for being late | 15:08 |
noonedeadpunk | #topic rollcall | 15:08 |
noonedeadpunk | o/ | 15:08 |
NeilHanlon | hiya | 15:08 |
jrosser | o/ hello | 15:09 |
noonedeadpunk | #topics bug triage | 15:10 |
noonedeadpunk | we've been reported quite some bugs lately, including 2023.1 release | 15:10 |
noonedeadpunk | The first one related to ceph_client has been already merged and backport proposed | 15:11 |
noonedeadpunk | #link https://bugs.launchpad.net/openstack-ansible/+bug/2024339 | 15:11 |
noonedeadpunk | Next one, is that I clean forgot to bump plugins collection version to match 2023.1 | 15:11 |
noonedeadpunk | #link https://bugs.launchpad.net/openstack-ansible/+bug/2024407 | 15:11 |
noonedeadpunk | I plan to do that during bump for next release | 15:12 |
damiandabrowski | hi | 15:12 |
noonedeadpunk | But good to mention that now, as in case I will forget about it again someone would stop bump during review | 15:12 |
jrosser | how did that | 15:12 |
jrosser | sorry - where should we have bumped that? in a-r-r? | 15:13 |
noonedeadpunk | a-c-r | 15:13 |
jrosser | ok | 15:13 |
noonedeadpunk | as we install it as a collection | 15:13 |
noonedeadpunk | and I didn't touch collections as didn't want to bring in untested things | 15:13 |
noonedeadpunk | and it works in CI as we take version from zuul required-projects rather then clone I believe | 15:14 |
jrosser | hmm ok | 15:14 |
noonedeadpunk | and last, but not least this one regarding nova failing on password update | 15:15 |
noonedeadpunk | #link https://bugs.launchpad.net/openstack-ansible/+bug/2023370 | 15:15 |
noonedeadpunk | as 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 |
noonedeadpunk | with changing default behaviour | 15:16 |
noonedeadpunk | also worth updating doc I believe - I can recall we've stated somewhere that password rotation is not supported | 15:18 |
noonedeadpunk | so might be worth adding details in there | 15:18 |
noonedeadpunk | have hard times finding where it was | 15:18 |
noonedeadpunk | Also, during summit I've promised to create a bugs for irrelevant documentation, so that contributors could step in fixing it | 15:19 |
noonedeadpunk | #action noonedeadpunk to create bug reports for irrelevant documentation | 15:19 |
noonedeadpunk | #topic office hours | 15:21 |
noonedeadpunk | I think main things we might wanna do now, is to kill focal tests, and finally update ansible-core version | 15:22 |
noonedeadpunk | along with collections | 15:22 |
jrosser | yes that would be good | 15:23 |
noonedeadpunk | I've started looking into where we use focal explicitly and using topic:osa/sunset-focal | 15:24 |
noonedeadpunk | was checking integrated repo right now | 15:24 |
noonedeadpunk | I've also tried to update doc on releasing activities, to make it more clear and somewhat a checklist of what we need to do when | 15:28 |
noonedeadpunk | https://review.opendev.org/c/openstack/openstack-ansible/+/885376 | 15:28 |
noonedeadpunk | The question is though - when we wanna have a new release for 2023.1? | 15:31 |
noonedeadpunk | Should we make one right away once determined bugs are covered? | 15:31 |
noonedeadpunk | or should we wait for some more reports? | 15:31 |
jrosser | we have usually made a .1.0 release when we think most things are shaken down | 15:32 |
jrosser | not sure if we are early for that or not tbh | 15:32 |
noonedeadpunk | I'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 notes | 15:33 |
noonedeadpunk | and https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/886458 is smth worth backporting I believe | 15:34 |
jrosser | feels like that resolves a bug really | 15:34 |
noonedeadpunk | but also changes a behaviour | 15:35 |
noonedeadpunk | so yeah... | 15:35 |
noonedeadpunk | maybe I can drop a release note for 2023.1 bump, but that's kinda nasty thing to do | 15:36 |
NeilHanlon | do we have an incompatible upgrades policy ? | 15:36 |
noonedeadpunk | yeah, kinda | 15:37 |
noonedeadpunk | though this specific change does not break anything per say | 15:37 |
NeilHanlon | True... | 15:37 |
noonedeadpunk | but per say yes, we try to avoid doing incompatible upgrades | 15:39 |
noonedeadpunk | *in general | 15:39 |
NeilHanlon | no one deploys .0 releases anyways!! | 15:41 |
noonedeadpunk | hehe, yeah, that's what we don't suggest for sure :D | 15:41 |
noonedeadpunk | usually what we say is that .1.0 is usually good enough to upgrade to | 15:42 |
noonedeadpunk | #endmeeting | 15:57 |
opendevmeet | Meeting ended Tue Jun 20 15:57:21 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:57 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/openstack_ansible_meeting/2023/openstack_ansible_meeting.2023-06-20-15.08.html | 15:57 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/openstack_ansible_meeting/2023/openstack_ansible_meeting.2023-06-20-15.08.txt | 15:57 |
opendevmeet | Log: https://meetings.opendev.org/meetings/openstack_ansible_meeting/2023/openstack_ansible_meeting.2023-06-20-15.08.log.html | 15:57 |
opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Remove Ubuntu 20.04 support https://review.opendev.org/c/openstack/openstack-ansible/+/886517 | 15:59 |
opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Remove Ubuntu 20.04 support https://review.opendev.org/c/openstack/openstack-ansible/+/886517 | 16:04 |
opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Remove Ubuntu 20.04 support https://review.opendev.org/c/openstack/openstack-ansible/+/886517 | 16:07 |
lowercase | scammers tried to hit my credit card again | 16:17 |
opendevreview | Damian Dąbrowski proposed openstack/openstack-ansible master: Allow to update AIO config prior to an upgrade https://review.opendev.org/c/openstack/openstack-ansible/+/885190 | 16:27 |
opendevreview | Damian Dąbrowski proposed openstack/openstack-ansible master: Allow to update AIO config prior to an upgrade https://review.opendev.org/c/openstack/openstack-ansible/+/885190 | 16:29 |
mgariepy | lowercase, usually here my bank cancel the card and send me another one. | 17:13 |
opendevreview | Merged openstack/openstack-ansible stable/yoga: Drop `else` condition in the container_skel_load loop https://review.opendev.org/c/openstack/openstack-ansible/+/886143 | 17:37 |
lowercase | mgariepy: 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 |
lowercase | If 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 |
noonedeadpunk | yeah, that makes sense | 18:05 |
lowercase | From 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 un | 18:08 |
lowercase | less its big bucks too. | 18:08 |
noonedeadpunk | actually, ATM in the convention center was shut down at all on Saturday, just recalled `out of service` paper on it... | 18:10 |
noonedeadpunk | no idea if that's related though | 18:10 |
lowercase | There 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 |
lowercase | By 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 |
noonedeadpunk | sounds quite realistic to have that said | 18:18 |
opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Bump ansible-core to 2.15.1 and collections https://review.opendev.org/c/openstack/openstack-ansible/+/886527 | 18:44 |
noonedeadpunk | let's see how dramatically it will fail.... | 18:45 |
NeilHanlon | lowercase: well I'm not saying it was me, but I _did_ have my Flipper Zero with me at the convention... | 18:48 |
noonedeadpunk | doh... 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 |
noonedeadpunk | https://zuul.opendev.org/t/openstack/build/e9737f42f5274be284cfbe9c2408dd82 | 18:50 |
* NeilHanlon adjusts his eyes | 18:50 | |
NeilHanlon | really? a soname bump? :\ | 18:50 |
* NeilHanlon finds the virt sig | 18:51 | |
noonedeadpunk | yup, looks like this... | 18:51 |
noonedeadpunk | Just /o\ | 18:51 |
NeilHanlon | tableflip.jpg.exe | 18:56 |
noonedeadpunk | .exe concerns me even more though :D | 18:58 |
NeilHanlon | noonedeadpunk: re glusterfs/liburing... it seems this was "unintentional" or so... will update w/ more info when I have it lol | 22:03 |
NeilHanlon | though it does seem there are also el9 repos instead of el9s; will have a look if we are using them already for rocky | 22:07 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!