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

OCPBUGS-43330: BMO never mounted dataimage into IBI provisioned SNO #141

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

tsorya
Copy link
Contributor

@tsorya tsorya commented Oct 16, 2024

There's a race between the DataImage creation and the reboot annotation added in updateBMHProvisioningState This PR adds a check that the DataImage creationTimestamp is more than the DataImageCoolDownPeriod ago (set to 1 second by default). In case the the dataImage was created withing the DataImageCoolDownPeriod the controller will return early and requeue the ICI CR after the DataImageCoolDownPeriod. This should prevent IBIO from adding the reboot annotation before BMO cached client notice that a DataImage exists.

There's a race between the DataImage creation and the reboot annotation added in updateBMHProvisioningState
This PR adds a check that the DataImage creationTimestamp is more than the DataImageCoolDownPeriod ago (set to 1 second by default).
In case the the dataImage was created withing the DataImageCoolDownPeriod the controller will
return early and requeue the ICI CR after the DataImageCoolDownPeriod.
This should prevent IBIO from adding the reboot annotation before BMO cached client notice that a DataImage exists.

Signed-off-by: Eran Cohen <[email protected]>
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 16, 2024
@openshift-ci-robot
Copy link

@tsorya: This pull request references Jira Issue OCPBUGS-43330, which is invalid:

  • expected the bug to target the "4.18.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.

In response to this:

There's a race between the DataImage creation and the reboot annotation added in updateBMHProvisioningState This PR adds a check that the DataImage creationTimestamp is more than the DataImageCoolDownPeriod ago (set to 1 second by default). In case the the dataImage was created withing the DataImageCoolDownPeriod the controller will return early and requeue the ICI CR after the DataImageCoolDownPeriod. This should prevent IBIO from adding the reboot annotation before BMO cached client notice that a DataImage exists.

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 openshift-eng/jira-lifecycle-plugin repository.

Copy link

openshift-ci bot commented Oct 16, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tsorya

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

What's the difference between this and #140?

Copy link

openshift-ci bot commented Oct 16, 2024

@tsorya: 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-sigs/prow repository. I understand the commands that are listed here.

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. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants