We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In the test "test_resize_osd_when_capacity_near_full" we use the benchmark-operator fixture. In the recent tests the benchmark-controller-manager pod failed to reach the Running state. See, for example, the test: https://reportportal-ocs4.apps.ocp-c1.prod.psi.redhat.com/ui/#ocs/launches/738/26643/1314478/1314507/log
benchmark-operator
The text was updated successfully, but these errors were encountered:
Tested locally on ibmcloud and it is working as expected
$ git clone [email protected]:cloud-bulldozer/benchmark-operator.git Cloning into 'benchmark-operator'... remote: Enumerating objects: 8397, done. remote: Counting objects: 100% (319/319), done. remote: Compressing objects: 100% (166/166), done. remote: Total 8397 (delta 140), reused 260 (delta 123), pack-reused 8078 (from 1) Receiving objects: 100% (8397/8397), 9.69 MiB | 5.68 MiB/s, done. Resolving deltas: 100% (5419/5419), done. oviner~/test$ cd benchmark-operator/ oviner~/test/benchmark-operator(master)$ make deploy IMG=quay.io/ocsci/benchmark-operator:testing cd config/manager && /home/oviner/test/benchmark-operator/bin/kustomize edit set image controller=quay.io/ocsci/benchmark-operator:testing /home/oviner/test/benchmark-operator/bin/kustomize build config/default | kubectl apply -f - namespace/benchmark-operator created customresourcedefinition.apiextensions.k8s.io/benchmarks.ripsaw.cloudbulldozer.io created serviceaccount/benchmark-operator created clusterrolebinding.rbac.authorization.k8s.io/benchmark-operator-binding created configmap/benchmark-manager-config created deployment.apps/benchmark-controller-manager created oviner~/test/benchmark-operator(master)$ kubectl get pods -n benchmark-operator NAME READY STATUS RESTARTS AGE benchmark-controller-manager-646d45bc5d-cmt5q 0/2 ContainerCreating 0 14s oviner~/test/benchmark-operator(master)$ kubectl get pods -n benchmark-operator -w NAME READY STATUS RESTARTS AGE benchmark-controller-manager-646d45bc5d-cmt5q 2/2 Running 0 16s
Sorry, something went wrong.
No branches or pull requests
In the test "test_resize_osd_when_capacity_near_full" we use the
benchmark-operator
fixture. In the recent tests the benchmark-controller-manager pod failed to reach the Running state. See, for example, the test: https://reportportal-ocs4.apps.ocp-c1.prod.psi.redhat.com/ui/#ocs/launches/738/26643/1314478/1314507/logThe text was updated successfully, but these errors were encountered: