Skip to content

Problem: Vault setting seems to be lost intermittently, how to troubleshoot #2978

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
horned1 opened this issue Apr 29, 2025 · 0 comments
Open
Assignees
Milestone

Comments

@horned1
Copy link

horned1 commented Apr 29, 2025

Issue

I am experiencing an issue where the Tasks intermittently lose the 'Vault' setting, meaning the task (if it uses out vault for sensitive information, which most do) will fail. What got me looking into this is that it has happened twice to a set of task that run on a schedule. Meaning

  • I can see that it works at one point , then fails without human interaction in-between
  • It's a small controlled (static) set, which means I am 100% sure haven't copied the task which I know will loose the Vault setting.

The Semaphore server itself is updated/rebooted often, could this have some effect on this setting, is there a way to programmatically get the task settings out of semaphore, to monitor this? Any logs that might show changes in task configuration?

Impact

Ansible (task execution)

Installation method

Package

Database

BoltDB

Browser

Chrome

Semaphore Version

Semaphore version: 2.11.2-0e9490c-1735214524

Ansible Version

Logs & errors

No response

Manual installation - system information

No response

Configuration

No response

Additional information

No response

@fiftin fiftin self-assigned this Apr 29, 2025
@fiftin fiftin added this to Bugfixing Apr 29, 2025
@fiftin fiftin modified the milestones: 2.15, 2.14 Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants