Skip to content

Add support to the step registry for the openshift-sdn modes #8157

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

Merged
merged 1 commit into from
Apr 23, 2020

Conversation

pecameron
Copy link
Contributor

@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 6, 2020
@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 7, 2020
@pecameron
Copy link
Contributor Author

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 7, 2020
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 7, 2020
@pecameron pecameron force-pushed the sdn858 branch 6 times, most recently from b2d2fbe to 5cb2bfd Compare April 8, 2020 13:15
@@ -0,0 +1,11 @@
approvers:
Copy link
Contributor

Choose a reason for hiding this comment

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

@pecameron let's put network people in here

@dcbw
Copy link
Contributor

dcbw commented Apr 8, 2020

@pecameron take a look at PR #8075 which is what I think you should follow here. Basically, add a workflow like https://github.com/openshift/release/pull/8075/files#diff-7e9e1262c023bd4b0886f0a5e0ad5231 that does the ipi-conf-aws, then drops a manifest file that sets the right OpenShiftSDN network mode, then continues the install and runs the e2e tests.

@pecameron pecameron force-pushed the sdn858 branch 3 times, most recently from 45e8bae to e4ef3dd Compare April 9, 2020 19:45
@pecameron
Copy link
Contributor Author

/retest

@pecameron pecameron changed the title [WIP]Add support to the step registry for the openshift-sdn modes Add support to the step registry for the openshift-sdn modes Apr 13, 2020
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 13, 2020
@pecameron
Copy link
Contributor Author

@dcbw passing tests. Anything else before merge?

@pecameron
Copy link
Contributor Author

@stevekuznetsov @wking Is there more to do for this PR? PTAL

@@ -0,0 +1,10 @@
ref:
as: sdn-conf-multi-manifest
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't know if this is a big deal but it might be cleaer to change this to sdn-conf-multitenant-manifest? it might be clearer if we ever need to create many manifests in the future

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was keeping the length of the filename down.

@pecameron
Copy link
Contributor Author

/assign stevekuznetsov

@pecameron
Copy link
Contributor Author

/assign @stevekuznetsov

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 17, 2020
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 20, 2020
@pecameron
Copy link
Contributor Author

Rebased

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Apr 20, 2020

@pecameron: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/rehearse/openshift/cluster-network-operator/master/e2e-sdn-step-registry 45e8baeab7416f059296450a440c5d9ff027c10a link /test pj-rehearse
ci/rehearse/openshift/cluster-network-operator/master/e2e-gcp-upgrade ec403d7635b13aafdeadf97599242b8d510c0490 link /test pj-rehearse
ci/rehearse/cri-o/cri-o/release-1.13/e2e-aws e0886ec573b0b348bb221ebe63a270da64aa5aef link /test pj-rehearse
ci/rehearse/openshift/cluster-network-operator/master/e2e-ovn-hybrid-step-registry e0886ec573b0b348bb221ebe63a270da64aa5aef link /test pj-rehearse
ci/rehearse/openshift/cluster-network-operator/master/e2e-aws-sdn-multi-step-registry e0f04b803b8562e080593d4a2cc49bc2a0f1b07f link /test pj-rehearse
ci/rehearse/openshift/cluster-network-operator/master/e2e-aws-sdn-single-step-registry e0f04b803b8562e080593d4a2cc49bc2a0f1b07f link /test pj-rehearse

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

@pecameron
Copy link
Contributor Author

/retest

@dcbw
Copy link
Contributor

dcbw commented Apr 21, 2020

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 21, 2020
@dcbw
Copy link
Contributor

dcbw commented Apr 21, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 21, 2020
@pecameron
Copy link
Contributor Author

@dcbw @stevekuznetsov @wking This didin't get merged 4/17. A merge ahead of it forced a rebase. Can this be merged now?

@pecameron
Copy link
Contributor Author

@stevekuznetsov @dcbw Is there anything holding up getting this merged?

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dcbw, pecameron, stevekuznetsov

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-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 23, 2020
@openshift-merge-robot openshift-merge-robot merged commit 12082ad into openshift:master Apr 23, 2020
@openshift-ci-robot
Copy link
Contributor

