MessagingTimeout after create a instance in Openstack 17.1

Solution In Progress - Updated -

Environment

  • Red Hat OpenStack Platform 17.1

Issue

After upgraded successfully from Openstack 16.2 to 17.1, all instances created shows the status of ERROR and a fault of Timed out waiting for a reply of a message.

Resolution

  1. Find where RetryFilter was set in templates.
find <templates path>/* -type f -exec grep -l 'RetryFilter' {} \;

  1. Edit the file and remove RetryFilter from nova::scheduler::filter::scheduler_enabled_filters: list.

  2. Deploy the overcloud.

  3. Test the creation of a instance.

Root Cause

RetryFilter is not available in OSP 17 as mentioned in the Advisory RHEA-2022:6543, BZ2028171.

Diagnostic Steps

  1. Check the status of the instance.
(overcloud) [stack@undercloud ~]$ openstack server show <instance ID>
...
| OS-EXT-STS:vm_state                  | error
...
| fault                                | {"code": 500, "created": "2023-10-27T16:10:34Z", "message": "MessagingTimeout", "details": "Traceback (most recent call last):
...
|                                      | oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply to message ID 0000000000000000000
  1. Check nova scheduler logs in controllers.
[root@overcloud-controller-0 ~]# grep 'RetryFilter' /var/log/containers/nova/nova-scheduler.log
...
2023-10-29 14:53:01.654 2 ERROR nova nova.exception.SchedulerHostFilterNotFound: Scheduler Host Filter RetryFilter could not be found.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments