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

Bug 1835457: Put BMH status in annotation while reconciliation #68

Merged
merged 5 commits into from May 14, 2020

Conversation

stbenjam
Copy link
Member

@stbenjam stbenjam commented May 13, 2020

Upstream added support to populate introspection via annotation, we need to backport this into baremetal-operator so we can populate masters IP information to make the node/machine link.

@openshift-ci-robot openshift-ci-robot added the bugzilla/severity-unspecified Referenced Bugzilla bug's severity is unspecified for the PR. label May 13, 2020
@openshift-ci-robot
Copy link

@stbenjam: This pull request references Bugzilla bug 1835457, 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.5.0) matches configured target release for branch (4.5.0)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1835457: Put BMH status in annotation while reconciliation

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 bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label May 13, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 13, 2020
@stbenjam
Copy link
Member Author

Per @dhellmann I'll need to yoink metal3-io#516 when it merges

If we are copying the Status in from a baremetalhost.metal3.io/status
annotation, return and requeue immediately after writing it rather than
try to continue to do other things, which may result in a write
conflict.

Also, invert the output of the hostHasStatus() method, so that it no
longer returns the exact opposite of what it says on the tin.
@openshift-ci-robot
Copy link

@stbenjam: This pull request references Bugzilla bug 1835457, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.0) matches configured target release for branch (4.5.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1835457: Put BMH status in annotation while reconciliation

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.

@dhellmann
Copy link

This cherry-pick looks good to me. I'll wait for @mhrivnak's question to be resolved before approving formally.

@stbenjam
Copy link
Member Author

Linting fix: metal3-io#521

@imain
Copy link

imain commented May 13, 2020

Looks good to me.

dhellmann and others added 3 commits May 13, 2020 19:03
The lint target does not work, yet, because generate-sdk fails. Add a
separate target for golint and then have travis use that as a quick
way to enforce it until we can set up a prow job.

Signed-off-by: Doug Hellmann <dhellmann@redhat.com>
Signed-off-by: Doug Hellmann <dhellmann@redhat.com>
The upstream lint target in make is overloaded and is trying to do too
much.
Copy link
Member

@mhrivnak mhrivnak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest including some documentation for the API addition, but since it's also undocumented upstream, I'm fine with someone doing it there first.

@stbenjam
Copy link
Member Author

/test images

@dhellmann
Copy link

/lgtm

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhellmann, stbenjam

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

@openshift-merge-robot openshift-merge-robot merged commit 6b3d162 into openshift:master May 14, 2020
@openshift-ci-robot
Copy link

@stbenjam: All pull requests linked via external trackers have merged: openshift/baremetal-operator#68. Bugzilla bug 1835457 has been moved to the MODIFIED state.

In response to this:

Bug 1835457: Put BMH status in annotation while reconciliation

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.

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/severity-unspecified Referenced Bugzilla bug's severity is unspecified for the PR. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants