Skip to content
New issue

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

MGMT-8934: Day 2 Workers - Conformance #25752

Merged

Conversation

paul-maidment
Copy link
Contributor

@paul-maidment paul-maidment commented Jan 28, 2022

This test is a periodic test against OCP 4.11
These tests are running against an AWS instance of a single node cluster. Similar to the openshift-e2e-aws-single-node workflow.
This deploys an instance of single node and then adds a worker node to the cluster by scaling the replicas of a worker machineset, running the conformance tests after adding the node. After this, two
more nodes are added followed by another round of conformance tests.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 28, 2022
@paul-maidment
Copy link
Contributor Author

/test pj-rehearse

1 similar comment
@paul-maidment
Copy link
Contributor Author

/test pj-rehearse

@paul-maidment paul-maidment force-pushed the Paul_Omer_Testing_Branch branch 5 times, most recently from 87ca7bb to 6c5d483 Compare January 28, 2022 18:52
@paul-maidment
Copy link
Contributor Author

/test pj-rehearse

3 similar comments
@paul-maidment
Copy link
Contributor Author

/test pj-rehearse

@paul-maidment
Copy link
Contributor Author

/test pj-rehearse

@paul-maidment
Copy link
Contributor Author

/test pj-rehearse

@paul-maidment paul-maidment force-pushed the Paul_Omer_Testing_Branch branch 2 times, most recently from a1315a0 to 5f5a481 Compare January 31, 2022 22:18
@paul-maidment
Copy link
Contributor Author

/test pj-rehearse

1 similar comment
@paul-maidment
Copy link
Contributor Author

/test pj-rehearse

@paul-maidment paul-maidment force-pushed the Paul_Omer_Testing_Branch branch 11 times, most recently from 5c89e36 to 0b551ff Compare February 1, 2022 16:57
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 21, 2022
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 21, 2022
@omertuc
Copy link
Contributor

omertuc commented Feb 21, 2022

/lgtm

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

omertuc commented Feb 21, 2022

Results looking good, unholding

@omertuc
Copy link
Contributor

omertuc commented Feb 21, 2022

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 21, 2022
@omertuc
Copy link
Contributor

omertuc commented Feb 21, 2022

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 21, 2022
@omertuc
Copy link
Contributor

omertuc commented Feb 21, 2022

Sorry - forgot - we need a reporter_config entry for this job so we get Slack messages. @paul-maidment please add one, you can grep for #single-node-ci in this code base to see how it's done for other jobs

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 21, 2022
@omertuc
Copy link
Contributor

omertuc commented Feb 21, 2022

Looks like your recent push deleted all reporter_configs:
image

@paul-maidment paul-maidment force-pushed the Paul_Omer_Testing_Branch branch 2 times, most recently from bfabc96 to 91e4b6f Compare February 21, 2022 21:17
@@ -19031,7 +19031,7 @@ periodics:
- --confirm
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file is full of seemingly unrelated diffs, can you sort it out?

@paul-maidment paul-maidment force-pushed the Paul_Omer_Testing_Branch branch 3 times, most recently from 30e81b0 to 05a4ebb Compare February 21, 2022 21:31
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 21, 2022

@paul-maidment: 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/periodic-ci-openshift-release-master-nightly-4.11-e2e-aws-single-node-paul beb21aeb41cc19f1bd48ee4b44b86fb45eb63010 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.10-e2e-metal-ipi-serial-ovn-dualstack 5c89e36d98e66bf3cafb30cdbb05de17f9905d76 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.10-e2e-aws-csi 5c89e36d98e66bf3cafb30cdbb05de17f9905d76 link unknown /test pj-rehearse
ci/rehearse/openshift/oc/release-4.10/e2e-aws-upgrade 6b67a21ba55478e0fa3c766da89284583672af37 link unknown /test pj-rehearse
ci/rehearse/openshift/oc/release-4.10/e2e-aws-serial 6b67a21ba55478e0fa3c766da89284583672af37 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.10-e2e-azure-fips 37051fc2c42f316ae19dd7e4f6cf0312ba75a568 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.10-e2e-vsphere 37051fc2c42f316ae19dd7e4f6cf0312ba75a568 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.10-e2e-ovirt 37051fc2c42f316ae19dd7e4f6cf0312ba75a568 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.10-e2e-gcp-csi f34b9a2c51a3af520b5a34e80fdc93d9d0769c68 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.10-e2e-azurestack-csi c16748c5778ba33f5408c84e0b6ac4cac98baa5b link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.10-e2e-metal-single-node-live-iso 37051fc2c42f316ae19dd7e4f6cf0312ba75a568 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.10-e2e-metal-ipi-upgrade f34b9a2c51a3af520b5a34e80fdc93d9d0769c68 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.10-upgrade-from-stable-4.8-e2e-aws-upgrade-paused 3b68798cc9d3e9f47040c08a235412c71d1b835b link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.10-e2e-vsphere-ovn f34b9a2c51a3af520b5a34e80fdc93d9d0769c68 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.10-e2e-metal-ipi-virtualmedia c16748c5778ba33f5408c84e0b6ac4cac98baa5b link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.10-e2e-ovirt-csi 37051fc2c42f316ae19dd7e4f6cf0312ba75a568 link unknown /test pj-rehearse
ci/rehearse/openshift/release/master/nightly-4.10-images b3f179e1e541c45e779615246aa2541dd0172490 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.10-e2e-aws-single-node-with-workers 45e626ea300345e878808af6e930f905a9a57214 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.10-e2e-aws-single-node-worker ca80c3e9592f44fd0cf694eee7987413d627679f link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.9-e2e-aws-single-node-worker 70ad08b7e17ddd9d3dbd9e7efdc500b8249e5a3d link unknown /test pj-rehearse

