New install of MOI on RHEL 8 server system starts with unhealthy services

Products

• Mainframe Operational Intelligence

Issue/Introduction

Have a new installation of MOI on a server system RHEL 8.8 that starts with unhealthy services.

Resolution

Perform the following steps from the offending server machine to resolve:

Shutdown moi:
moi shutdown

Remove old network:
docker network rm ca_itoa_network

Install netavark:
yum install netavark aardvark-dns

Override podman default network configuration:
***** WRITE BELOW CONTENT TO /etc/containers/containers.conf *****
[network]

# Explicitly force "netavark" as to not use the outdated CNI networking, which it would not apply otherwise as long as old stuff is there.
# This may be removed once all containers were upgraded?
# see https://discussion.fedoraproject.org/t/how-to-get-podman-dns-plugin-container-name-resolution-to-work-in-fedora-coreos-36-podman-plugins-podman-dnsname/39493/5?u=rugk

# official doc:
# Network backend determines what network driver will be used to set up and tear down container networks.
# Valid values are "cni" and "netavark".
# The default value is empty which means that it will automatically choose CNI or netavark. If there are
# already containers/images or CNI networks preset it will choose CNI.
#
# Before changing this value all containers must be stopped otherwise it is likely that
# iptables rules and network interfaces might leak on the host. A reboot will fix this.
#
network_backend = "netavark"
***** END OF CONTENT *****

Start moi
moi startup