Skip to content
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.

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

Flavor validations #3953

Merged
merged 1 commit into from Jul 30, 2020

Conversation

iamemilio
Copy link

@iamemilio iamemilio commented Jul 23, 2020

Check that a minimum set of requirements are met for flavors to ensure
that installation failures due to insufficient resources don't occur.

Stacked on top of my AZ pull request because this builds on top of the testing groundwork laid in that patch.

/cc @pierreprinetti @Fedosin @mandre @adduarte for review

@openshift-ci-robot
Copy link
Contributor

@iamemilio: GitHub didn't allow me to request PR reviews from the following users: for, review.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

Stacked on top of my AZ pull request because this builds on top of the testing groundwork laid in that patch.

/cc @pierreprinetti @Fedosin @mandre @adduarte for review

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.

@iamemilio
Copy link
Author

/label platform/openstack

@iamemilio
Copy link
Author

/retest

1 similar comment
@iamemilio
Copy link
Author

/retest

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 28, 2020
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 28, 2020
@Fedosin
Copy link
Contributor

Fedosin commented Jul 28, 2020

/lgtm
/approve
/hold
/test e2e-openstack

@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 Jul 28, 2020
@openshift-ci-robot openshift-ci-robot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jul 28, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Fedosin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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 lgtm Indicates that a PR is ready to be merged. label Jul 28, 2020
@Fedosin
Copy link
Contributor

Fedosin commented Jul 28, 2020

/lgtm

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

Fedosin commented Jul 28, 2020

/test e2e-openstack

@Fedosin
Copy link
Contributor

Fedosin commented Jul 28, 2020

/test e2e-aws

@Fedosin
Copy link
Contributor

Fedosin commented Jul 29, 2020

/retest

}(),
cloudInfo: validMpoolCloudInfo(),
expectedError: true,
expectedErrMsg: "compute.0..platform.openstack.flavorName: Not found: \"non-existant-flavor\"",
Copy link
Member

Choose a reason for hiding this comment

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

The two dots in compute.0..platform.openstack.flavorName is confusing, I suppose it works because it's a regex. Shouldn't it be something like compute\[0\]\.platform\.openstack\.flavorName instead?

Copy link
Author

Choose a reason for hiding this comment

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

yeah but it complained when I tried to escape the bracket character. The effect is the same

Copy link
Author

@iamemilio iamemilio Jul 29, 2020

Choose a reason for hiding this comment

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

Ah I actually figured out how to do this right, I'll just fix it

expectedErrMsg: "controlPlane.platform.openstack.flavorName: Not found: \"non-existant-flavor\"",
},
{
name: "not found control plane flavorName",
Copy link
Member

Choose a reason for hiding this comment

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

the name does not match the test.

name: "invalid platform flavor",
platform: func() *openstack.Platform {
p := validPlatform()
p.FlavorName = validComputeFlavor
Copy link
Member

Choose a reason for hiding this comment

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

I suggest you instead use invalidCtrlPlaneFlavor, where you can set all the values to be lower than required. You can also drop validComputeFlavor and invalidComputeFlavor that are not used for platform flavors.

Copy link
Author

Choose a reason for hiding this comment

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

My thinking here was that if they opt to use a default, then it has to meet the minimum requirement for both the master and workers. And since the master has higher requirements, then that is the bound we should test for.

@iamemilio
Copy link
Author

/retest

Check that a minimum set of requirements are met for flavors to ensure
that installation failures due to insufficient resources don't occur.
@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Jul 29, 2020
@mandre
Copy link
Member

mandre commented Jul 29, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 29, 2020
@iamemilio
Copy link
Author

/retest

1 similar comment
@iamemilio
Copy link
Author

/retest

@iamemilio
Copy link
Author

/hold cancel

e2e openstack passing, code localized to openstack validations

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 29, 2020
@openshift-bot
Copy link
Contributor

/retest

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

5 similar comments
@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-ci-robot
Copy link
Contributor

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

Test name Commit Details Rerun command
ci/prow/e2e-crc 47006ef link /test e2e-crc

Full PR test history. Your PR dashboard.

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-bot
Copy link
Contributor

/retest

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

@openshift-merge-robot openshift-merge-robot merged commit 7e8d172 into openshift:master Jul 30, 2020
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. platform/openstack
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants