You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to modify an existing Ansible inventory entry which uses file type and absolute path, it is not saved because of an error requesting a relative path. Adding an inventory with a absolute path works fine.
The documentation suggests using absolute path for this type of approach.
Impact
Web-Frontend (what users interact with)
Installation method
Docker
Database
BoltDB
Browser
Firefox, Microsoft Edge
Semaphore Version
2.10.11
Ansible Version
No response
Logs & errors
No Docker logs.
Manual installation - system information
Red Hat Enterprise Linux 8.10
Linux <snip> 4.18.0-513.9.1.el8_9.x86_64 #1 SMP Thu Nov 16 10:29:04 EST 2023 x86_64 x86_64 x86_64 GNU/Linux
Docker version 24.0.7, build afdd53b
Docker Compose version v2.21.0
Configuration
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
mattroot
changed the title
Problem: Unable to modify a repository
Problem: Unable to modify a repository using absolute path
Jul 11, 2024
mattroot
changed the title
Problem: Unable to modify a repository using absolute path
Problem: Unable to modify an inventory entry using absolute path
Jul 11, 2024
Issue
When attempting to modify an existing Ansible inventory entry which uses
file
type and absolute path, it is not saved because of an error requesting a relative path. Adding an inventory with a absolute path works fine.The documentation suggests using absolute path for this type of approach.
Impact
Web-Frontend (what users interact with)
Installation method
Docker
Database
BoltDB
Browser
Firefox, Microsoft Edge
Semaphore Version
2.10.11
Ansible Version
No response
Logs & errors
No Docker logs.
Manual installation - system information
Red Hat Enterprise Linux 8.10
Configuration
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: