fix e2e prometheus, operator-group, 4.11 errors#719
Conversation
ebcbdbe to
0688488
Compare
|
/retest |
fa0e83a to
b25665a
Compare
the prometheus secret based token will no longer exist from OCP 4.11 onwards. To get the prometheus token, we need to create the secret manually to get the token. this commit creates the prometheus robot secret which we then use to get the prometheus token.
In the OperatorGroup, as seen in [1,2], to catch up with the operator moving AllNamespaces support from true to false in installModes [3]. This avoids [4]: + oc get events LAST SEEN TYPE REASON OBJECT MESSAGE 10m Warning UnsupportedOperatorGroup clusterserviceversion/update-service-operator.v5.0.0 AllNamespaces InstallModeType not supported, cannot configure to watch all namespaces [1]: https://github.com/openshift/cincinnati-operator/blob/eed7a92a5efda96545e9be90a6ec65b427026d11/docs/disconnected-updateservice-operator.md#deploy-the-updateservice-operator [2]: https://github.com/openshift/cincinnati-operator/blob/eed7a92a5efda96545e9be90a6ec65b427026d11/tools/create-sub-group.sh#L23-L25 [3]: openshift/cincinnati-operator@1137a5c#diff-ef93a20b4f66d5fb3e6d84caf1169c43d4f750684fabd1a7c27065312dbb7fcdL73-R73 [4]: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/31237/rehearse-31237-pull-ci-openshift-cincinnati-master-e2e/1557865068975099904#1:build-log.txt%3A897-899
ae4e7cc to
9b3ef9f
Compare
update service operator had a breaking change where the policy engine URI was changed. this resulted in two different URIs for tests on 4.10 and 4.11 clusters. this changes makes sure we're getting the URI set by the operator, so same script can work for different versions of Update Service Operator
9b3ef9f to
7b1b9af
Compare
|
/retest |
|
/retest |
| # Expose services | ||
| PE_URL=$(oc get route e2e-policy-engine-route -o jsonpath='{.spec.host}') | ||
| export GRAPH_URL="https://${PE_URL}/api/upgrades_info/graph" | ||
| PE_URL=$(oc -n "${NAMESPACE}" get -o jsonpath='{.status.policyEngineURI}' updateservice "e2e") |
There was a problem hiding this comment.
could be a race here, if the controller hasn't populated the property yet. From our docs:
Use the following command to obtain a policy engine route:
$ while sleep 1; do POLICY_ENGINE_GRAPH_URI="$(oc -n "${NAMESPACE}" get -o jsonpath='{.status.policyEngineURI}/api/upgrades_info/v1/graph{"\n"}' updateservice "${NAME}")"; SCHEME="${POLICY_ENGINE_GRAPH_URI%%:*}"; if test "${SCHEME}" = http -o "${SCHEME}" = https; then break; fi; doneYou might need to poll until the command succeeds.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: PratikMahajan, wking The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@PratikMahajan: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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/test-infra repository. I understand the commands that are listed here. |
No description provided.