@pecameron: Updated the following 7 configmaps:

  • step-registry configmap in namespace ci at cluster app.ci using the following files:
    • key OWNERS using file ci-operator/step-registry/origin/e2e-aws-sdn-multi/OWNERS
    • key origin-e2e-aws-sdn-multi-workflow.yaml using file ci-operator/step-registry/origin/e2e-aws-sdn-multi/origin-e2e-aws-sdn-multi-workflow.yaml
    • key OWNERS using file ci-operator/step-registry/origin/e2e-aws-sdn-single/OWNERS
    • key origin-e2e-aws-sdn-single-workflow.yaml using file ci-operator/step-registry/origin/e2e-aws-sdn-single/origin-e2e-aws-sdn-single-workflow.yaml
    • key OWNERS using file ci-operator/step-registry/sdn/OWNERS
    • key OWNERS using file ci-operator/step-registry/sdn/conf/OWNERS
    • key OWNERS using file ci-operator/step-registry/sdn/conf/multi-manifest/OWNERS
    • key sdn-conf-multi-manifest-commands.sh using file ci-operator/step-registry/sdn/conf/multi-manifest/sdn-conf-multi-manifest-commands.sh
    • key sdn-conf-multi-manifest-ref.yaml using file ci-operator/step-registry/sdn/conf/multi-manifest/sdn-conf-multi-manifest-ref.yaml
    • key sdn-conf-commands.sh using file ci-operator/step-registry/sdn/conf/sdn-conf-commands.sh
    • key sdn-conf-ref.yaml using file ci-operator/step-registry/sdn/conf/sdn-conf-ref.yaml
    • key OWNERS using file ci-operator/step-registry/sdn/conf/single-manifest/OWNERS
    • key sdn-conf-single-manifest-commands.sh using file ci-operator/step-registry/sdn/conf/single-manifest/sdn-conf-single-manifest-commands.sh
    • key sdn-conf-single-manifest-ref.yaml using file ci-operator/step-registry/sdn/conf/single-manifest/sdn-conf-single-manifest-ref.yaml
  • step-registry configmap in namespace ci at cluster api.ci using the following files:
    • key OWNERS using file ci-operator/step-registry/origin/e2e-aws-sdn-multi/OWNERS
    • key origin-e2e-aws-sdn-multi-workflow.yaml using file ci-operator/step-registry/origin/e2e-aws-sdn-multi/origin-e2e-aws-sdn-multi-workflow.yaml
    • key OWNERS using file ci-operator/step-registry/origin/e2e-aws-sdn-single/OWNERS
    • key origin-e2e-aws-sdn-single-workflow.yaml using file ci-operator/step-registry/origin/e2e-aws-sdn-single/origin-e2e-aws-sdn-single-workflow.yaml
    • key OWNERS using file ci-operator/step-registry/sdn/OWNERS
    • key OWNERS using file ci-operator/step-registry/sdn/conf/OWNERS
    • key OWNERS using file ci-operator/step-registry/sdn/conf/multi-manifest/OWNERS
    • key sdn-conf-multi-manifest-commands.sh using file ci-operator/step-registry/sdn/conf/multi-manifest/sdn-conf-multi-manifest-commands.sh
    • key sdn-conf-multi-manifest-ref.yaml using file ci-operator/step-registry/sdn/conf/multi-manifest/sdn-conf-multi-manifest-ref.yaml
    • key sdn-conf-commands.sh using file ci-operator/step-registry/sdn/conf/sdn-conf-commands.sh
    • key sdn-conf-ref.yaml using file ci-operator/step-registry/sdn/conf/sdn-conf-ref.yaml
    • key OWNERS using file ci-operator/step-registry/sdn/conf/single-manifest/OWNERS
    • key sdn-conf-single-manifest-commands.sh using file ci-operator/step-registry/sdn/conf/single-manifest/sdn-conf-single-manifest-commands.sh
    • key sdn-conf-single-manifest-ref.yaml using file ci-operator/step-registry/sdn/conf/single-manifest/sdn-conf-single-manifest-ref.yaml
  • ci-operator-master-configs configmap in namespace ci at cluster ci/api-build01-ci-devcluster-openshift-com:6443 using the following files:
    • key openshift-cluster-network-operator-master.yaml using file ci-operator/config/openshift/cluster-network-operator/openshift-cluster-network-operator-master.yaml
  • ci-operator-master-configs configmap in namespace ci at cluster api.ci using the following files:
    • key openshift-cluster-network-operator-master.yaml using file ci-operator/config/openshift/cluster-network-operator/openshift-cluster-network-operator-master.yaml
  • ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-cluster-network-operator-master.yaml using file ci-operator/config/openshift/cluster-network-operator/openshift-cluster-network-operator-master.yaml
  • job-config-master configmap in namespace ci at cluster api.ci using the following files:
    • key openshift-cluster-network-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-network-operator/openshift-cluster-network-operator-master-presubmits.yaml
  • job-config-master configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-cluster-network-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-network-operator/openshift-cluster-network-operator-master-presubmits.yaml

In response to this:

https://issues.redhat.com/browse/SDN-858

Signed-off-by: Phil Cameron [email protected]

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.

@pecameron pecameron deleted the sdn858 branch April 24, 2020 12:47
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.

7 participants