Bug 2060587 - Hardware events subscription is deleted after a reboot on HPE machine
Summary: Hardware events subscription is deleted after a reboot on HPE machine
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Iury Gregory Melo Ferreira
QA Contact: Pedro Amoedo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-03 19:38 UTC by Ori Michaeli
Modified: 2023-03-09 01:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-03-09 01:14:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ori Michaeli 2022-03-03 19:38:09 UTC
Description of problem:
After creation of a subscription on a HPE node and rebooting it the subscription was deleted -> this was checked through the BMC.
oc get bmceventsubscriptions.metal3.io -A shows the subscription still exists. 

Version-Release number of selected component (if applicable):
4.10.0-0.nightly-2022-03-01-224543

How reproducible:
100%

Steps to Reproduce:
1. Create a subscription on a node.
2. Reboot the node.
3. Check through the BMC that the subscription still exists.

Actual results:
The subscription was deleted.

Expected results:
The subscription should remain intact after a reboot.

Additional info:
HPE DL380 - Firmware Revision: 2.31

Comment 1 Iury Gregory Melo Ferreira 2022-04-01 14:47:33 UTC
Hey Ori,

I was able to talk with some HPE folks, and they asked me the following question:

"By any chance the delivery of the events were supposed to go to the system being rebooted? there is an iLO subscription behavior wherein if it fails to deliver the event to the target, it would delete the subscription thinking the subscription is invalid."

Can you check if there was something receiving the subscriptions while the node was on and when we try to reboot? I think Jack can probably provide some help on how you can verify this.

Thanks

Comment 2 Ori Michaeli 2022-04-06 15:29:37 UTC
My scenario was as follows - I created a subscription and without the triggering of any event I rebooted the node.
This caused the subscription to be deleted.
without the reboot the subscription remained intact for a day or so.

Comment 5 Shiftzilla 2023-03-09 01:14:18 UTC
OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira.

https://issues.redhat.com/browse/OCPBUGS-9151


Note You need to log in before you can comment on or make changes to this bug.