Closed joelsmith closed 3 years ago
@joelsmith: This pull request references Bugzilla bug 1974567, which is invalid:
Comment /bugzilla refresh
to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.
/bugzilla refresh
@joelsmith: This pull request references Bugzilla bug 1974567, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (schoudha@redhat.com), skipping review request.
@joelsmith: This pull request references Bugzilla bug 1974567, which is valid.
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (schoudha@redhat.com), skipping review request.
Chen, could you please take a look? /assign @wangchen615
/retest
Chen, could you please take a look? /assign @wangchen615
@joelsmith I see the log says the below:
Current deployments and pods:
NAME READY UP-TO-DATE AVAILABLE AGE
vertical-pod-autoscaler-operator 0/1 0 0 4m38s
No resources found in openshift-vertical-pod-autoscaler namespace.
I need to test it again on my local env to see what is the error for the not-ready deployment.
/retest
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: joelsmith, wangchen615
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@joelsmith: All pull requests linked via external trackers have merged:
Bugzilla bug 1974567 has been moved to the MODIFIED state.
According to https://bugzilla.redhat.com/show_bug.cgi?id=1805488, only components which must run before the SCC controller starts should use run-level 1. VPA is fine to run with the restricted SCC.