#9521 Critical path generation (still) broken
Opened a month ago by adamwill. Modified 16 days ago

I can't find an existing issue for this; please point me to it if there is one.

AFAICT, generation of the critical path is broken and has been for years. Bodhi uses PDC as its source of information as to what packages are in the critical path; the data in PDC is supposed to be generated and regularly updated based on what packages are in some specific comps groups, but that does not seem to be happening.

For e.g. the most recent change to the critpath groups in comps was this one in August, but if you ask PDC what's in critpath right now, xorg-x11-drv-amdgpu isn't there.

This is significant for me because openQA asks Bodhi if an update is critpath or not, and tests it if it is. So openQA is not testing updates for packages that have been added to the critpath since...whenever PDC was last updated...but it should be. I can whitelist 'missing' packages one at a time in openQA scheduling code, but it'd really be better if critpath generation worked.


Last change I can find before the xorg-x11-drv-amdgpu one was me adding dbus-broker in April 2019. That one does seem to have been applied.

@kevin says this may be getting done manually and not scripted, I always had the impression it was supposed to be automated/scripted, but maybe I'm wrong?

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: medium-gain, medium-trouble, ops

a month ago

We went with ops first as we need to update the current state and we should likely move it to dev once we've figured how to do it manually so we can automate it (sounds like a good toddler to do)

Metadata Update from @pingou:
- Issue untagged with: medium-gain, medium-trouble, ops
- Issue priority set to: Needs Review (was: Waiting on Assignee)

a month ago

Metadata Update from @pingou:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: medium-gain, medium-trouble, ops

a month ago

The gnome-shell/mutter focus bug I have been hitting just made me loose a nice long comment I put in here. :( Very fucking anoying.

Anyhow, to try and retype it:

This was to my understanding never automated. It's manually done by releng, and since it's not something thats listed as part of any cycle tasks it never gets done.

https://docs.pagure.org/releng/sop_update_critpath.html

So, perhaps we could make a toddler to do it, or perhaps we could add something to rawhide compose to do it daily then?

It's currently stored in pdc, but we really hope to kill pdc, so perhaps we should figure out where we might store this and then look at implementing the updating thing in the new location?

Note if we change it from being stored in PDC to somewhere else, at least Bodhi and the openQA scheduler will need updating to read it from the new place instead. Not sure if anything else reads it from PDC.

So, perhaps we could make a toddler to do it, or perhaps we could add something to rawhide compose to do it daily then?

This could be the easiest and simplest way forward for now.
We'll need a little more info to figure out what needs to be done though. Do we
have a link to the existing script to automate?

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog