Bug 2131962

Summary: HM ServiceMonitor not detecting member(VM) hard stopped
Product: Red Hat OpenStack Reporter: Fernando Royo <froyo>
Component: python-ovn-octavia-providerAssignee: Fernando Royo <froyo>
Status: CLOSED ERRATA QA Contact: Eran Kuris <ekuris>
Severity: medium Docs Contact:
Priority: medium    
Version: 17.0 (Wallaby)CC: averdagu
Target Milestone: z1Keywords: Triaged
Target Release: 17.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-ovn-octavia-provider-1.0.1-0.20221122190308.bbf881f.el9ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-01-25 12:29:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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