Full PR test history. Your PR dashboard.

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.

This test is a periodic test against OCP 4.11
These tests are running against an AWS instance of a single node cluster. Similar to the openshift-e2e-aws-single-node workflow.
This deploys an instance of single node and then adds a worker node to the cluster by scaling the replicas of a worker machineset, running the conformance tests after adding the node. After this, two
more nodes are added followed by another round of conformance tests.
@omertuc
Copy link
Contributor

omertuc commented Feb 21, 2022

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 21, 2022
@omertuc
Copy link
Contributor

omertuc commented Feb 21, 2022

/lgtm

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

openshift-ci bot commented Feb 21, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: omertuc, paul-maidment, vrutkovs

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

The pull request process is described here

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-merge-robot openshift-merge-robot merged commit 53313b9 into openshift:master Feb 21, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 21, 2022

@paul-maidment: 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__nightly-4.11.yaml using file ci-operator/config/openshift/release/openshift-release-master__nightly-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 OWNERS using file ci-operator/step-registry/openshift/e2e/aws/single-node/workers/OWNERS
    • key openshift-e2e-aws-single-node-workers-workflow.metadata.json using file ci-operator/step-registry/openshift/e2e/aws/single-node/workers/openshift-e2e-aws-single-node-workers-workflow.metadata.json
    • key openshift-e2e-aws-single-node-workers-workflow.yaml using file ci-operator/step-registry/openshift/e2e/aws/single-node/workers/openshift-e2e-aws-single-node-workers-workflow.yaml
    • key OWNERS using file ci-operator/step-registry/single-node/add-worker/1/OWNERS
    • key single-node-add-worker-1-commands.sh using file ci-operator/step-registry/single-node/add-worker/1/single-node-add-worker-1-commands.sh
    • key single-node-add-worker-1-ref.metadata.json using file ci-operator/step-registry/single-node/add-worker/1/single-node-add-worker-1-ref.metadata.json
    • key single-node-add-worker-1-ref.yaml using file ci-operator/step-registry/single-node/add-worker/1/single-node-add-worker-1-ref.yaml
    • key OWNERS using file ci-operator/step-registry/single-node/add-worker/2/OWNERS
    • key single-node-add-worker-2-commands.sh using file ci-operator/step-registry/single-node/add-worker/2/single-node-add-worker-2-commands.sh
    • key single-node-add-worker-2-ref.metadata.json using file ci-operator/step-registry/single-node/add-worker/2/single-node-add-worker-2-ref.metadata.json
    • key single-node-add-worker-2-ref.yaml using file ci-operator/step-registry/single-node/add-worker/2/single-node-add-worker-2-ref.yaml
    • key OWNERS using file ci-operator/step-registry/single-node/add-worker/3/OWNERS
    • key single-node-add-worker-3-commands.sh using file ci-operator/step-registry/single-node/add-worker/3/single-node-add-worker-3-commands.sh
    • key single-node-add-worker-3-ref.metadata.json using file ci-operator/step-registry/single-node/add-worker/3/single-node-add-worker-3-ref.metadata.json
    • key single-node-add-worker-3-ref.yaml using file ci-operator/step-registry/single-node/add-worker/3/single-node-add-worker-3-ref.yaml
    • key OWNERS using file ci-operator/step-registry/single-node/add-worker/OWNERS
    • key OWNERS using file ci-operator/step-registry/single-node/e2e/test/2/OWNERS
    • key single-node-e2e-test-2-commands.sh using file ci-operator/step-registry/single-node/e2e/test/2/single-node-e2e-test-2-commands.sh
    • key single-node-e2e-test-2-ref.metadata.json using file ci-operator/step-registry/single-node/e2e/test/2/single-node-e2e-test-2-ref.metadata.json
    • key single-node-e2e-test-2-ref.yaml using file ci-operator/step-registry/single-node/e2e/test/2/single-node-e2e-test-2-ref.yaml

In response to this:

This test is a periodic test against OCP 4.11
These tests are running against an AWS instance of a single node cluster. Similar to the openshift-e2e-aws-single-node workflow.
This deploys an instance of single node and then adds a worker node to the cluster by scaling the replicas of a worker machineset, running the conformance tests after adding the node. After this, two
more nodes are added followed by another round of conformance tests.

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.

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
6 participants