Skip to content

Conversation

@sallyom
Copy link
Contributor

@sallyom sallyom commented Oct 14, 2020

Picking up @praveenkumar 's PR to rebase/test/add ssh config vars

@sallyom sallyom force-pushed the praveen-libvirt-workflow branch 6 times, most recently from ea60e09 to a7dd46b Compare October 15, 2020 03:03
@sallyom sallyom force-pushed the praveen-libvirt-workflow branch 13 times, most recently from af2574b to f5154ce Compare October 16, 2020 17:39
@sallyom
Copy link
Contributor Author

sallyom commented Oct 16, 2020

@praveenkumar it's ready!! I added the same set of tests that are currently running in the openshift/installer libvirt-e2e job.
ptal, let's get this merged! thanks :)

@sallyom
Copy link
Contributor Author

sallyom commented Oct 19, 2020

@praveenkumar , after this merges, we can look at replacing the custom image with a provision script within the upi-gcp-nested-pre workflow.

@praveenkumar
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 20, 2020
@praveenkumar
Copy link
Contributor

/assign @abhinavdahiya

praveenkumar and others added 3 commits October 20, 2020 09:50
- move libvirt workflow under openshift/e2e/gcp
- add ServerAlive vars to ssh config
- configure list of e2es to run
- extract openshift-tests
@sallyom sallyom force-pushed the praveen-libvirt-workflow branch from f5154ce to b002981 Compare October 20, 2020 14:09
@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Oct 20, 2020
@sallyom
Copy link
Contributor Author

sallyom commented Oct 20, 2020

thanks for the review @wking, updated, ptal!

@praveenkumar
Copy link
Contributor

/lgtm

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

/approve

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, praveenkumar, sallyom

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 Oct 22, 2020
@openshift-merge-robot openshift-merge-robot merged commit e47a0f7 into openshift:master Oct 22, 2020
@openshift-ci-robot
Copy link
Contributor

@sallyom: Updated the following 5 configmaps:

  • ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-installer-master.yaml using file ci-operator/config/openshift/installer/openshift-installer-master.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
  • 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
  • step-registry configmap in namespace ci at cluster api.ci using the following files:
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/OWNERS
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/conf/OWNERS
    • key openshift-e2e-gcp-libvirt-conf-commands.sh using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/conf/openshift-e2e-gcp-libvirt-conf-commands.sh
    • key openshift-e2e-gcp-libvirt-conf-ref.metadata.json using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/conf/openshift-e2e-gcp-libvirt-conf-ref.metadata.json
    • key openshift-e2e-gcp-libvirt-conf-ref.yaml using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/conf/openshift-e2e-gcp-libvirt-conf-ref.yaml
    • key openshift-e2e-gcp-libvirt-workflow.metadata.json using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/openshift-e2e-gcp-libvirt-workflow.metadata.json
    • key openshift-e2e-gcp-libvirt-workflow.yaml using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/openshift-e2e-gcp-libvirt-workflow.yaml
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/setup/OWNERS
    • key openshift-e2e-gcp-libvirt-setup-commands.sh using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/setup/openshift-e2e-gcp-libvirt-setup-commands.sh
    • key openshift-e2e-gcp-libvirt-setup-ref.metadata.json using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/setup/openshift-e2e-gcp-libvirt-setup-ref.metadata.json
    • key openshift-e2e-gcp-libvirt-setup-ref.yaml using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/setup/openshift-e2e-gcp-libvirt-setup-ref.yaml
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/test/OWNERS
    • key openshift-e2e-gcp-libvirt-test-commands.sh using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/test/openshift-e2e-gcp-libvirt-test-commands.sh
    • key openshift-e2e-gcp-libvirt-test-ref.metadata.json using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/test/openshift-e2e-gcp-libvirt-test-ref.metadata.json
    • key openshift-e2e-gcp-libvirt-test-ref.yaml using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/test/openshift-e2e-gcp-libvirt-test-ref.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/gcp/libvirt/OWNERS
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/conf/OWNERS
    • key openshift-e2e-gcp-libvirt-conf-commands.sh using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/conf/openshift-e2e-gcp-libvirt-conf-commands.sh
    • key openshift-e2e-gcp-libvirt-conf-ref.metadata.json using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/conf/openshift-e2e-gcp-libvirt-conf-ref.metadata.json
    • key openshift-e2e-gcp-libvirt-conf-ref.yaml using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/conf/openshift-e2e-gcp-libvirt-conf-ref.yaml
    • key openshift-e2e-gcp-libvirt-workflow.metadata.json using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/openshift-e2e-gcp-libvirt-workflow.metadata.json
    • key openshift-e2e-gcp-libvirt-workflow.yaml using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/openshift-e2e-gcp-libvirt-workflow.yaml
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/setup/OWNERS
    • key openshift-e2e-gcp-libvirt-setup-commands.sh using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/setup/openshift-e2e-gcp-libvirt-setup-commands.sh
    • key openshift-e2e-gcp-libvirt-setup-ref.metadata.json using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/setup/openshift-e2e-gcp-libvirt-setup-ref.metadata.json
    • key openshift-e2e-gcp-libvirt-setup-ref.yaml using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/setup/openshift-e2e-gcp-libvirt-setup-ref.yaml
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/test/OWNERS
    • key openshift-e2e-gcp-libvirt-test-commands.sh using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/test/openshift-e2e-gcp-libvirt-test-commands.sh
    • key openshift-e2e-gcp-libvirt-test-ref.metadata.json using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/test/openshift-e2e-gcp-libvirt-test-ref.metadata.json
    • key openshift-e2e-gcp-libvirt-test-ref.yaml using file ci-operator/step-registry/openshift/e2e/gcp/libvirt/test/openshift-e2e-gcp-libvirt-test-ref.yaml
Details

In response to this:

Picking up @praveenkumar 's PR to rebase/test/add ssh config vars

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

Development

Successfully merging this pull request may close these issues.

8 participants