Bug 2131962 - HM ServiceMonitor not detecting member(VM) hard stopped
Summary: HM ServiceMonitor not detecting member(VM) hard stopped
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-ovn-octavia-provider
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z1
: 17.0
Assignee: Fernando Royo
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-04 09:53 UTC by Fernando Royo
Modified: 2023-01-25 12:30 UTC (History)
1 user (show)

Fixed In Version: python-ovn-octavia-provider-1.0.1-0.20221122190308.bbf881f.el9ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-25 12:29:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 859065 0 None MERGED Capture port deleted event associated to HM ServiceMonitor 2022-10-04 09:55:21 UTC
Red Hat Issue Tracker OSP-19475 0 None None None 2022-10-17 13:45:50 UTC
Red Hat Product Errata RHBA-2023:0271 0 None None None 2023-01-25 12:30:28 UTC

Description Fernando Royo 2022-10-04 09:53:49 UTC
When a VM is deleted, if over the port associated is a ServiceMonitor check created, an event should be triggered to notify that the port is unreachable anymore. This event apppears not been arriving to the driver agent on the ovn-provider, basically because when a vm is deleted the member is not updated to ERROR status (a HM should exist over the VM)

Reproducible via:

- Create a VM with services running on port 80 and 22
- Create a lb over the same VM with listener on port (80 or 22) and a member over the VM VIP
- Create a hm
- Delete the VM 
- No ServiceMonitorUpdateEvent is printed on driver-agent logs.

Comment 10 errata-xmlrpc 2023-01-25 12:29:56 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenStack Platform 17.0.1 bug fix and enhancement advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:0271


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