-
Notifications
You must be signed in to change notification settings - Fork 37
OCPBUGS-1871: Fix machine not going failed with invalid vmsize #36
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
OCPBUGS-1871: Fix machine not going failed with invalid vmsize #36
Conversation
|
@RadekManak: This pull request references Jira Issue OCPBUGS-1871, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
|
/hold Might not always be invalid |
|
/unhold |
| skuI, err := s.resourcesSkus.Get(ctx, skuSpec) | ||
| if err != nil { | ||
| return fmt.Errorf("failed to find sku %s", s.scope.MachineConfig.VMSize) | ||
| return machinecontroller.InvalidMachineConfiguration("failed to fetch instance type information from azure: %w", err) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this be a transient error? What machine configuration leads into this? Is there a way to be more precise here, eg, if it returns a not found error vs something else?
ac81a10 to
8edd88c
Compare
|
/approve Thanks for updating |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoelSpeed 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 |
|
/jira refresh |
|
@JoelSpeed: This pull request references Jira Issue OCPBUGS-1871, which is invalid:
Comment DetailsIn response to this:
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. |
|
/jira refresh |
|
@JoelSpeed: This pull request references Jira Issue OCPBUGS-1871, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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. |
|
/override ci/prow/e2e-azure-operator The failure in the e2e is resolved by openshift/machine-api-operator#1076 and the tests that didn't run are autoscaler related, confident this change isn't going to break those |
|
@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-azure-operator DetailsIn response to this:
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. |
|
/hold @RadekManak There are some comments in the bug about the message having changed, how would you like to resolve that? |
8edd88c to
6da451e
Compare
|
/lgtm |
|
/retest-required |
2 similar comments
|
/retest-required |
|
/retest-required |
|
/hold This failed QE, seems we need to do a similar change in another part of the code when we haven't got accelerated networking enabled |
6da451e to
7fd0017
Compare
|
Changed it to use the same error handling in all three places that call the resourceskus. Get function. |
|
/retest |
|
/label qe-approved |
|
/lgtm |
|
/retest-required |
4 similar comments
|
/retest-required |
|
/retest-required |
|
/retest-required |
|
/retest-required |
|
/override ci/prow/e2e-azure-operator This failed on the penultimate test which we are working on fixing, this is a known issue. I don't believe this PR is causing any problems. All the previous tests have passed and 2 of the 4 autoscaler tests passed indicating the autoscaler is also functional |
|
@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-azure-operator DetailsIn response to this:
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. |
|
@RadekManak: all tests passed! Full PR test history. Your PR dashboard. 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. |
|
@RadekManak: Jira Issue OCPBUGS-1871 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state. DetailsIn response to this:
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. |
|
[ART PR BUILD NOTIFIER] This PR has been included in build ose-machine-api-provider-azure-container-v4.12.0-202305022015.p0.gcfb76ac.assembly.stream for distgit ose-machine-api-provider-azure. |
This error needs to be InvalidMachineConfiguration, because machine goes failed only if it finds error of that type.