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

Bug 2166969

Summary: OVN cluster containers are not updated during update.
Product: Red Hat OpenStack Reporter: Sofer Athlan-Guyot <sathlang>
Component: openstack-tripleo-heat-templatesAssignee: Sofer Athlan-Guyot <sathlang>
Status: CLOSED EOL QA Contact: Archana Singh <arcsingh>
Severity: high Docs Contact:
Priority: high    
Version: 17.0 (Wallaby)CC: jpretori, kgilliga, mburns, mciecier
Target Milestone: asyncKeywords: Triaged
Target Release: 17.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-14.3.1-0.20230522090509.feca772.el9ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-10-10 12:21:23 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:
Bug Depends On:    
Bug Blocks: 2172611    

Description Sofer Athlan-Guyot 2023-02-03 18:16:24 UTC 
This bug was initially created as a copy of Bug #2166883

I am copying this bug because: It affects 17.0 as well.



Description of problem: During a openstack overcloud run the all the
overcloud's containers should be updated.

But here the OVN database containers are not updated:

    osp17.0 -> 17.1 update
    [tripleo-admin@controller-1 ~]$ sudo podman ps | grep ovn
    503897e01169 undercloud-0.ctlplane.redhat.local:8787/rh-osbs/rhosp17-openstack-ovn-nb-db-server:17.0_20220908.1 kolla_start 3 weeks ago Up 24 hours ovn_cluster_north_db_server
    6723bdc08d43 undercloud-0.ctlplane.redhat.local:8787/rh-osbs/rhosp17-openstack-ovn-sb-db-server:17.0_20220908.1 kolla_start 3 weeks ago Up 24 hours ovn_cluster_south_db_server
    bf80025be019 undercloud-0.ctlplane.redhat.local:8787/rh-osbs/rhosp17-openstack-ovn-northd:17.0_20220908.1 kolla_start 3 weeks ago Up 24 hours (healthy) ovn_cluster_northd
    8afe1e0aa88f undercloud-0.ctlplane.redhat.local:8787/rh-osbs/rhosp17-openstack-nova-novncproxy:17.1_20230130.1 kolla_start 20 hours ago Up 20 hours (healthy) nova_vnc_proxy
    f5fccc07d2ee undercloud-0.ctlplane.redhat.local:8787/rh-osbs/rhosp17-openstack-ovn-controller:17.1_20230130.1 kolla_start 20 hours ago Up 20 hours (healthy) ovn_controller

Afected containers:
 - ovn-nb-db-server;
 - ovn-sb-db-server;
 - ovn-northd

Since wallaby, OVN databases are not under pacemaker control, and uses
the cluster feature of the dbs. So the "pacemaker" code that was
handling the update is not there anymore.

Those containers are bootstrapped using docker_container step 0 which
is not run as part of the common deploy step during the update, which
goes from step 1 to 6.

The configuration is then done, not using puppet but ansible, meaning
we don't have any docker_container step >= 1 to trigger an container
update in the current update framework.

For an update to happen here we must have explicit step in the
"update_tasks" part of the playbook.


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


How reproducible: all the time.

We don't have downstream CI failure on this as currently we don't have
code that check that the container have changed. We are working on
adding that check to the CI. Upstream CI doesn't include OVN cluster
database in its setup. We are looking into having that covered as
well.

This was discovered during a manual check by Mikolaj Ciecierski.