Repository navigation
prowgen: gcs-credentials volume definition missing from vsphere02 periodic job specs #5113
Description
Activity
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close not-planned
@openshift-ci[bot]: Closing this issue, marking it as "Not Planned".
Details
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen.
Mark the issue as fresh by commenting/remove-lifecycle rotten.
Exclude this issue from closing again by commenting/lifecycle frozen./close not-planned
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
All prowgen-generated periodic jobs targeting the vsphere02 cluster include a gcs-credentials volumeMount in the ci-operator container but have no corresponding volume definition in the pod spec's volumes list.
Example affected jobs:
periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-vsphere-ipi-ovn-winc-f7
periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-vsphere-ipi-disconnected-ovn-winc-f28
(likely all vsphere02 periodic jobs generated by prowgen)
Jobs run successfully regardless, suggesting namespace-level secret injection on vsphere02 or a prowgen intentional omission. Worth investigating whether this is by design.
Surfaced in: #78004 / #78004 (comment)