While watching a long-running release, I noticed that the push-rpms-data-to-pyxis task sat there pending for 20 minutes. I worried something was wrong, so I looked in the events logs and found that it was prohibited from attaching to the pvc that it wanted because another task in the same pipeline was currently using it (the rh-sign-image-cosign task. They would otherwise be able to run in parallel, but one was stopped waiting for the other.
Can anything be done to decrease use or dependence on the shared pvc? Can some tasks use the volume in a read-only capacity that allows multi-attach?
While watching a long-running release, I noticed that the push-rpms-data-to-pyxis task sat there pending for 20 minutes. I worried something was wrong, so I looked in the events logs and found that it was prohibited from attaching to the pvc that it wanted because another task in the same pipeline was currently using it (the rh-sign-image-cosign task. They would otherwise be able to run in parallel, but one was stopped waiting for the other.
Can anything be done to decrease use or dependence on the shared pvc? Can some tasks use the volume in a read-only capacity that allows multi-attach?