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

Get correct image checksum in getImageUpdateOptsForNode() #768

Merged
merged 1 commit into from Jan 18, 2021

Conversation

zaneb
Copy link
Member

@zaneb zaneb commented Jan 18, 2021

We always want to get the checksum from the Image passed as imageData.
Due to an inadvertant change during the refactoring that created this
method (177d9ef), we were always
getting the checksum from the Image in the Spec, even though imageData
may reference the one in the Status during registration.

This meant that during deprovisioning (with no image in the Spec),
adoption would fail as the node would not have image data added during
registration.

We always want to get the checksum from the Image passed as imageData.
Due to an inadvertant change during the refactoring that created this
method (177d9ef), we were always
getting the checksum from the Image in the Spec, even though imageData
may reference the one in the Status during registration.

This meant that during deprovisioning (with no image in the Spec),
adoption would fail as the node would not have image data added during
registration.
@zaneb zaneb requested a review from hardys January 18, 2021 17:06
@metal3-io-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zaneb

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

@metal3-io-bot metal3-io-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 18, 2021
@zaneb
Copy link
Member Author

zaneb commented Jan 18, 2021

/test-v1a3-centos-integration
/test-integration

@metal3-io-bot metal3-io-bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jan 18, 2021
@hardys
Copy link
Member

hardys commented Jan 18, 2021

Thanks for spotting this, not sure how/why I made that mistake! 🤔

/lgtm

@metal3-io-bot metal3-io-bot added the lgtm Indicates that a PR is ready to be merged. label Jan 18, 2021
@metal3-io-bot metal3-io-bot merged commit 50a08ad into metal3-io:master Jan 18, 2021
hardys pushed a commit to hardys/baremetal-operator that referenced this pull request Jan 19, 2021
As seen in the regression CI discovered that prompted
metal3-io#768
we're missing some test coverage of the two possible
image sources in ValidateManagementAccess
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. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants