Bug 2166883
| Summary: | OVN cluster containers are not updated during update. | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Sofer Athlan-Guyot <sathlang> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Sofer Athlan-Guyot <sathlang> |
| Status: | CLOSED ERRATA | QA Contact: | Archana Singh <arcsingh> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 17.1 (Wallaby) | CC: | dabarzil, jmarcian, jpretori, kgilliga, mburns |
| Target Milestone: | beta | Keywords: | Triaged |
| Target Release: | 17.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-heat-templates-14.3.1-1.20230423001017.004ef6e.el9ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-08-16 01:13:41 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: | |||
Note, there's a clone of this bug for OSP17 there: Bug #2166883 Hi, wrong link in the previous for OSP17.0, here it is Bug #2166969 *** Bug 2182682 has been marked as a duplicate of this bug. *** Review tested and working without any cut in control plane. 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 |
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.