Comment 17 for bug 1787760

I realize our conversation is off-topic of the original issue but this may be as good of a place as any to have it. Firstly, I want to complement the kolla-ansible team on responding to these issues and I do understand your statements above.

However, the bifracted support schedules between the kolla-ansible and the rest of the OS community, see also https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases and https://releases.openstack.org/, creates issues as bug fixes are rolled into extended maintenance (EM) branches but these changes are not at least regression tested with kolla-ansible.

One of the reasons for the the change EM schedules was obviously to reduce the pain associated with upgrading. As a reference, my company's upgrade from Queens to Rocky via kolla-ansible caused several weeks of downtime. Beyond debugging at least one of the core project upgrades, many of the services just do not work correctly and therefore have been removed/are not used. For example, Freezer's and Karbor's dashboard breaks Horizon and therefore had to be removed. Searchlight also fails to which I reported the issue in May 2020; there has been no response (https://bugs.launchpad.net/kolla-ansible/+bug/1881222). I believe these should have been picked up in regression testing and/or prechecks; they were not picked up in at least the prechecks.

One suggestion is to remove support for projects and/or functionality that is unstable or does not have a specific majority level. Maintaining a release schedule that is consistent with the OS community should be a priority for the kolla-ansible project. Again, I appreciate your support and I do like the project.

Switching back to the original issue, has the merged change made its way into the containers such that a kolla-ansible pull will pull corrected zun containers?