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-15235: [iRMC] Fix IPMI incompatibility handling error #21

Merged
merged 1 commit into from
Jun 26, 2023

Conversation

hroyrh
Copy link

@hroyrh hroyrh commented Jun 26, 2023

This patch deals with overlooked situation in patch d23f72e, in which irmc_ipmi_succeed flag is added to deal with iRMC firmware's IPMI incompatibility introduced at iRMC firmware version S6 2.00 and later.
That flag is set and updated by irmc power_interface code and rest of iRMC driver code use that flag.

When ipmitool is set as power_interface, that flag is not set nor updated and rest of iRMC driver code fail to handle IPMI incompatibility correctly.

This patch adds logic to check power_interface to
make iRMC driver properly deal with iRMC firmware's IPMI incompatibility even when ipmitool power_interface is used.

Change-Id: Id353c4f5260a7c469779b50ad302f442223df5a0 (cherry picked from commit 27bf209)

This patch deals with overlooked situation in patch
d23f72e, in which
`irmc_ipmi_succeed` flag is added to deal with iRMC
firmware's IPMI incompatibility introduced at iRMC
firmware version S6 2.00 and later.
That flag is set and updated by `irmc` power_interface
code and rest of iRMC driver code use that flag.

When `ipmitool` is set as power_interface, that flag
is not set nor updated and rest of iRMC driver code
fail to handle IPMI incompatibility correctly.

This patch adds logic to check power_interface to
make iRMC driver properly deal with iRMC firmware's IPMI
incompatibility even when `ipmitool` power_interface
is used.

Change-Id: Id353c4f5260a7c469779b50ad302f442223df5a0
(cherry picked from commit 27bf209)
@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 Jun 26, 2023
@openshift-ci-robot
Copy link

@hroyrh: This pull request references Jira Issue OCPBUGS-15235, which is invalid:

  • expected the bug to target the "4.13.z" version, but no target version was set
  • expected Jira Issue OCPBUGS-15235 to depend on a bug targeting a version in 4.14.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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:

This patch deals with overlooked situation in patch d23f72e, in which irmc_ipmi_succeed flag is added to deal with iRMC firmware's IPMI incompatibility introduced at iRMC firmware version S6 2.00 and later.
That flag is set and updated by irmc power_interface code and rest of iRMC driver code use that flag.

When ipmitool is set as power_interface, that flag is not set nor updated and rest of iRMC driver code fail to handle IPMI incompatibility correctly.

This patch adds logic to check power_interface to
make iRMC driver properly deal with iRMC firmware's IPMI incompatibility even when ipmitool power_interface is used.

Change-Id: Id353c4f5260a7c469779b50ad302f442223df5a0 (cherry picked from commit 27bf209)

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

openshift-ci bot commented Jun 26, 2023

@hroyrh: 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.

@rhjanders
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 26, 2023
@hroyrh
Copy link
Author

hroyrh commented Jun 26, 2023

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jun 26, 2023
@openshift-ci-robot
Copy link

@hroyrh: This pull request references Jira Issue OCPBUGS-15235, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.13.z) matches configured target version for branch (4.13.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-13564 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-13564 targets the "4.14.0" version, which is one of the valid target versions: 4.14.0
  • bug has dependents

Requesting review from QA contact:
/cc @pamoedom

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-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jun 26, 2023
@openshift-ci openshift-ci bot requested a review from pamoedom June 26, 2023 04:56
@elfosardo
Copy link

/approve

@openshift-ci
Copy link

openshift-ci bot commented Jun 26, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elfosardo, hroyrh

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 Jun 26, 2023
@elfosardo
Copy link

/hold

@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 Jun 26, 2023
@elfosardo
Copy link

/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 Jun 26, 2023
@openshift-merge-robot openshift-merge-robot merged commit 8b1a2d0 into openshift:release-4.13 Jun 26, 2023
4 checks passed
@openshift-ci-robot
Copy link

@hroyrh: Jira Issue OCPBUGS-15235: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-15235 has been moved to the MODIFIED state.

In response to this:

This patch deals with overlooked situation in patch d23f72e, in which irmc_ipmi_succeed flag is added to deal with iRMC firmware's IPMI incompatibility introduced at iRMC firmware version S6 2.00 and later.
That flag is set and updated by irmc power_interface code and rest of iRMC driver code use that flag.

When ipmitool is set as power_interface, that flag is not set nor updated and rest of iRMC driver code fail to handle IPMI incompatibility correctly.

This patch adds logic to check power_interface to
make iRMC driver properly deal with iRMC firmware's IPMI incompatibility even when ipmitool power_interface is used.

Change-Id: Id353c4f5260a7c469779b50ad302f442223df5a0 (cherry picked from commit 27bf209)

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

6 participants