- Controller sosreport: http://file01.intranet.prod.int.ams2.redhat.com/moddi/pub/sosreport-lab-controller01-777777777-2019-11-06-loxtbik.tar.xz
- Undercloud sosreport: http://file01.intranet.prod.int.ams2.redhat.com/moddi/pub/sosreport-undercloud-77777777-2019-11-06-ffduhpg.tar.xz
*** Bug 1769473 has been marked as a duplicate of this bug. ***
As Alex said, Leapp upgraded to latest RHEL8.1 in the controller, however Red Hat's registry didn't have the images updated yet so we can see a difference in the RHEL version between the host and the containers: [heat-admin@lab-controller01 ~]$ sudo podman run -it --name haproxy_init_test --net host 172.16.0.1:8787/rhosp15-rhel8/openstack-haproxy:15.0-76 bash ()[root@lab-controller01 /]# cat /etc/redhat-release Red Hat Enterprise Linux release 8.0 (Ootpa) [heat-admin@lab-controller01 ~]$ cat /etc/redhat-release Red Hat Enterprise Linux release 8.1 (Ootpa) Restoring Michelle's comment https://bugzilla.redhat.com/show_bug.cgi?id=1769473#c4: So, unfortunately, pcmk requires to have the same content across host and HA containers (in order to remove this restriction in pcmk/pcs https://bugzilla.redhat.com/show_bug.cgi?id=1603613 would have to get fixed). So right now the only way to 'fix' this is to either: A) use a rhel 8.0 overcloud with the rhel-8.0 based containers B) get some rhel 8.1 HA containers built B.1) Either we have releng rebuild them based on 8.1 content or B.2) we build them ourselves. Now on to B.2) we could probably work on some commands to do exactly that if there is interest/need ?
*** Bug 1769472 has been marked as a duplicate of this bug. ***
I think hosts should use 8.0 channels and not move to 8.1 until it's properly supported and tested in osp15.
Hi Alfredo, Thanks fore stepping in. That 8.1 bits are introducing the problem here is clear, however we are using the documented software repos, which immediately fall into the new bits after 8.1 GA. The expected/natural flow should be to have 8.1 containers available at the same time CDN has 8.1 bits too. Otherwise if freezing the software channel in 8.0 was a mandatory requirement for 15, somehow contradicts previous statements and introduces other challenges like the lack of ability to do a minor upgrade (if patching is required for security reasons for example). Best Regards, --- Mauro S. Oddi
we are working in a new OSP15 async release with updated containers and images to 8.1-
Closing EOL, OSP 15 has been retired as of Sept 19