| opendevreview | Goutham Pacha Ravi proposed openstack/project-config master: Add devstack-plugin-lustre notifications https://review.opendev.org/c/openstack/project-config/+/989053 | 04:44 |
|---|---|---|
| opendevreview | Goutham Pacha Ravi proposed openstack/project-config master: Add devstack-plugin-lustre to Zuul tenant https://review.opendev.org/c/openstack/project-config/+/989054 | 05:00 |
| opendevreview | Dmitriy Chubinidze proposed openstack/openstack-zuul-jobs master: Fix variable assignment syntax and typo in install_horizon https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/989068 | 07:44 |
| opendevreview | Dmitriy Chubinidze proposed openstack/openstack-zuul-jobs master: Fix variable assignment syntax and typo in install_horizon https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/989068 | 07:45 |
| mikal | Hey, my Debian Trixie Kolla-Ansible zuul jobs have been failing for around 24 hours with what looks to me like an inconsistent sync. Is it possible that the syncer thingie needs a pep talk? | 08:49 |
| frickler | yes. "The lock file '/afs/.openstack.org/mirror/debian/db/lockfile' already exists." not sure if that might be related to the other mirror updates fungi was doing recently | 10:02 |
| opendevreview | Merged openstack/project-config master: Fix publish-openstack-releasenotes-python3 job https://review.opendev.org/c/openstack/project-config/+/988968 | 11:47 |
| *** ykarel_ is now known as ykarel | 13:13 | |
| fungi | frickler: mikal: it was not related to earlier work, but there was a trixie point release this week and i bet reprepro timed out trying to download all the churn. i'll take a look | 13:32 |
| fungi | the job failures are likely due to the packages on job nodes being newer than the ones in our mirrors | 13:32 |
| opendevreview | Merged openstack/openstack-zuul-jobs master: Fix variable assignment syntax and typo in install_horizon https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/989068 | 13:54 |
| clarkb | fungi: our image builds should build against our mirrors to avoid this problem. And the vos release + reprepro consistency checking should ensure that while we may be stale the mirror itself should be valid/functional | 14:46 |
| clarkb | I wonder if the problem is when mixing in other external packages like for erlang (I think kolla pulls those in separately) if they depend on new packages | 14:46 |
| fungi | entirely possible, i haven't seen the example failure details | 14:52 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/project-config master: Change ACLs for Venus to retired https://review.opendev.org/c/openstack/project-config/+/989144 | 14:55 |
| frickler | example failure is https://zuul.opendev.org/t/openstack/build/a979c3fada98466fa886dc22a181930f, looks like the issue is happening in container builds, so very likely we are use a newer docker debian base image? example build log | 15:07 |
| frickler | https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_a97/openstack/a979c3fada98466fa886dc22a181930f/primary/logs/build/000_FAILED_openstack-base.log | 15:07 |
| frickler | "FROM quay.io/opendevmirror/debian:trixie" | 15:07 |
| fungi | yeah, that probably updated for debian 13.5 and our mirror hasn't (yet) | 15:12 |
| clarkb | ya that would explain it | 15:16 |
| opendevreview | Merged openstack/project-config master: Add devstack-plugin-lustre notifications https://review.opendev.org/c/openstack/project-config/+/989053 | 15:37 |
| opendevreview | Merged openstack/project-config master: Add devstack-plugin-lustre to Zuul tenant https://review.opendev.org/c/openstack/project-config/+/989054 | 15:37 |
| opendevreview | Merged openstack/project-config master: [EOL]: Remove VirtualPDU repository references https://review.opendev.org/c/openstack/project-config/+/988655 | 15:47 |
| opendevreview | Merged openstack/openstack-zuul-jobs master: Change py314 jobs to non-voting in stable/2026.1 https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/981538 | 15:50 |
| opendevreview | Elod Illes proposed openstack/project-config master: [release-tool] check-approval use only governance data https://review.opendev.org/c/openstack/project-config/+/989179 | 16:43 |
| opendevreview | Elod Illes proposed openstack/project-config master: [release-tool] check-approval use only governance data https://review.opendev.org/c/openstack/project-config/+/989179 | 16:50 |
| fungi | frickler: mikal: the debian mirrors should be current again, and back to updating every 2 hours | 17:53 |
| stevebaker[m] | Hey all, we have a need in Ironic CI to have an ubuntu container image with custom packages (including PPA) installed to be available to pull during jobs. This is fallout from the canonical outages, we need something more robust than installing packages in a container image build in every job. I'm looking for guidance on the best way to publish this image and keep it up to date. Some existing quay.io repo? | 20:49 |
| clarkb | I assume the problem was the use of PPA packages more than anything else? (Since we have mirrors of ubuntu proper packages as do many others) | 20:55 |
| clarkb | is your idea to publish a container image with the packages preinstalled and then not update them as part of your build? If so then ya we use quay.io for our own container images and that seems to work well enough | 20:56 |
| stevebaker[m] | yes, specifically this image needs firefox, which is only available as a PPA in ubuntu | 20:56 |
| clarkb | fwiw if you just need a browser I think chromium is still a normal package on ubuntu but I haven't checked super recently | 20:58 |
| clarkb | alternatively you could use debian which doesn't put things like that into snaps | 20:58 |
| clarkb | also quay has its fair share of outages but they don't tend to be super long | 20:58 |
| stevebaker[m] | This feature is tied to firefox, the ironic community would prefer testing happens on ubuntu. Is there an existing opendev or openinfra repo on quay.io we can publish to or would we need to manage our own? | 21:02 |
| JayF | Today is the day you get to learn Ironic ships a firefox extension :D :-O | 21:02 |
| clarkb | you would need to manage your own | 21:02 |
| clarkb | opendev's quay orgs are for opendev things. Not for third parties to publish to | 21:03 |
| clarkb | but there are jobs and ansible roles that do most of the heavy lifting of actually publishing your images once you have a destination set up | 21:03 |
| clarkb | you can look at how opendev publishes its images for examples | 21:03 |
| clarkb | note that I don't actually think the OS platform matters much if you're testing and extension | 21:04 |
| clarkb | you could just install firefox from mozilla even (I do this on some machines) | 21:04 |
| clarkb | I have to pop out now and will be back in about 1.5-2 hours. But none of what you're describing sounds impossible. Just needs some work | 21:04 |
| stevebaker[m] | OK that gives us some things to ponder, thanks clarkb | 21:05 |
| cardoe | There's loci but it pushes to an org called "airshipit" for the airship project | 21:11 |
| cardoe | They also want things to remain airship-y | 21:11 |
| cardoe | I'd like to have something generic | 21:12 |
| cardoe | with PEP (something) the dependency-groups thing and standardizing the bindep profiles and groups in pyproject.toml and build isolation.... you can actually build a very thin container for projects that comply | 21:16 |
| cardoe | Using a default containerfile | 21:17 |
| fungi | similarly, the kolla folks publish their test images to a kolla org on some public regisry | 21:18 |
| cardoe | total aside... do you guys maintain the check-requirements job? And where does it live? | 22:23 |
| fungi | cardoe: i don't find any job named "check-requirements" defined, can you be more specific? | 22:37 |
| fungi | aha, itym "requirements-check" ? | 22:37 |
| fungi | there's also a "requirements-check-self" | 22:37 |
| cardoe | https://opendev.org/openstack/osc-lib/src/commit/feae2aef1119828645470b0a71805623dd7c517d/.zuul.yaml#L4 | 22:38 |
| fungi | that's a project-template, not a job | 22:38 |
| cardoe | Well https://review.opendev.org/c/openstack/requirements/+/989214 is doing what I was setting out to do | 22:39 |
| fungi | cardoe: the "check-requirements" project-template is, perhaps unsurprisingly, defined in the openstack/requirements repository: https://opendev.org/openstack/requirements/src/branch/master/.zuul.d/project-template.yaml#L1-L8 | 22:41 |
| fungi | though all it does is add the requirements-check job to both the check and gate pipelines | 22:41 |
| fungi | though that job is also defined in the same file, immediately below the project-template which includes it | 22:42 |
| fungi | cardoe: so anyway, if you need to make changes to the check-requirements project-template, the requirements-check job it includes, or that job's run-phase playbook and the role it encapsulates, they're all defined in that same repository as your existing change | 22:47 |
| fungi | should be able to do it all in the same change and it will be self-testing | 22:48 |
| cardoe | perfect | 22:51 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!