| 2022-08-09 13:00:01 |
Takashi Kajinami |
bug |
|
|
added bug |
| 2022-08-09 13:00:15 |
Takashi Kajinami |
tripleo: importance |
Undecided |
Critical |
|
| 2022-08-09 13:00:19 |
Takashi Kajinami |
tripleo: assignee |
|
Takashi Kajinami (kajinamit) |
|
| 2022-08-09 13:12:04 |
OpenStack Infra |
tripleo: status |
New |
In Progress |
|
| 2022-08-15 23:47:57 |
Takashi Kajinami |
summary |
Support customizing [oslo_messaging_rabbit] heartbeat_in_pthread |
[oslo_messaging_rabbit] heartbeat_in_pthread should be False for non-wsgi services |
|
| 2022-08-15 23:50:07 |
Takashi Kajinami |
description |
Description
===========
We have recently found an issue with recent oslo.messaging and some processes like nova-compute or neutron-server do not behave properly with the current defaults.
example: https://bugs.launchpad.net/oslo.messaging/+bug/1934937
So far the valid workaround is to set the [oslo_messaging_rabbit] heartbeat_in_pthread option to False for all non-wsgi services but current tht does not manage this parameter.
As a short term solution until the issue is fixed in oslo.messaging, we need ;
- The HeartbeatInPthread parameter per service, to set the parameter for a specific service
- Make the parameter defaults to False, to override the default until the issue is cleared in oslo.messaging (or in any different layer) |
Description
===========
We have recently found an issue with recent oslo.messaging and some processes like nova-compute or neutron-server do not behave properly with the current defaults.
example: https://bugs.launchpad.net/oslo.messaging/+bug/1934937
We are currently discussing disabling reverting the default value in oslo.messaging in oslo/stable team.
However as a short term solution until the issue is fixed in oslo.messaging, we need to set this parameter to False. |
|
| 2022-08-16 14:31:43 |
Takashi Kajinami |
description |
Description
===========
We have recently found an issue with recent oslo.messaging and some processes like nova-compute or neutron-server do not behave properly with the current defaults.
example: https://bugs.launchpad.net/oslo.messaging/+bug/1934937
We are currently discussing disabling reverting the default value in oslo.messaging in oslo/stable team.
However as a short term solution until the issue is fixed in oslo.messaging, we need to set this parameter to False. |
Description
===========
We have recently found an issue with recent oslo.messaging and some processes like nova-compute or neutron-server do not behave properly with the current defaults.
examples:
https://bugs.launchpad.net/oslo.messaging/+bug/1934937
https://bugs.launchpad.net/oslo.messaging/+bug/1961402
We are currently discussing disabling reverting the default value in oslo.messaging in oslo/stable team, but discussion about backportability is still under discussion.
Considering the impact of he problem, we should set this parameter to False now to workaround the problem until the issue is fixed in oslo.messaging. |
|
| 2022-08-16 15:05:23 |
Takashi Kajinami |
tags |
|
wallaby-backport-potential |
|
| 2022-08-16 20:37:24 |
OpenStack Infra |
tripleo: status |
In Progress |
Fix Released |
|
| 2022-08-19 19:51:38 |
OpenStack Infra |
tags |
wallaby-backport-potential |
in-stable-wallaby wallaby-backport-potential |
|
