Issue
Maybe this was an RTFM issue, but a containerized Docker version upgrade from 2.17.26 to 2.18.12 specifically did not update the VENV environment. Was pointing to 11.1.0 instead of the 13.5.0 Ansible environment.
The only give away was the system information pop-up showing "Ansible was not found on this system"...
Maybe something to put into an upgrade document for those of us coming from 2.17.x to 2.18.x on a containerized Docker version.
For those digging, execute a shell into your container path and update the VNEV variable with the new path in /opt/semaphore/apps/xx
Impact
Ansible (task execution)
Installation method
Docker
Database
SQLite
Browser
Firefox
Semaphore Version
OLD: 2.17.26
NEW: 2.18.12
Ansible Version
Logs & errors
No response
Manual installation - system information
No response
Configuration
No response
Additional information
No response
Issue
Maybe this was an RTFM issue, but a containerized Docker version upgrade from 2.17.26 to 2.18.12 specifically did not update the VENV environment. Was pointing to 11.1.0 instead of the 13.5.0 Ansible environment.
The only give away was the system information pop-up showing "Ansible was not found on this system"...
Maybe something to put into an upgrade document for those of us coming from 2.17.x to 2.18.x on a containerized Docker version.
For those digging, execute a shell into your container path and update the VNEV variable with the new path in /opt/semaphore/apps/xx
Impact
Ansible (task execution)
Installation method
Docker
Database
SQLite
Browser
Firefox
Semaphore Version
OLD: 2.17.26
NEW: 2.18.12
Ansible Version
Logs & errors
No response
Manual installation - system information
No response
Configuration
No response
Additional information
No response