Octavia should support Fedora 28 base system. Initial identified tasks include: * diskimage-builder support to build F28 amphora * Check new package versions support (haproxy) * Update amphora agent code * ifcfg scripts are deprecated (amphora agent) * ifcfg scripts are deprecated (tripleo, health monitor ports)
Patch [1] proposes adding a new octavia-v2-dsvm-py35-scenario-fedora-latest job to octavia-tempest-plugin. As of today, the fedora element in diskimage-builder only supports Fedora 26 and 27 [2] so the amphora will be based on Fedora 27. The controller node will be 'latest' which is Fedora 28. [1] https://review.openstack.org/#/c/600381/ [2] https://github.com/openstack/diskimage-builder/blob/b602c05551707c58105ae9de3ab67483780a4273/diskimage_builder/elements/fedora/environment.d/10-fedora-distro-name.bash#L14-L20
My attempts to build a RHEL8 based amphora image did not succeed so far ; While I was able to deploy rhos-release to enable osp15-trunk repositories on the RHEL8 cloud image, the diskimage-builder support is still incomplete. I applied some workarounds to build a working environment and build an Amphora image: 1. locally enhance RHEL8 cloud image by adding rhos-release with the 15-trunk repositories. The CDN and test users for RHEL8 are still not in place, so this is a workaround for that. 2. local modifications to diskimage-builder codebase and to the operating system to overcome the fact the pip install diskimage-builder (from local code) did not deploy these[1] aliases. The dib rhel9 support is still a work in progress see. I reached out to Ian and offered to collaborate on that to move this forward faster. [1] https://github.com/openstack/diskimage-builder/blob/5b1844acf99d3797b1bbe02601e5ce94308cab55/setup.cfg#L65-L68 [2] https://review.openstack.org/#/c/623137/
I deployed openstack-selinux from 15-trunk to capture possible policies we'll need in addition to the existing ones. Reported bug 1684885 against openstack-selinux. Proposed a possible fix (WIP) https://github.com/nmagnezi/openstack-selinux/commit/9c21cf25f87b60f8dd13ecd4a757fd0373391c6b
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, 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-2019:2811