Skip to content

Conversation

@wking
Copy link
Member

@wking wking commented Feb 26, 2022

Installing a cluster using the new knobs the installer grew in openshift/installer#5645.

@openshift-ci openshift-ci bot requested review from dgoodwin and droslean February 26, 2022 07:19
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 26, 2022
@wking wking force-pushed the cvo-capabilities branch 2 times, most recently from b95bb01 to ebefd59 Compare February 26, 2022 07:25
@wking
Copy link
Member Author

wking commented Feb 26, 2022

no-capabilities:

INFO[2022-02-26T07:27:52Z] Resolved release initial to registry.ci.openshift.org/ocp/release:4.11.0-0.nightly-2022-02-23-185405
...
level=fatal msg=failed to fetch Master Machines: failed to load asset "Install Config": failed to unmarshal install-config.yaml: failed to parse first occurence of unknown field: error unmarshaling JSON: while decoding JSON: json: unknown field "capabilities"

So we'll want to wait for a few nightlies to be accepted before they pick up openshift/installer#5645 and we can confirm this is working.

@wking wking force-pushed the cvo-capabilities branch 2 times, most recently from 28fd681 to d47812b Compare March 3, 2022 05:45
@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 3, 2022
@wking wking force-pushed the cvo-capabilities branch from d47812b to 44c0c66 Compare March 3, 2022 05:48
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 3, 2022
@wking
Copy link
Member Author

wking commented Mar 3, 2022

e2e-aws-no-capabilities failed on the gather-aws-console step with:

Gathering console logs for i-060395fe12cd09648

An error occurred (RequestLimitExceeded) when calling the GetConsoleOutput operation (reached max retries: 2): Request limit exceeded.
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"k8s.io/test-infra/prow/entrypoint/run.go:80","func":"k8s.io/test-infra/prow/entrypoint.Options.Run","level":"error","msg":"Error executing test process","severity":"error","time":"2022-03-03T07:00:56Z"}
error: failed to execute wrapped command: exit status 1

That's sounds like AWS-side throttling or something. But certainly not a cluster-under-test issue. And hooray, our spec property is all set up:

$ curl -s https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_release/26597/rehearse-26597-periodic-ci-openshift-release-master-ci-4.11-e2e-aws-no-capabilities/1499260995871182848/artifacts/e2e-aws-no-capabilities/gather-extra/artifacts/clusterversion.json | jq -r '.items[].spec'
{
  "capabilities": {
    "baselineCapabilitySet": "None"
  },
  "clusterID": "bacdbde4-dd63-4d8f-87e5-7284c9ece340"
}

So I think we're set to merge here.

@dgoodwin
Copy link
Contributor

dgoodwin commented Mar 3, 2022

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 3, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgoodwin, wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2022

@wking: 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/rehearse/openshift/alibaba-disk-csi-driver-operator/release-4.11/e2e-alibabacloud-disk-csi ebefd591b68b7987cefb7d51dfd2a3f02fec50cb link unknown /test pj-rehearse
ci/rehearse/openshift/cluster-etcd-operator/release-4.9/e2e-gcp-disruptive-ovn ebefd591b68b7987cefb7d51dfd2a3f02fec50cb link unknown /test pj-rehearse
ci/rehearse/openshift/openshift-controller-manager/release-4.12/openshift-e2e-aws-builds-techpreview ebefd591b68b7987cefb7d51dfd2a3f02fec50cb link unknown /test pj-rehearse
ci/rehearse/openshift/cluster-cloud-controller-manager-operator/release-4.9/e2e-azure-ccm ebefd591b68b7987cefb7d51dfd2a3f02fec50cb link unknown /test pj-rehearse
ci/prow/pj-rehearse 44c0c66 link false /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.11-e2e-aws-no-capabilities 44c0c66 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-ovn-kubernetes-release-4.12-e2e-ibmcloud-ipi-ovn-periodic 44c0c66 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.11-e2e-aws-no-capabilities 28fd68105ec870e73a7bc4cbc746e081680261f9 link unknown /test pj-rehearse
ci/rehearse/openshift/origin/release-4.9/e2e-aws-disruptive 44c0c66 link unknown /test pj-rehearse
ci/rehearse/openshift/origin/release-4.1/e2e-aws-builds 44c0c66 link unknown /test pj-rehearse
ci/rehearse/openshift/origin/release-4.5/e2e-aws-csi 44c0c66 link unknown /test pj-rehearse
ci/rehearse/openshift/origin/release-4.2/e2e-cmd 44c0c66 link unknown /test pj-rehearse

Full PR test history. Your PR dashboard.

Details

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/test-infra repository. I understand the commands that are listed here.

@openshift-ci openshift-ci bot merged commit 7b5ae7c into openshift:master Mar 3, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2022

@wking: Updated the following 3 configmaps:

  • ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-release-master__ci-4.11.yaml using file ci-operator/config/openshift/release/openshift-release-master__ci-4.11.yaml
  • job-config-master-periodics configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-release-master-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-master-periodics.yaml
  • step-registry configmap in namespace ci at cluster app.ci using the following files:
    • key ipi-conf-commands.sh using file ci-operator/step-registry/ipi/conf/ipi-conf-commands.sh
    • key ipi-conf-ref.yaml using file ci-operator/step-registry/ipi/conf/ipi-conf-ref.yaml
Details

In response to this:

Installing a cluster using the new knobs the installer grew in openshift/installer#5645.

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/test-infra repository.

@wking wking deleted the cvo-capabilities branch March 3, 2022 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants