Skip to content

enable configuring 'single-node' variant #14556

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.

Sign up for GitHub

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

Jump to bottom
Merged
openshift-merge-robot merged 1 commit into from
Jan 6, 2021
Merged

enable configuring 'single-node' variant #14556

openshift-merge-robot merged 1 commit into from
Jan 6, 2021

Conversation

@osherdp
Copy link
Contributor

@osherdp osherdp commented Jan 3, 2021 •
edited
Loading

Using 1 master+worker node in SNO (Single Node Openshift) cluster installation.

@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 Jan 3, 2021
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 3, 2021

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@osherdp
Copy link
Contributor Author

osherdp commented Jan 3, 2021

/test all

1 similar comment
@osherdp
Copy link
Contributor Author

osherdp commented Jan 3, 2021

/test all

@osherdp
Copy link
Contributor Author

osherdp commented Jan 3, 2021

/test ?

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 3, 2021

@osherdp: The following commands are available to trigger jobs:

  • /test app-ci-config-dry
  • /test boskos-config
  • /test boskos-config-generation
  • /test build01-dry
  • /test build02-dry
  • /test ci-operator-config
  • /test ci-operator-config-metadata
  • /test ci-operator-registry
  • /test ci-testgrid-allow-list
  • /test config
  • /test core-dry
  • /test core-valid
  • /test correctly-sharded-config
  • /test deprecate-templates
  • /test generated-config
  • /test generated-dashboards
  • /test ordered-prow-config
  • /test owners
  • /test pj-rehearse
  • /test prow-config
  • /test prow-config-filenames
  • /test prow-config-semantics
  • /test release-config
  • /test release-controller-config
  • /test secret-generator-config-valid
  • /test services-dry
  • /test services-valid
  • /test step-registry-metadata
  • /test step-registry-shellcheck
  • /test vsphere-dry
  • /test pylint
  • /test yamllint

Use /test all to run the following jobs:

  • pull-ci-openshift-release-master-app-ci-config-dry
  • pull-ci-openshift-release-master-boskos-config
  • pull-ci-openshift-release-master-boskos-config-generation
  • pull-ci-openshift-release-master-build01-dry
  • pull-ci-openshift-release-master-build02-dry
  • pull-ci-openshift-release-master-ci-operator-config
  • pull-ci-openshift-release-master-ci-operator-config-metadata
  • pull-ci-openshift-release-master-ci-operator-registry
  • pull-ci-openshift-release-master-config
  • pull-ci-openshift-release-master-core-dry
  • pull-ci-openshift-release-master-core-valid
  • pull-ci-openshift-release-master-correctly-sharded-config
  • pull-ci-openshift-release-master-deprecate-templates
  • pull-ci-openshift-release-master-generated-config
  • pull-ci-openshift-release-master-generated-dashboards
  • pull-ci-openshift-release-master-ordered-prow-config
  • pull-ci-openshift-release-master-owners
  • pull-ci-openshift-release-master-pj-rehearse
  • pull-ci-openshift-release-master-prow-config
  • pull-ci-openshift-release-master-prow-config-filenames
  • pull-ci-openshift-release-master-prow-config-semantics
  • pull-ci-openshift-release-master-release-config
  • pull-ci-openshift-release-master-release-controller-config
  • pull-ci-openshift-release-master-secret-generator-config-valid
  • pull-ci-openshift-release-master-services-dry
  • pull-ci-openshift-release-master-services-valid
  • pull-ci-openshift-release-master-step-registry-metadata
  • pull-ci-openshift-release-master-step-registry-shellcheck
  • pull-ci-openshift-release-master-vsphere-dry
  • pull-ci-openshift-release-yamllint
Details

In response to this:

/test ?

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.

@osherdp
Copy link
Contributor Author

osherdp commented Jan 3, 2021

/test pj-rehearse

@osherdp
Copy link
Contributor Author

osherdp commented Jan 3, 2021

/test pj-rehearse

1 similar comment
@osherdp
Copy link
Contributor Author

