Bug 2125531

Summary: Nova notifications with error response are not retried
Product: Red Hat OpenStack Reporter: Slawek Kaplonski <skaplons>
Component: openstack-neutronAssignee: Slawek Kaplonski <skaplons>
Status: CLOSED ERRATA QA Contact: Maor <mblue>
Severity: medium Docs Contact:
Priority: medium    
Version: 17.0 (Wallaby)CC: chrisw, jlibosva, jschluet, lmartins, mblue, scohen
Target Milestone: gaKeywords: Triaged
Target Release: 17.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-neutron-18.5.1-1.20221021162909.9d826bc.el9ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 2125534 (view as bug list) Environment:
Last Closed: 2023-08-16 01:12:09 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:
Bug Depends On:    
Bug Blocks: 2125534, 2125539    

Description Slawek Kaplonski 2022-09-09 08:42:42 UTC
Sometimes Neutron is failing to send notification to Nova due to timeout, refused connection or another HTTP error.
Whenever such event occurs, Neutron notifier for Nova will log an error and consider it's job done.
Meanwhile, since there is no retry mechanism, Nova will wait till timeout and put VM in error state.

Comment 1 Jakub Libosvar 2023-02-03 20:14:58 UTC
Re-targetting to 17.1

Comment 3 Lukas Svaty 2023-06-16 08:13:29 UTC
Bulk moving target milestone to GA after the release of Beta on 14th June '23.

Comment 13 errata-xmlrpc 2023-08-16 01:12:09 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 (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), 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/RHEA-2023:4577