Skip to content

Conversation

@sallyom
Copy link
Contributor

@sallyom sallyom commented Dec 16, 2018

This PR:

  • updates cluster-launch-installer-libvirt template
  • updates test command

@openshift-ci-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Dec 16, 2018
@sallyom sallyom force-pushed the remove-smoke-4-test-suite-libvirt branch 5 times, most recently from 9306531 to 8a966a2 Compare December 20, 2018 21:05
@sallyom sallyom force-pushed the remove-smoke-4-test-suite-libvirt branch 2 times, most recently from 6656e46 to cb60152 Compare December 21, 2018 12:35
@wking
Copy link
Member

wking commented Dec 22, 2018

Are we versioning @ironcladlou's repo? I don't see us bumping it here. Or maybe we don't need any changes there?

@sallyom sallyom force-pushed the remove-smoke-4-test-suite-libvirt branch from cb60152 to b621149 Compare December 22, 2018 15:22
@sallyom
Copy link
Contributor Author

sallyom commented Dec 22, 2018

@wking We are not versioning https://github.com/ironcladlou/openshift4-libvirt-gcp, images are built manually (today) and pushed to gcp projects openshift-gce-devel-ci/openshift-devel-ci. The script to setup the libvirt environment in the gce image is updated according to changes in openshift/installer (by me, and we can discuss best way to maintain this in the future). We've discussed whether this setup should become an 'officially' supported development env, but last outcome of that was that this will be only maintained for CI purposes. The provisioning script is (pretty much) a mirror of the libvirt how-to docs, and could run with every CI job (rather than banked in a gce image) but that would increase the time of a libvirt test by a lot.

@wking
Copy link
Member

wking commented Dec 22, 2018

Manually pushing is fine with me for now, I just wanted to make sure it was being bumped somehow ;).

@sallyom sallyom force-pushed the remove-smoke-4-test-suite-libvirt branch 2 times, most recently from 1df97dd to 1dc8c46 Compare December 22, 2018 16:53
@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 11, 2019
@gbraad
Copy link

gbraad commented Mar 13, 2019

@praveenkumar @zeenix Might be of interest to you guys

@sallyom sallyom force-pushed the remove-smoke-4-test-suite-libvirt branch from 1dc8c46 to 135b90a Compare March 13, 2019 18:29
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 13, 2019
@sallyom sallyom force-pushed the remove-smoke-4-test-suite-libvirt branch from 135b90a to 0fdc5bd Compare March 19, 2019 18:07
@praveenkumar
Copy link
Contributor

@wking @sallyom if that is ok can we merge this now?

@sallyom
Copy link
Contributor Author

sallyom commented Mar 20, 2019

@wking, I have updated, been running with this, it's working well (the install times out but the setup is correct. The libvirt template creates an instance in gce, runs the install using the nested-libvirt setup, and the gce is deleted upon any hiccups or success).

This PR will give @praveenkumar and team a good starting point to get this job consistently passing (it's not run unless you comment in gh).

@wking
Copy link
Member

wking commented Mar 25, 2019

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 25, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sallyom, 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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 25, 2019
@openshift-merge-robot openshift-merge-robot merged commit b6400ce into openshift:master Mar 25, 2019
@openshift-ci-robot
Copy link
Contributor

@sallyom: Updated the following 2 configmaps:

  • prow-job-cluster-launch-installer-libvirt-e2e configmap in namespace ci using the following files:
    • key cluster-launch-installer-libvirt-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-libvirt-e2e.yaml
  • prow-job-cluster-launch-installer-libvirt-e2e configmap in namespace ci-stg using the following files:
    • key cluster-launch-installer-libvirt-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-libvirt-e2e.yaml
Details

In response to this:

This PR:

  • updates cluster-launch-installer-libvirt template
  • updates test command

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. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants