Closed joelsmith closed 2 years ago
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: joelsmith
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@joelsmith: The following tests failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
ci/prow/e2e-aws-olm | 9736140764751e79d5138e083effa12d48e74560 | link | true | /test e2e-aws-olm |
ci/prow/e2e-aws-operator | 9736140764751e79d5138e083effa12d48e74560 | link | true | /test e2e-aws-operator |
Full PR test history. Your PR dashboard.
Test fails when VPA operator deployment can't start its pods:
message: 'pods "vertical-pod-autoscaler-operator-6b586f464c-" is forbidden:
unable to validate against any security context constraint: [provider "anyuid":
Forbidden: not usable by user or serviceaccount, pod.metadata.annotations[container.seccomp.security.alpha.kubernetes.io/vertical-pod-autoscaler-operator]:
Forbidden: seccomp may not be set, provider "nonroot": Forbidden: not usable
by user or serviceaccount, provider "hostmount-anyuid": Forbidden: not usable
by user or serviceaccount, provider "machine-api-termination-handler": Forbidden:
not usable by user or serviceaccount, provider "hostnetwork": Forbidden: not
usable by user or serviceaccount, provider "hostaccess": Forbidden: not usable
by user or serviceaccount, provider "node-exporter": Forbidden: not usable
by user or serviceaccount, provider "privileged": Forbidden: not usable by
user or serviceaccount]'
The error message doesn't give any info on how it failed to validate against restricted
which is the SCC I would expect it to use.
@joelsmith: PR needs rebase.
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
@openshift-bot: Closed this PR.
This should fix warnings showing up in CI and operator logs. For example: