Skip to content

Conversation

@derekhiggins
Copy link
Contributor

@derekhiggins derekhiggins commented Sep 13, 2019

Adding a template to for jobs that test Bare Metal
Installer Provisioned Infrastructure. This template uses
packet.net to spin up a single baremetal server and test
the ipi installer on it.

Due to openshift/ci-tools#136 I'll add a seperate PR to use it in a presubmit job

Update:
updates cluster-launch-installer-e2e, No longer adds a template

@openshift-ci-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Sep 13, 2019
@derekhiggins
Copy link
Contributor Author

/assign @smarterclayton

Copy link
Contributor

Choose a reason for hiding this comment

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

Naming here is wrong. This really upi for packet, so update the naming to be consistent (cluster-launch-installer-upi-packet-e2e).

What's more concerning is that this template is inconsistent in structure, naming, and behavior from the other templates. This template really needs to look like cluster-launch-installer-e2e with a few small tweaks (such as your custom terraform setup) or be part of that template with a cluster type (packet). You can omit some of that to get started, but the end result needs to be more consistent with the rest or this will forever atrophy when someone needs to refactor all of them and yours is unmaintainable.

Why is the libvirt image needed?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Naming here is wrong. This really upi for packet, so update the naming to be consistent (cluster-launch-installer-upi-packet-e2e).

What's more concerning is that this template is inconsistent in structure, naming, and behavior from the other templates. This template really needs to look like cluster-launch-installer-e2e with a few small tweaks (such as your custom terraform setup) or be part of that template with a cluster type (packet). You can omit some of that to get started, but the end result needs to be more consistent with the rest or this will forever atrophy when someone needs to refactor all of them and yours is unmaintainable.

I'm not sure I understand this, we're not using UPI, this is IPI, I don't see it easily fitting into any of the other templates as the flow is different, for the moment we just want to spin up a baremetal centos server and run the installer on it. But I can look at adding the cluster type to cluster-launch-installer-e2e

Why is the libvirt image needed?

I'm using it because it was the only image I found that had the libnss_wrapper so I could ssh to packet.net servers, incidentally the reason for using the UPI image is because it had terraform.

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 24, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: derekhiggins
To complete the pull request process, please assign smarterclayton
You can assign the PR to them by writing /assign @smarterclayton in a comment when ready.

The full list of commands accepted by this bot can be found 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 removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 24, 2019
@derekhiggins derekhiggins force-pushed the ipi-e2e-job branch 5 times, most recently from 3238ee7 to ebc782f Compare September 26, 2019 16:58
@derekhiggins
Copy link
Contributor Author

@smarterclayton I've updated this into the cluster-launch-installer-e2e.yaml template, is this what you wanted? I'm still not sure about your naming comment, AIUI this is baremetal ipi?

Updating cluster-launch-installer-e2e template to for
jobs that test Bare Metal provided Installer Provisioned
Infrastructure. Use packet.net to spin up a single baremetal
server and test the ipi installer on it.
@openshift-ci-robot
Copy link
Contributor

@derekhiggins: PR needs rebase.

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.

1 similar comment
@openshift-ci-robot
Copy link
Contributor

@derekhiggins: PR needs rebase.

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.

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 12, 2019
@openshift-ci-robot
Copy link
Contributor

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

Test name Commit Details Rerun command
ci/rehearse/openshift/cloud-credential-operator/master/e2e-gcp 538ba0d link /test pj-rehearse
ci/rehearse/openshift/cloud-credential-operator/master/e2e-azure 538ba0d link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-ipi 538ba0d link /test pj-rehearse
ci/prow/pj-rehearse 538ba0d link /test pj-rehearse
ci/rehearse/cri-o/cri-o/release-1.13/e2e-aws 538ba0d link /test pj-rehearse
ci/prow/step-registry-shellcheck 538ba0d link /test step-registry-shellcheck
ci/prow/build-farm-consistency 538ba0d link /test build-farm-consistency

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.

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.

@petr-muller
Copy link
Member

Stale PR, please adapt and reopen if still needed.

/close

@openshift-ci-robot
Copy link
Contributor

@petr-muller: Closed this PR.

Details

In response to this:

Stale PR, please adapt and reopen if still needed.

/close

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

needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. 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.

4 participants