Bug 2106733: Fix panic when accessing nil machine annotations map

[RadekManak]

This is a bug fix for panic when deleting a machine and trying to access a value from its annotations while the map is not initialized.

[openshift-ci]

@RadekManak: This pull request references Bugzilla bug 2060068, which is invalid:

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

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

In response to this:

Bug 2060068: Fix panic when accessing nil machine annotations map

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]

@RadekManak: This pull request references Bugzilla bug 2106733, which is invalid:

• expected the bug to target the "4.12.0" release, but it targets "---" instead

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

In response to this:

Bug 2106733: Fix panic when accessing nil machine annotations map

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]

/bugzilla refresh

[openshift-ci]

@RadekManak: This pull request references Bugzilla bug 2106733, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.12.0) matches configured target release for branch (4.12.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @sunzhaohua2

In response to this:

/bugzilla 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.

[lobziik]

/lgtm

[JoelSpeed]

/approve

[openshift-ci]

[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

Needs approval from an approver in each of these files:

• OWNERS [JoelSpeed]

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]

/retest-required

Remaining retests: 2 against base HEAD 577ec9f and 8 for PR HEAD 2b7b6b0 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 1 against base HEAD 577ec9f and 7 for PR HEAD 2b7b6b0 in total

[openshift-ci]

@RadekManak: all tests passed!

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-ci]

@RadekManak: All pull requests linked via external trackers have merged:

• openshift/machine-api-provider-aws#46

Bugzilla bug 2106733 has been moved to the MODIFIED state.

In response to this:

Bug 2106733: Fix panic when accessing nil machine annotations map

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]

/cherry-pick release-4.11

[openshift-cherrypick-robot]

@RadekManak: new pull request created: #47

In response to this:

/cherry-pick release-4.11

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.