[CentOS-devel] [TripleO] [CloudSIG] Errors on Recent TripleO Deployment - Ussuri and Victoria

Wed Feb 10 18:29:40 UTC 2021
Nathan McGarvey <nathanmcgarvey at gmail.com>

To anyone on the cloud SIG team, specifically dealing with a TripleO

    As of this week, a stock install of the "Ussuri" and "Victoria"
releases of TripleO undercloud fail due to internal puppet module issues
as follows:

    Note that at least Ussuri worked recently (in the last few weeks):

        "puppet-user: Error: no parameter named 'key_size' (file:
/etc/puppet/modules/tripleo/manifests/certmonger/haproxy.pp, line: 102)
on Certmonger_certificate[haproxy-external-cert] (file:
/etc/puppet/modules/tripleo/manifests/certmonger/haproxy.pp, line: 102)
on node centos8-testing.localdomain"

    It seams that this may have been fixed in

    ... "Could not find class ::neutron::plugins::ml2::ovs_driver" ...

   I'm not sure if this is related/fixed, but it may be:

    Steps to reproduce:
        Base install of CentOS8.3 Minimal (VM and baremetal behave the same)
        install centos-release-openstack-<version>
        [Optional?] dnf module disable container-tools:rhel8 and dnf
module enable container-tools:2.0
        dnf install python3-tripleoclient ceph-ansible openstack-selinux
        dnf distro-sync
        add the "stack" user and such, add sudo rules, etc.
        [copy undercloud.conf.sample to undercloud.conf]
            NOTE: minor customization of IPs in my test environment.
        [Optional] generate the container parameters yaml
        openstack undercloud install --verbose

     Has anybody else experienced this? Any ideas on how to rectify the
issue or prevent this from happening in the future. This seems like a
pretty big breakage since it is effectively a no-go for any new install
at least. (I'd assume the overcloud install will break in the same
manner since it should be using the same repos and containers.)

    Please pardon my ignorance if I'm missing something obvious since
I'm a new poster to this thread.