osherdp commented Jan 3, 2021

/test pj-rehearse

@osherdp
Copy link
Contributor Author

osherdp commented Jan 3, 2021

/test pj-rehearse

@osherdp
Copy link
Contributor Author

osherdp commented Jan 3, 2021

/test pj-rehearse

@osherdp osherdp force-pushed the test/e2e-sno-aws branch 2 times, most recently from 6791963 to 2d1c8dd Compare January 3, 2021 12:57
@osherdp
Copy link
Contributor Author

osherdp commented Jan 3, 2021

/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 Jan 3, 2021
@osherdp osherdp marked this pull request as ready for review January 3, 2021 12:57
@osherdp osherdp changed the title WIP: enable configuring SNO platform enable configuring 'sno' variant Jan 3, 2021
@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 Jan 3, 2021
@osherdp osherdp mentioned this pull request Jan 3, 2021
Merged
@osherdp
Copy link
Contributor Author

osherdp commented Jan 3, 2021

/cc @eranco74 @romfreiman

@eranco74
Copy link
Contributor

eranco74 commented Jan 3, 2021

/lgtm

smarterclayton
smarterclayton reviewed Jan 5, 2021
View reviewed changes
@smarterclayton smarterclayton changed the title enable configuring 'sno' variant enable configuring 'single-node' variant Jan 5, 2021
@osherdp osherdp requested a review from smarterclayton January 5, 2021 20:18
@osherdp
Copy link
Contributor Author

osherdp commented Jan 5, 2021

/retest

@romfreiman
Copy link

romfreiman commented Jan 5, 2021

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 5, 2021
@romfreiman
Copy link

romfreiman commented Jan 5, 2021

/retest

@osherdp
Copy link
Contributor Author

osherdp commented Jan 5, 2021

/test pj-rehearse

@osherdp
Copy link
Contributor Author

osherdp commented Jan 6, 2021

/test e2e-gcp-ovn

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 6, 2021

@osherdp: The specified target(s) for /test were not found.
The following commands are available to trigger jobs:

  • /test app-ci-config-dry
  • /test boskos-config
  • /test boskos-config-generation
  • /test build01-dry
  • /test build02-dry
  • /test ci-operator-config
  • /test ci-operator-config-metadata
  • /test ci-operator-registry
  • /test ci-testgrid-allow-list
  • /test config
  • /test core-dry
  • /test core-valid
  • /test correctly-sharded-config
  • /test deprecate-templates
  • /test generated-config
  • /test generated-dashboards
  • /test ordered-prow-config
  • /test owners
  • /test pj-rehearse
  • /test prow-config
  • /test prow-config-filenames
  • /test prow-config-semantics
  • /test release-config
  • /test release-controller-config
  • /test secret-generator-config-valid
  • /test services-dry
  • /test services-valid
  • /test step-registry-metadata
  • /test step-registry-shellcheck
  • /test vsphere-dry
  • /test pylint
  • /test yamllint

Use /test all to run the following jobs:

  • pull-ci-openshift-release-master-app-ci-config-dry
  • pull-ci-openshift-release-master-boskos-config
  • pull-ci-openshift-release-master-boskos-config-generation
  • pull-ci-openshift-release-master-build01-dry
  • pull-ci-openshift-release-master-build02-dry
  • pull-ci-openshift-release-master-ci-operator-config
  • pull-ci-openshift-release-master-ci-operator-config-metadata
  • pull-ci-openshift-release-master-ci-operator-registry
  • pull-ci-openshift-release-master-config
  • pull-ci-openshift-release-master-core-dry
  • pull-ci-openshift-release-master-core-valid
  • pull-ci-openshift-release-master-correctly-sharded-config
  • pull-ci-openshift-release-master-deprecate-templates
  • pull-ci-openshift-release-master-generated-config
  • pull-ci-openshift-release-master-generated-dashboards
  • pull-ci-openshift-release-master-ordered-prow-config
  • pull-ci-openshift-release-master-owners
  • pull-ci-openshift-release-master-pj-rehearse
  • pull-ci-openshift-release-master-prow-config
  • pull-ci-openshift-release-master-prow-config-filenames
  • pull-ci-openshift-release-master-prow-config-semantics
  • pull-ci-openshift-release-master-release-config
  • pull-ci-openshift-release-master-release-controller-config
  • pull-ci-openshift-release-master-secret-generator-config-valid
  • pull-ci-openshift-release-master-services-dry
  • pull-ci-openshift-release-master-services-valid
  • pull-ci-openshift-release-master-step-registry-metadata
  • pull-ci-openshift-release-master-step-registry-shellcheck
  • pull-ci-openshift-release-master-vsphere-dry
  • pull-ci-openshift-release-yamllint
