| *** ralonsoh_ is now known as ralonsoh | 07:33 | |
| zigo | clarkb: $ ssh -p 29418 review.opendev.org gerrit stream-events | 07:59 |
|---|---|---|
| zigo | zigo@review.opendev.org: Permission denied (publickey). | 07:59 |
| zigo | Do I need to ask for specific rights to someone then? | 07:59 |
| elodilles | i guess you just have to use the ssh key you are using in your gerrit account | 08:09 |
| zigo | Which is what I did. | 08:29 |
| elodilles | zigo: the above mentioned command worked fine for me with my ssh key, fwiw | 09:34 |
| elodilles | release-team: since we are quite late with the tempest-plugin tagging i've reviewed the generated release patches and added PTL-Approved+1 for those where we haven't got any answer yet. when you have time please review them: https://review.opendev.org/q/topic:flamingo-tp-latest+is:open | 09:36 |
| clarkb | zigo: elodilles: gerrit does have a specific permission for stream events but I'm pretty sure we let any registered user do it. My hunc his that you need to supply an explicit username as it differs in gerrit and your local machine | 14:44 |
| ttx | done | 14:44 |
| opendevreview | Merged openstack/releases master: Release neutron-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961715 | 14:47 |
| opendevreview | Merged openstack/releases master: Release zaqar-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961723 | 14:47 |
| opendevreview | Merged openstack/releases master: Release blazar-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961699 | 14:47 |
| opendevreview | Merged openstack/releases master: Release designate-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961706 | 14:48 |
| opendevreview | Merged openstack/releases master: Release telemetry-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961718 | 14:52 |
| opendevreview | Merged openstack/releases master: Release freezer-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961707 | 14:53 |
| opendevreview | Merged openstack/releases master: Release watcher-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961722 | 14:53 |
| opendevreview | Merged openstack/releases master: Release glance-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961708 | 14:53 |
| opendevreview | Merged openstack/releases master: Release barbican-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961698 | 14:55 |
| opendevreview | Merged openstack/releases master: Release octavia-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961717 | 14:55 |
| opendevreview | Merged openstack/releases master: Release keystone-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961711 | 14:55 |
| opendevreview | Merged openstack/releases master: Release manila-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961713 | 14:55 |
| opendevreview | Merged openstack/releases master: Release zun-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961724 | 14:56 |
| opendevreview | Merged openstack/releases master: Release heat-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961709 | 14:56 |
| opendevreview | Merged openstack/releases master: Release mistral-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961714 | 14:56 |
| opendevreview | Merged openstack/releases master: Release vitrage-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961721 | 14:56 |
| opendevreview | Merged openstack/releases master: Release trove-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961719 | 14:56 |
| opendevreview | Merged openstack/releases master: Release cyborg-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961705 | 14:57 |
| opendevreview | Merged openstack/releases master: Release venus-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961720 | 15:00 |
| opendevreview | Merged openstack/releases master: Release ironic-tempest-plugin for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/961710 | 15:00 |
| elodilles | ttx: thanks o/ | 15:01 |
| elodilles | we had a release job failure, that is due to some infra issue: https://lists.openstack.org/archives/list/release-job-failures@lists.openstack.org/thread/YGACWEOLNCMR4L5B54NW7HCP5MZ7LBRN/ | 15:19 |
| elodilles | release-openstack-python job had POST_FAILURE with rsync error: unexplained error (code 255) | 15:20 |
| elodilles | tagging was successful | 15:20 |
| elodilles | announce-release and propose-update-constraints jobs were skipped | 15:21 |
| elodilles | i don't think this is an issue, but not nice that we are missing the announce mail :/ | 15:21 |
| elodilles | (tempest-plugins are not present in upper-constraints.txt) | 15:22 |
| clarkb | elodilles: ansible's rsync tasks don't use the ssh controlmaster process to reuse existing connections so they always initiate a new connection. THis make them more susceptible to network blips | 16:46 |
| clarkb | looks like in this case the rsync connection timed out | 16:46 |
| clarkb | That job did run in a cloud that we had network issues with previously (multiple interfaces on the same network causing bad routing decisions) but I believe I fixed that yesterday and checking the job logs indicates there was only one interface as epxected | 16:47 |
| clarkb | it is probably worth monitoring and if it persists or gets worse we can engage the cloud provider (maybe there is something up with the neutron routers or floating ip nat system | 16:47 |
| clarkb | the only other thought I have is that the job is running on ubuntu focal which is quite old. However that shouldn't break rsync ssh connectivity | 16:47 |
| clarkb | more of a general observation that you'll want to update those job nodes at some point | 16:47 |
| elodilles | clarkb: ACK, thanks for the info, there wasn't any other failure, so at least this was a single issue. ubuntu-focal is really not up-to-date, yes :/ i've added it to release team's 'things to change' list, i think we can work with that after the 2025.2 Flamingo release next week | 16:55 |
| clarkb | yup after the release is probably a good idea | 16:56 |
| zigo | clarkb: Thanks, it does work with my username indeed ! :) | 17:42 |
| zigo | ie: ssh -p 29418 thomas-goirand@review.opendev.org gerrit stream-events. | 17:42 |
| zigo | When is release day? Tomorrow? | 21:57 |
| clarkb | a week from tomorrow I think | 21:57 |
| zigo | FYI, got all working smooth on Trixie already, currently Tempest is running on my CI. | 21:57 |
| clarkb | https://releases.openstack.org/flamingo/schedule.html has the schedule | 21:57 |
| zigo | Ah, right. | 21:57 |
| zigo | I missread... :P | 21:58 |
| zigo | clarkb: With the ssh sthingy on gerrit, how can I select only artifact release events? | 21:59 |
| clarkb | zigo: you can use `-s event-type` as arguments to the command to filter down to things you care about. But you'll probably need a small script that looks at the project names and event type and look for the events that teh release team generates when they push releases | 22:01 |
| zigo | Yeah, but what event-type will that be? | 22:01 |
| clarkb | ref updated events then looking for tag refs like refs/tags/x.y.z events | 22:01 |
| clarkb | I think | 22:01 |
| zigo | Oh, thanks. | 22:01 |
| clarkb | zigo: the release team runs ci jobs that push tags to the projects which then kick off jobs to build the versions of software at that git tag | 22:03 |
| zigo | clarkb: something like this then ? ssh -p 29418 thomas-goirand@review.opendev.org "gerrit stream-events -s ref-updated" | 22:03 |
| clarkb | so in theory looking for events that map to that set of actions is close to what you want | 22:03 |
| clarkb | yes I think so | 22:03 |
| zigo | Will try, thanks ! | 22:03 |
| clarkb | note that ref-updated will give you more than just tags | 22:03 |
| zigo | I can make an ssh key especially for that, right? | 22:03 |
| clarkb | it will include every merge to master for example so you need to filter futher but the command itself cannot do that | 22:03 |
| clarkb | you can have multiple ssh keys in gerrit but they can't be limited to specific actions | 22:04 |
| zigo | Ok. My point: I don't want to do that with my Yubikey's key ... :P | 22:04 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!