Hi
I have a working AWX lab on Centos 7 with local docker.
How do I upgrade AWX or new ansible ex 2.4?
Do I “git rebase origin” and run the install agin? Will it keep my AWX settings/history?
Tanks
Christer
ansible 2.4 was only just released this morning so it might not have landed in the ansible el7 repository just yet (though the installer will pick it up).
You should just need to re-run the installer and your settings and history will likely be preserved… if you are using a standalone docker install then it sets up a persistent directory for the postgres container.
Hi
It works really well.
Now it filling my disk with docker awx_* images. Most old work fine to delete but some get this. Safe to force?
$ sudo docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
awx_task 1.0.0.530 4becec0cbe4a 23 hours ago 997MB
awx_web 1.0.0.530 c5b0e9aae1dc 24 hours ago 970MB
awx_sdist_builder 1.0.0.493 749353e46a2f 4 days ago 543MB
awx_sdist_builder 1.0.0.519 749353e46a2f 4 days ago 543MB
awx_sdist_builder 1.0.0.530 749353e46a2f 4 days ago 543MB
centos 7 196e0ce0c9fb 9 days ago 197MB
$ sudo docker rmi 749353e46a2f
Error response from daemon: conflict: unable to delete 749353e46a2f (must be forced) - image is referenced in multiple repositories
//
Christer
you can delete the older sdist builder images but you probably don’t want to delete awx_task and awx_web
Hi
This have work well for several upgrades but now there is some issue.
The about say AWX 1.0.0.573 and it have not upgrade after that when i tried.
Now it clear it should be upgraded.
Last git fetch say 1.0.1 but still rerun the install only end with
PLAY RECAP *************************************************************************************************************************
localhost : ok=10 changed=0 unreachable=0 failed=0
$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
64ad0944c61c ansible/awx_task:latest “/tini – /bin/sh …” 2 weeks ago Up 43 minutes 8052/tcp awx_task
adb374db9bd2 ansible/awx_web:latest “/tini – /bin/sh …” 2 weeks ago Up 43 minutes 0.0.0.0:80->8052/tcp awx_web
7dbe2d864617 memcached:alpine “docker-entrypoint…” 3 weeks ago Up 43 minutes 11211/tcp memcached
7d3a3ebbac28 rabbitmq:3 “docker-entrypoint…” 3 weeks ago Up 43 minutes 4369/tcp, 5671-5672/tcp, 25672/tcp rabbitmq
529f4cd863c0 postgres:9.6 “docker-entrypoint…” 3 weeks ago Up 43 minutes 5432/tcp postgres
[christer@c7 installer]$
I have try to do a fresh git clone and rerun the installer but still unchanged system.
Before the upgrade to AWX 1.0.0.573 the ansible/awx_* had :version_id like ansible/awx_web:1.0.0.573
Regards
Christer
Update
Killing the awx containers only result in restart of the existing container.
TASK [local_docker : Activate AWX Web Container] ***********************************************************************************
changed: [localhost]
TASK [local_docker : Activate AWX Task Container] **********************************************************************************
changed: [localhost]
PLAY RECAP *************************************************************************************************************************
localhost : ok=10 changed=2 unreachable=0 failed=0
[christer@c7 installer]$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
64ad0944c61c ansible/awx_task:latest “/tini – /bin/sh …” 2 weeks ago Up 4 seconds 8052/tcp awx_task
adb374db9bd2 ansible/awx_web:latest “/tini – /bin/sh …” 2 weeks ago Up 7 seconds 0.0.0.0:80->8052/tcp
You should remove the containers themselves… you may also need to delete the existing awx_ images from your docker instance.
you need to:
`
docker stop awx_task
docker rm awx_task
docker rmi ansible/awx_task:latest
docker stop awx_web
docker rm awx_web
docker rmi ansible/awx_web:latest
ansible-playbook -i hosts install.yml
`
Is this documented anywhere? I couldn’t find it.
Not yet. As of now it’s documented right here!
Is there any issue anywhere about getting it documented? I didn’t find in when searching on Github.
it looks like the new version of the installer wipes the previous version of DB, even if mounted with persistent volume.
That is a pretty disappointing and unpleasant not to end on.
Has this issue been resolved?
Is it safe to re-run the installer now, to upgrade AWX, or is it still going to wipe the DB?