Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2096334

Summary:	Containers are immediately SIGKILLed instead of first being gracefully shutdown with a SIGTERM
Product:	Red Hat OpenStack	Reporter:	Cédric Jeanneret <cjeanner>
Component:	tripleo-ansible	Assignee:	Cédric Jeanneret <cjeanner>
Status:	CLOSED ERRATA	QA Contact:	Joe H. Rahme <jhakimra>
Severity:	low	Docs Contact:
Priority:	low
Version:	16.2 (Train)	CC:	bdobreli, tkajinam
Target Milestone:	z4	Keywords:	Triaged
Target Release:	16.2 (Train on RHEL 8.4)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tripleo-ansible-0.8.1-2.20220622005831.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-12-07 19:23:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Cédric Jeanneret 2022-06-13 14:48:05 UTC

This bug was initially created as a copy of Bug #2080585

I am copying this bug because:

The issue isn't scoped to libvirt only, and is addressed by a patch available since wallaby (osp-17):
https://review.opendev.org/c/openstack/tripleo-ansible/+/748832

We need this BZ to track the patch, and do the proper backport work for 16.2.4


Description of problem:

Similar of this BZ `https://bugzilla.redhat.com/show_bug.cgi?id=2011409` which fixed in 16.2.2. However, after scale up the stack, the Cu  experience that nova_libvirt fails to come up only on the old compute nodes, the newly deployed compute nodes do not have issues.

~~~
 systemctl status tripleo_nova_libvirt.service
● tripleo_nova_libvirt.service - nova_libvirt container
   Loaded: loaded (/etc/systemd/system/tripleo_nova_libvirt.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2022-04-08 00:31:12 CEST; 5h 48min ago
  Process: 395229 ExecStopPost=/usr/bin/podman stop -t 10 nova_libvirt (code=exited, status=0/SUCCESS)
  Process: 395073 ExecStart=/usr/libexec/tripleo-start-podman-container nova_libvirt (code=exited, status=1/FAILURE)
 Main PID: 393879 (code=exited, status=1/FAILURE)
~~~


Version-Release number of selected component (if applicable):

podman-3.0.1-7.module+el8.4.0+12906+0cce23da.x86_64


Actual results:

After deploying (scalee up) the already deployed stack, Cu not able to start the nova_libvirt service on the old compute nodes.

Expected results:

After deploying (scalee up) the already deployed stack, Cu should be able to start the nova_libvirt service on the old compute nodes.


Additional info:

There is an errata `https://access.redhat.com/errata/RHBA-2021:40931` and the issue has been fixed RHOSP 16.2.2. However, the cu confirmed that they are having the issue only on the nodes that are updated. When scaling up the stack, the newly deployed compute nodes do not have issues.

Comment 3 Takashi Kajinami 2022-06-13 15:00:33 UTC

>>>>> NOTE <<<<<<

The tripleo-container-manage role in tripleo-ansible is Tech Preview in RHOSP16.2 .
 https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2/html-single/director_installation_and_usage/index#assembly_managing-containers-with-ansible

So the feature is NOT supported and users should use paunch instead in general.

Comment 4 Bogdan Dobrelya 2022-06-13 15:40:54 UTC

This is likely not an urgent priority, since paunch is default in 16.x. And this issue is related to tripleo-ansilbe container manager, which is TP there.

Comment 5 Bogdan Dobrelya 2022-06-13 15:40:54 UTC

This is likely not an urgent priority, since paunch is default in 16.x. And this issue is related to tripleo-ansilbe container manager, which is TP there.

Comment 6 Takashi Kajinami 2022-06-15 00:37:39 UTC

Setting severity/priority to low because the feature is not officially supported .

Comment 16 errata-xmlrpc 2022-12-07 19:23:18 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 16.2.4), 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-2022:8794