Archy's Blog

NOTE: this guide exists for Upgrading from v3.3 to v3.4 as well -->  here With the current version, the  official documentation  is quite good and can be referenced. I would recommend executing all of these commands in a tmux session so that your session will remain on the server in case anything happens to your workstation. Start by checking for running tasks that would prohibit an update: [root@katello01 ~]# foreman-rake katello:upgrade_check Next, update the katello host and reboot if yum tells you to: [root@katello01 ~]# dnf -4y --refresh update [root@katello01 ~]# dnf needs-restarting -r If there were any updates to foreman-related packages, make sure foreman is in a consistent state: [root@katello01 ~]# foreman-maintain service stop [root@katello01 ~]# foreman-installer --scenario katello When the katello services have started again, upgrade the release-rpms: [root@katello01 ~]# dnf -4y update https://yum.theforeman.org/releases/3.5/el8/x86_64/for...

Since version 18.0.0, awx is supposed to be installed using the awx-operator  which requires kubernetes or a k8s-compatible platform such as openshift or minikube. I'll assume you have a running kubernetes cluster with: a default storage class ( tutorial )  metallb up and running ( tutorial ) First, create the namespace, operatorgroup and subscription for the awx-operator: [ 19:37:49 ] - archy ~/kubernetes/awx> cat << EOF >> 0-awx-operator.yml --- apiVersion: v1 kind: Namespace metadata: name: awx ... --- apiVersion: operators.coreos.com/v1 kind: OperatorGroup metadata: name: operatorgroup namespace: awx spec: targetNamespaces: - awx ... --- apiVersion: operators.coreos.com/v1alpha1 kind: Subscription metadata: name: awx namespace: awx spec: channel: alpha name: awx-operator source: operatorhubio-catalog sourceNamespace: olm ... EOF Apply the manifest ...