Skip to content

Conversation

@patrickdillon
Copy link
Contributor

Jira: CORS-1059

Run BYOH tests on:

  • installer
  • machine-api operator
  • machine-config operator

More specifically this renames the tests to e2e-aws-scaleup-rhel7 and switches always_run to true.

NOTE I ignored warning messages like the following from prow-gen. Please let me know if that is a problem and I can try to rename the test:

WARN[0000] Generated job name is longer than 63 characters. This may cause issues when Prow attempts to label resources with job name. Consider a shorter name.  name=pull-ci-openshift-machine-config-operator-master-e2e-aws-scaleup-rhel7

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

/cc vrutkovs

@runcom
Copy link
Member

runcom commented Apr 15, 2019

NOTE I ignored warning messages like the following from prow-gen. Please let me know if that is a problem and I can try to rename the test:

these shouldn't be an issue but I'm not entirely sure (I've had PR merged with this anyway)

this LGTM and can't wait to have it :)

@vrutkovs
Copy link
Contributor

NOTE I ignored warning messages like the following from prow-gen. Please let me know if that is a problem and I can try to rename the test:

WARN[0000] Generated job name is longer than 63 characters. This may cause issues when Prow attempts to label resources with job name. Consider a shorter name.  name=pull-ci-openshift-machine-config-operator-master-e2e-aws-scaleup-rhel7

That's expected, yes

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 15, 2019
@runcom
Copy link
Member

runcom commented Apr 15, 2019

@patrickdillon: The following test failed, say /retest to rerun them all:

😢

@runcom
Copy link
Member

runcom commented Apr 15, 2019

aws limit error tho:

level=error msg="Error: Error applying plan:"
level=error
level=error msg="1 error occurred:"
level=error msg="\t* module.vpc.aws_route_table_association.route_net[0]: 1 error occurred:"
level=error msg="\t* aws_route_table_association.route_net.0: timeout while waiting for state to become 'success' (timeout: 5m0s)"

let's retest shortly

@patrickdillon
Copy link
Contributor Author

/retest

1 similar comment
@vrutkovs
Copy link
Contributor

/retest

@vrutkovs
Copy link
Contributor

https://rpms.svc.ci.openshift.org/openshift-origin-v4.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found

Asked testplatform folks to create 4.1 repos

@patrickdillon
Copy link
Contributor Author

/retest

@patrickdillon patrickdillon force-pushed the installer-mco-mao-rhel-scaleup branch from 668e39a to 4b138a6 Compare April 22, 2019 18:12
@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Apr 22, 2019
@patrickdillon
Copy link
Contributor Author

@vrutkovs lgtm got removed when I resoived merge conflicts. can you take another look?

@patrickdillon
Copy link
Contributor Author

/retest

@patrickdillon
Copy link
Contributor Author

/retest

1 similar comment
@patrickdillon
Copy link
Contributor Author

/retest

@patrickdillon
Copy link
Contributor Author

/retest

@patrickdillon patrickdillon force-pushed the installer-mco-mao-rhel-scaleup branch from 4b138a6 to 645929d Compare April 24, 2019 20:20
@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 24, 2019
@patrickdillon patrickdillon force-pushed the installer-mco-mao-rhel-scaleup branch from 645929d to ce3351e Compare April 24, 2019 20:34
@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 25, 2019
@patrickdillon patrickdillon force-pushed the installer-mco-mao-rhel-scaleup branch from 28f4b7a to 4a41fb9 Compare April 25, 2019 15:06
@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 25, 2019
@patrickdillon
Copy link
Contributor Author

/retest

2 similar comments
@patrickdillon
Copy link
Contributor Author

/retest

@patrickdillon
Copy link
Contributor Author

/retest

@patrickdillon
Copy link
Contributor Author

/test ci/rehearse/openshift/installer/release-4.1/e2e-aws-scaleup-rhel7

@patrickdillon patrickdillon force-pushed the installer-mco-mao-rhel-scaleup branch from 4a41fb9 to 798cd9c Compare April 25, 2019 18:13
@patrickdillon
Copy link
Contributor Author

/retest

@vrutkovs
Copy link
Contributor

/test pj-rehearse

@openshift-ci-robot
Copy link
Contributor

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

Test name Commit Details Rerun command
ci/rehearse/openshift/machine-config-operator/release-4.1/e2e-aws-scaleup-rhel7 798cd9c link /test pj-rehearse
ci/rehearse/openshift/installer/release-4.0/e2e-aws-scaleup-rhel7 798cd9c link /test pj-rehearse
ci/rehearse/openshift/installer/release-4.1/e2e-aws-scaleup-rhel7 798cd9c link /test pj-rehearse
ci/rehearse/openshift/machine-config-operator/release-4.0/e2e-aws-scaleup-rhel7 798cd9c link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-aws-scaleup-rhel7 798cd9c link /test pj-rehearse
ci/rehearse/openshift/machine-api-operator/master/e2e-aws-scaleup-rhel7 798cd9c link /test pj-rehearse
ci/rehearse/openshift/machine-config-operator/master/e2e-aws-scaleup-rhel7 798cd9c link /test pj-rehearse
ci/rehearse/openshift/machine-api-operator/release-4.1/e2e-aws-scaleup-rhel7 798cd9c link /test pj-rehearse
ci/prow/pj-rehearse 798cd9c 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.

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.

Copy link
Contributor

@vrutkovs vrutkovs left a comment

Choose a reason for hiding this comment

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

/lgtm

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

/approve

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: patrickdillon, vrutkovs
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers: cgwalters, spangenberg, tomassedovic

If they are not already assigned, you can assign the PR to them by writing /assign @cgwalters @spangenberg @tomassedovic in a comment when ready.

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

@patrickdillon
Copy link
Contributor Author

/assign @cgwalters @spangenberg

@patrickdillon
Copy link
Contributor Author

/hold
The rehearsals are too flakey. I'm going to consider breaking this into separate PRs, see if that helps.

@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 26, 2019
Copy link
Contributor

@michaelgugino michaelgugino left a comment

Choose a reason for hiding this comment

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

I'm not a fan of the implementation here: https://github.com/openshift/openshift-ansible/blob/master/test/aws/create_machineset.yml

The only thing that looks like it should be variable is the ami-id. Please create a proper template so it's easier to identify breakage in the future. As-is, we would have to reverse engineer what's actually being created in several places.

@patrickdillon
Copy link
Contributor Author

/unassign @cgwalters @spangenberg

@patrickdillon
Copy link
Contributor Author

I am closing this to break into separate PRs for each repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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.

7 participants