Skip to content

Conversation

@RadekManak
Copy link
Contributor

This error needs to be InvalidMachineConfiguration, because machine goes failed only if it finds error of that type.

@openshift-ci-robot openshift-ci-robot added the jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. label Oct 7, 2022
@openshift-ci-robot
Copy link

@RadekManak: This pull request references Jira Issue OCPBUGS-1871, which is invalid:

  • expected the bug to target the "4.12.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This error needs to be InvalidMachineConfiguration, because machine goes failed only if it finds error of that type.

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 jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 7, 2022
@openshift-ci openshift-ci bot requested review from Fedosin and JoelSpeed October 7, 2022 14:42
@RadekManak
Copy link
Contributor Author

/hold Might not always be invalid

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 7, 2022
@RadekManak
Copy link
Contributor Author

/unhold
We treat failure to send request to create machine as invalid machine configuration, so I think failure to retrieve instance type information can be invalid machine configuration as well.

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 7, 2022
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)
Copy link
Contributor

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?

@RadekManak RadekManak force-pushed the fix_not_failed_invalid_vmsize branch from ac81a10 to 8edd88c Compare October 13, 2022 11:38
@JoelSpeed
Copy link
Contributor

/approve
/lgtm

Thanks for updating

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 13, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 13, 2022

[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

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 13, 2022
@JoelSpeed
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link

@JoelSpeed: This pull request references Jira Issue OCPBUGS-1871, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

@JoelSpeed
Copy link
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 14, 2022
@openshift-ci-robot
Copy link

@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
  • bug is open, matching expected state (open)
  • bug target version (4.12.0) matches configured target version for branch (4.12.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @huali9

Details

In response to this:

/jira refresh

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 openshift-ci bot requested a review from huali9 October 14, 2022 08:43
@JoelSpeed
Copy link
Contributor

/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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 14, 2022

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-azure-operator

Details

In response to this:

/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

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.

@JoelSpeed
Copy link
Contributor

/hold

@RadekManak There are some comments in the bug about the message having changed, how would you like to resolve that?

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 14, 2022
@RadekManak RadekManak force-pushed the fix_not_failed_invalid_vmsize branch from 8edd88c to 6da451e Compare October 14, 2022 10:23
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 14, 2022
@JoelSpeed
Copy link
Contributor

/lgtm
/retest-required

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 14, 2022
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD e62926d and 2 for PR HEAD 6da451e in total

@JoelSpeed
Copy link
Contributor

/retest-required

2 similar comments
@JoelSpeed
Copy link
Contributor

/retest-required

@JoelSpeed
Copy link
Contributor

/retest-required

@JoelSpeed
Copy link
Contributor

/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

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 18, 2022
@RadekManak RadekManak force-pushed the fix_not_failed_invalid_vmsize branch from 6da451e to 7fd0017 Compare October 18, 2022 12:47
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 18, 2022
@RadekManak
Copy link
Contributor Author

Changed it to use the same error handling in all three places that call the resourceskus. Get function.
/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 18, 2022
@RadekManak
Copy link
Contributor Author

/retest
Did the tests get stuck?

@huali9
Copy link

huali9 commented Oct 19, 2022

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Oct 19, 2022
@JoelSpeed
Copy link
Contributor

/lgtm
/retest-required

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 19, 2022
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 96739ba and 2 for PR HEAD 7fd0017 in total

@JoelSpeed
Copy link
Contributor

/retest-required

4 similar comments
@JoelSpeed
Copy link
Contributor

/retest-required

@JoelSpeed
Copy link
Contributor

/retest-required

@JoelSpeed
Copy link
Contributor

/retest-required

@JoelSpeed
Copy link
Contributor

/retest-required

@JoelSpeed
Copy link
Contributor

/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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 21, 2022

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-azure-operator

Details

In response to this:

/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

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

openshift-ci bot commented Oct 21, 2022

@RadekManak: all tests passed!

Full PR test history. Your PR dashboard.

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.

@openshift-merge-robot openshift-merge-robot merged commit cfb76ac into openshift:main Oct 21, 2022
@openshift-ci-robot
Copy link

@RadekManak: Jira Issue OCPBUGS-1871 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state.

Details

In response to this:

This error needs to be InvalidMachineConfiguration, because machine goes failed only if it finds error of that type.

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

[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.
All builds following this will include this PR.

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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants