-
Notifications
You must be signed in to change notification settings - Fork 231
remove hard-coding of AWS instance type #92
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
Conversation
|
is the installer passing this value? what happens if this is empty? |
|
/test e2e |
|
@trawler this is probably a legit fail based on my comment above as the test config don't set that value |
|
/test e2e-aws |
|
/hold |
|
@trawler The installer is currently not setting this value, we'll want a counter part PR to set this from the installer config. and the e2e-aws shows green, so not sure why our e2e was failing in your previews commit when the value was not set in the config, can you please verify this to ensure there's no gaps from installer->actuator? |
@enxebre I can confirm that when the instanceType is not being set, installation fails with this reply from the server: I'm not sure why the comment you quoted claims to set a default value, but actually, the aws-sdk will fail the install for an empty |
|
/test e2e-aws |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/test e2e-aws |
|
e2e-aws test failing for: |
|
/test e2e-aws |
|
@trawler: The following tests failed, say
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. DetailsInstructions 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. |
Where do we want the default value to live? If it's here, that's great. If it's in the installer, what happens if a user later bumps the config to remove the property (in an attempt to revert to the default value)? Or will that sort of adjustment be blocked somehow? |
|
Also, it may not be worth sinking time into this if the installer starts creating worker machine-sets directly. |
|
closing as specs are now moved to the installer |
Logrus to glog
OCPCLOUD-2565: Revendor MAO Pausing changes
resolves #85