Problem:
I have a rolling content view that is nearing obsolescence that I want to delete. I get a surprising error when trying to delete it.
Expected outcome:
The content view is deleted
Foreman and Proxy versions:
3.16.0
Foreman and Proxy plugin versions:
Katello 4.18.0
Distribution and version:
CentOS 9-Stream
Other relevant data:
No tasks appear to actually be running:
This is the status of the task in question:
Note: after a reboot the task status changed and I could delete the content view. Unclear why the task got into a funky state
Hi @mhjacks ,
Glad to hear at least the reboot allowed for the CV to be deleted. Are you able to find the error you originally saw?
@aruzicka , the “planned/pending” status looks a bit strange to me considering the task is at 100%, especially considering that a service restart caused it. Any concerns there?
I’m not seeing the original error anymore. In the second screenshot, the task shows “pending” and 100% which seems like it might be relevant.
Not captured in the initial report: the “normal” morning sync for that repo (the Google Chrome repo) reported incomplete, so I manually re-ran it. The task that resulted and blocked CV deletion was the result of that.
I wasn’t expecting the reboot to clear the issue. c9s got new kernel and glibc overnight, that’s why I rebooted.
Changed from what we see in the screenshots to …?
Hard to say, service restarts when things are running are always a bit iffy. In error situations like this, tasks and dynflow can go out of sync, so hard to say what this actually means without seeing things from dynflow’s point of view.