Details

In response to this:

/test e2e-gcp-ovn

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.

@osherdp
Copy link
Contributor Author

osherdp commented Jan 6, 2021

/retest

@osherdp
Copy link
Contributor Author

osherdp commented Jan 6, 2021

/test pj-rehearse

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 6, 2021

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

Test name Commit Details Rerun command
ci/rehearse/kubevirt/ssp-operator/master/e2e-functests b22139556d053160f37570369022abe00f981b0f link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-gcp-shared-vpc b22139556d053160f37570369022abe00f981b0f link /test pj-rehearse
ci/rehearse/openshift/cluster-etcd-operator/master/e2e-disruptive 7ef737e2bacf2f9b3135c59790031577f4d66dd7 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-aws-sno 89e1debcf85a7f2127bd2b8814d1a76b477fe4f2 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-aws-single-node 72a807f link /test pj-rehearse
ci/prow/pj-rehearse 72a807f link /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-merge-robot
Copy link
Contributor

openshift-merge-robot commented Jan 6, 2021

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

Test name Commit Details Rerun command
ci/rehearse/kubevirt/ssp-operator/master/e2e-functests b22139556d053160f37570369022abe00f981b0f link /test pj-rehearse
ci/prow/pj-rehearse 72a807f link /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.

@osherdp
Copy link
Contributor Author

osherdp commented Jan 6, 2021

@smarterclayton @romfreiman all should be good now
tell me if anything else needed

@smarterclayton
Copy link
Contributor

smarterclayton commented Jan 6, 2021

/lgtm

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 6, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eranco74, osherdp, pierreprinetti, romfreiman, smarterclayton

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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 6, 2021
@openshift-bot
Copy link
Contributor

openshift-bot commented Jan 6, 2021

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 3b13ef8 into openshift:master Jan 6, 2021
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 6, 2021

@osherdp: Updated the following 7 configmaps:

  • job-config-master configmap in namespace ci at cluster api.ci using the following files:
    • key openshift-installer-master-presubmits.yaml using file ci-operator/jobs/openshift/installer/openshift-installer-master-presubmits.yaml
  • job-config-master configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-installer-master-presubmits.yaml using file ci-operator/jobs/openshift/installer/openshift-installer-master-presubmits.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster vsphere using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster api.ci using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster app.ci using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster build01 using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster build02 using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
Details

In response to this:

Using 1 master+worker node in SNO (Single Node Openshift) cluster installation.

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.

This was referenced Jan 11, 2021
Merged
Merged
Merged
Merged
@omertuc omertuc mentioned this pull request Jan 24, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jstuever jstuever Awaiting requested review from jstuever

@mtnbikenc mtnbikenc Awaiting requested review from mtnbikenc

@eranco74 eranco74 Awaiting requested review from eranco74

@romfreiman romfreiman Awaiting requested review from romfreiman

@smarterclayton smarterclayton Awaiting requested review from smarterclayton

Assignees

@smarterclayton smarterclayton

@pierreprinetti pierreprinetti

@romfreiman romfreiman

@eranco74 eranco74

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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

8 participants

@osherdp @openshift-ci-robot @eranco74 @romfreiman @pierreprinetti @openshift-merge-robot @smarterclayton @openshift-bot