| *** ysandeep|out is now known as ysandeep | 05:27 | |
| *** sshnaidm|afk is now known as sshnaidm | 06:57 | |
| *** ysandeep is now known as ysandeep|lunch | 07:26 | |
| *** ysandeep|lunch is now known as ysandeep | 08:41 | |
| noonedeadpunk | yeah, we should merge https://review.opendev.org/c/openstack/openstack-ansible/+/821476 asap to start great OS cleanup | 08:51 |
|---|---|---|
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: [doc] Add Xena compatible OS https://review.opendev.org/c/openstack/openstack-ansible/+/821676 | 08:53 |
| jrosser | is there anything remaining to fix up for X release? | 09:03 |
| noonedeadpunk | Nothing I can think of tbh | 09:06 |
| noonedeadpunk | the only nasty thing, is that it feels like we need rc2 anyway. As if release from rc1 we will miss gitreview... From other side - nobody contributes from tag?:D | 09:07 |
| jrosser | i wonder if there are tools which read that | 09:07 |
| noonedeadpunk | I doubt that. I think we reference git status mostly | 09:10 |
| noonedeadpunk | I'm a bit tempted to make 24.0.0 from rc1 directly.... | 09:12 |
| noonedeadpunk | as there're really zero functional changes... | 09:14 |
| *** ysandeep is now known as ysandeep|afk | 09:35 | |
| jrosser | noonedeadpunk: i wonder if there is more for the cycle highlights now we are finished | 10:02 |
| jrosser | did we make galera TLS by default in the end? | 10:02 |
| noonedeadpunk | we did | 10:05 |
| noonedeadpunk | well, it makes limited sense as highlights are published by PR team several weeks before global release | 10:06 |
| noonedeadpunk | what we can do - write a prelude release note | 10:07 |
| noonedeadpunk | which actually for highlighting important things | 10:08 |
| *** ysandeep|afk is now known as ysandeep | 10:32 | |
| *** dviroel|rover|afk is now known as dviroel|rover | 11:01 | |
| opendevreview | Merged openstack/openstack-ansible-openstack_hosts stable/victoria: Add CentOS 8.4 support https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/818487 | 11:02 |
| opendevreview | Merged openstack/openstack-ansible-openstack_hosts stable/ussuri: Add CentOS 8.4 support https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/818488 | 11:02 |
| jrosser | hmm | 11:42 |
| jrosser | 2021-12-14T09:47:34,683 The conflict is caused by: | 11:42 |
| jrosser | 2021-12-14T09:47:34,683 keystone 20.1.0.dev19 depends on PyJWT>=1.6.1 | 11:42 |
| jrosser | 2021-12-14T09:47:34,683 The user requested (constraint) pyjwt===2.3.0 | 11:42 |
| jrosser | i wonder how thats happening | 11:43 |
| noonedeadpunk | where does this come from? | 11:49 |
| noonedeadpunk | aha, yoga patch... | 11:50 |
| jrosser | i started poking in the logs of this https://review.opendev.org/c/openstack/openstack-ansible/+/821476 | 11:50 |
| jrosser | actually this is why we need those logs from /openstack/repo/*/*/...... to grab all those .txt files | 11:51 |
| noonedeadpunk | but it's not really a conflict.... | 11:52 |
| jrosser | well the new resolver treats > 1 constraint for anything as a confict afaik | 11:53 |
| jrosser | and theres kind of a unusal pattern of pass/fail on that job, not obvious why | 11:53 |
| noonedeadpunk | and check passed as well.... | 11:54 |
| noonedeadpunk | but also - there's a single constraint I guess? | 11:54 |
| noonedeadpunk | PyJWT>=1.6.1 comes from requirements... | 11:55 |
| jrosser | yes | 11:55 |
| jrosser | but i think it means that the === line ended up in one of the other .txt files | 11:55 |
| noonedeadpunk | in u-c we have PyJWT===2.3.0 | 11:55 |
| jrosser | oh! | 11:55 |
| noonedeadpunk | so question where does lower case come from | 11:56 |
| jrosser | this has the feel of something that has broken because we branched / unpinned the roles | 11:58 |
| jrosser | this patch unpins everything and we take master u-c and services | 11:58 |
| noonedeadpunk | let me dare to recheck out of interest.... | 11:59 |
| jrosser | sure :) | 11:59 |
| jrosser | rebase maybe for good measure | 11:59 |
| noonedeadpunk | oh, yes, indeed | 11:59 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Start Yoga development cycle https://review.opendev.org/c/openstack/openstack-ansible/+/821476 | 11:59 |
| noonedeadpunk | great call | 12:00 |
| jrosser | rebase shouldnt matter because the patch should always be on the head of master? | 12:00 |
| jrosser | but somehow it does at times | 12:00 |
| noonedeadpunk | um, no, I'm not sure about that. Zuul retireves current position of repo that you're currently testing | 12:14 |
| noonedeadpunk | all rest is always master though | 12:14 |
| *** ysandeep is now known as ysandeep|brb | 12:21 | |
| *** ysandeep|brb is now known as ysandeep | 12:48 | |
| mgariepy | good morning everyone | 12:54 |
| noonedeadpunk | o/ | 13:40 |
| noonedeadpunk | jrosser: hm, it seems passing now... | 13:52 |
| jrosser | looks like pypi / fastly problem according to #opendev | 13:53 |
| noonedeadpunk | ah, makes sense then | 14:01 |
| *** ysandeep is now known as ysandeep|out | 14:13 | |
| *** dviroel|rover is now known as dviroel|rover|lunch | 14:59 | |
| noonedeadpunk | #startmeeting openstack_ansible_meeting | 15:00 |
| opendevmeet | Meeting started Tue Dec 14 15:00:34 2021 UTC and is due to finish in 60 minutes. The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| opendevmeet | The meeting name has been set to 'openstack_ansible_meeting' | 15:00 |
| noonedeadpunk | #topic office hours | 15:00 |
| noonedeadpunk | o/ | 15:00 |
| damiandabrowski[m] | hey! | 15:00 |
| jrosser | o/ hello | 15:01 |
| noonedeadpunk | tbh I don't have too much things to discuss:) | 15:02 |
| noonedeadpunk | except maybe if it's worth doing rc2 just for gitreview files... | 15:02 |
| spatel | hey | 15:03 |
| noonedeadpunk | I actually talked to releases team and from their POV we can just have stable tag based just on RC1 | 15:03 |
| spatel | are we safe with apache log4j ? | 15:03 |
| noonedeadpunk | openstack doesn't use java, so... | 15:03 |
| noonedeadpunk | can't say so regarding ELK or graylog, but that's quite different stories | 15:04 |
| noonedeadpunk | Oh, also I think we should finally EOL ocata https://review.opendev.org/c/openstack/openstack-ansible/+/795690 | 15:04 |
| noonedeadpunk | And I'm also thinking that time for pike and might be queens? | 15:05 |
| mgariepy | graylog have some fixes. | 15:06 |
| noonedeadpunk | ah, and gerrit ofc | 15:07 |
| noonedeadpunk | Once https://review.opendev.org/c/openstack/openstack-ansible/+/821476 land we should be able to land upcoming changes. jrosser has started with dropping CentOS 8, Debian 10 and Ubuntu bionic support | 15:08 |
| noonedeadpunk | Which is really good and worthy cleanup | 15:08 |
| damiandabrowski[m] | actually i wonder how many releases are we obligated to support? or it depend entirely on us? | 15:09 |
| noonedeadpunk | Eventually we follow https://releases.openstack.org/ for maintained state | 15:09 |
| noonedeadpunk | regarding EOL - it's up to projects | 15:09 |
| jrosser | we need to have some sort of decision / "words in a release note" about what we do with centos-8 on stable branches | 15:09 |
| jrosser | as i think the infra people are talking about removing the ci images soon | 15:10 |
| noonedeadpunk | I'd say we just stop testing it there | 15:10 |
| noonedeadpunk | and reno could be also like that "With CentOS 8 EOL we stop completing CI testing for this Operating System. It is highly recommended to upgrade to one of the supported systems" | 15:12 |
| damiandabrowski[m] | ah, so IMO we may mark pike and queens EOL ;) | 15:12 |
| noonedeadpunk | damiandabrowski[m]: I believe that Octavia have already EOLed even stein | 15:13 |
| noonedeadpunk | they're kind of leaders for keeping minimal releases even in EM state | 15:13 |
| noonedeadpunk | jrosser: mgariepy wdyt about eoling pike/queens? | 15:16 |
| jrosser | i would be OK with that - we don't see anyone submitting fixes | 15:16 |
| mgariepy | i'm also ok with this. and if we do see some stuff that really need fixing we can always fix it.. | 15:17 |
| noonedeadpunk | we won't be able to backport, but I doubt we will anyway | 15:17 |
| noonedeadpunk | looking at review dashboard we have some fixes for Rocky that we can't merge for quite a while | 15:17 |
| noonedeadpunk | mainly because tempest is broken... https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/782990 | 15:18 |
| noonedeadpunk | #agreed EOL Pike and Queens | 15:19 |
| noonedeadpunk | oh, eventually with that I was also thinking that we should change landing page of our docs for stable branches | 15:20 |
| damiandabrowski[m] | maybe it's the right time to announce how many releases we're going to support? just to make it official and predictable | 15:20 |
| noonedeadpunk | and leave there only current release data | 15:20 |
| noonedeadpunk | We _really_ support only releases that OpenStack considers as maintained | 15:21 |
| noonedeadpunk | As for EM, it's more like security patching | 15:22 |
| noonedeadpunk | So we jsut follow openstack state here https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases | 15:23 |
| noonedeadpunk | as for number of releases in EM - that's good question. I won't them call supported though :D | 15:23 |
| jrosser | its a good time to clean up - there are relatively few outstanding stable branch patches | 15:23 |
| noonedeadpunk | I'd say we can probably carry 3 releases in EM for sure? | 15:24 |
| noonedeadpunk | or actually 4 I guess now (as U is in EM now) | 15:25 |
| noonedeadpunk | it's a bit harder as we're trailing | 15:25 |
| noonedeadpunk | jrosser: the obvious problem is with https://review.opendev.org/c/openstack/openstack-ansible-os_almanach/+/658585 | 15:26 |
| noonedeadpunk | as we've retired repo | 15:26 |
| noonedeadpunk | so we don't have access to abandon it... | 15:26 |
| * noonedeadpunk reaching infra-rrot | 15:26 | |
| jrosser | we can ask in #opendev to get those patches abandoned | 15:26 |
| noonedeadpunk | *root | 15:26 |
| jrosser | yep | 15:26 |
| noonedeadpunk | Would be also great to clean-up master but well... | 15:27 |
| noonedeadpunk | we have tons of leftovers there... | 15:27 |
| damiandabrowski[m] | keeping 3-4 EM releases is fine to me | 15:27 |
| noonedeadpunk | ok, great | 15:30 |
| noonedeadpunk | will prepare patches then | 15:31 |
| noonedeadpunk | eventually I hope that with left focal and debian 11 (and centos 8-stream) we will be able to have ansible-core 2.12.... | 15:37 |
| noonedeadpunk | not sure if 8-stream does have libselinux for py38 but we can probably have some nasty workaround for it.... | 15:38 |
| jrosser | there was a pip module i think? | 15:38 |
| jrosser | https://pypi.org/project/selinux/ | 15:39 |
| noonedeadpunk | well it doesn't look too promising tbh.... | 15:39 |
| noonedeadpunk | unfortunatelly zbr is not around to ask... | 15:40 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible stable/xena: [doc] Clean out project index page for stable branches https://review.opendev.org/c/openstack/openstack-ansible/+/821720 | 15:47 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible stable/wallaby: [doc] Clean out project index page for stable branches https://review.opendev.org/c/openstack/openstack-ansible/+/821723 | 15:49 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible stable/xena: [doc] Clean out project index page for stable branches https://review.opendev.org/c/openstack/openstack-ansible/+/821720 | 15:51 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible stable/wallaby: [doc] Clean out project index page for stable branches https://review.opendev.org/c/openstack/openstack-ansible/+/821723 | 15:51 |
| noonedeadpunk | sorry, updated a bit | 15:51 |
| noonedeadpunk | as we already have that format for R->V | 15:52 |
| noonedeadpunk | only missed that for W and X | 15:52 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: [doc] Update stable releases support status https://review.opendev.org/c/openstack/openstack-ansible/+/821726 | 15:54 |
| *** dviroel|rover|lunch is now known as dviroel|rover | 15:59 | |
| noonedeadpunk | #endmeeting | 15:59 |
| opendevmeet | Meeting ended Tue Dec 14 15:59:58 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:59 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/openstack_ansible_meeting/2021/openstack_ansible_meeting.2021-12-14-15.00.html | 15:59 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/openstack_ansible_meeting/2021/openstack_ansible_meeting.2021-12-14-15.00.txt | 15:59 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/openstack_ansible_meeting/2021/openstack_ansible_meeting.2021-12-14-15.00.log.html | 15:59 |
| opendevreview | Merged openstack/openstack-ansible master: Add documentation of security improvements made to Openstack Ansible https://review.opendev.org/c/openstack/openstack-ansible/+/820370 | 16:38 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible stable/xena: Add documentation of security improvements made to Openstack Ansible https://review.opendev.org/c/openstack/openstack-ansible/+/821529 | 16:38 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/ansible-role-python_venv_build master: Verify that wheels are normally built https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/821415 | 16:53 |
| noonedeadpunk | the worst thing about that is ansible will render it in single line :( | 16:54 |
| noonedeadpunk | multiline is supported only for debug, but not for assert or fail which is a bummer | 16:54 |
| noonedeadpunk | (I was talking about https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/821415/2/tasks/main.yml ) | 16:54 |
| damiandabrowski[m] | hmm, i think i've managed to write multi line msg in fail module some time ago, but i'm not 100% sure | 16:56 |
| damiandabrowski[m] | let me check | 16:56 |
| noonedeadpunk | well, based on ansible docs, it's only string while for debug it could be list | 16:56 |
| noonedeadpunk | and "\n" were not interpreted | 16:57 |
| jrosser | we could turn it to a block | 16:57 |
| noonedeadpunk | but would be great to double check that | 16:57 |
| noonedeadpunk | then it will be jsut connected with "\n\n" or smth in single line which even worse I guess | 16:58 |
| noonedeadpunk | at least this way I managed to get it to be kind of readable while renderred in single line. Other options were just adding extra symbols to this line... | 17:00 |
| noonedeadpunk | but again - great if damiandabrowski[m] can double-check | 17:00 |
| damiandabrowski[m] | yeah noonedeadpunk actually i have multi-line fail msg implemented in my playbooks. But I just missed the fact that it doesn't work :D '\n' is just printed out as a string | 17:04 |
| noonedeadpunk | yeah... | 17:04 |
| noonedeadpunk | that is what I saw a was really surprised hehe | 17:04 |
| noonedeadpunk | *and | 17:07 |
| jamesdenton | anyone here using nfs w/ cinder? | 19:35 |
| jamesdenton | i started seeing this "Could not open \'/var/lib/nova/mnt/120c62d21bb233322c4a09c7a3d8f53f/volume-bbc22262-1623-49a7-a0f3-53f1cf84b880\': Permission denied\n'" error in nova-compute/conductor pretty recently (on 24.1.0.dev3 now) when trying to boot from volume, and not sure if it's me or if something broke | 19:37 |
| *** dviroel|rover is now known as dviroel|out | 20:31 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!