Skip to content
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

Problem: Semaphore checking out wrong git repo when trying to run a playbook #2053

Open
semaiwald opened this issue May 24, 2024 · 2 comments

Comments

@semaiwald
Copy link

semaiwald commented May 24, 2024

Issue

I have multiple projects running in SemaphoreUI with different repositories in each project.
Sometimes when I try to run a task template the SemaphoreUI trys to checkout a repository from a different project that isn't even specified as a repository in that current project.
This randomly happens to already existing task templates that already worked completely fine.

As a current workaround I just simply recreate the tasktemplate and it works again but its still frustrating to always have to recreate task templates.

Impact

Ansible (task execution)

Installation method

Package

Database

BoltDB

Browser

Chrome

Semaphore Version

v2.9.75

Ansible Version

ansible [core 2.16.6]
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.10/dist-packages/ansible
  ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/local/bin/ansible
  python version = 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (/usr/bin/python3)
  jinja version = 3.0.3
  libyaml = True

Logs & errors

Before recreating the task template:
image

After recreating the task template:
image

Specified repositories:
image

You can see that the repository that was checkouted in the first screenshot is not defined in the repositories list. It is defined in a completely different project but it still checkouts it.

Manual installation - system information

Linux ansible 5.15.0-73-generic #80-Ubuntu SMP Mon May 15 15:18:26 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

I am using apache2 as a reverse proxy.

Configuration

No response

Additional information

No response

@polskafan
Copy link

polskafan commented May 31, 2024

I can confirm this bug. I have the same issue, when running with multiple projects.

11:32:07 AM Task 2147483571 added to queue
11:32:07 AM Started: 2147483571
11:32:07 AM Run TaskRunner with template: Setup Woodpecker Agent
11:32:07 AM Preparing: 2147483571
11:32:07 AM Updating Repository https://*****/woodpecker-agent-setup.git
11:32:08 AM From https://*****/ansible-server-update

Ansible Version

Running latest docker version behind traefik

Semaphore v2.9.112-4f95ac8e-1717078250

@btzq
Copy link

btzq commented Jul 10, 2024

Hi, we are encountering this issue as well.

But our scenario is when we are getting Semaphore to call a artifact in a remote folder (which we specify the entire file path and full file name). It seems to grab the wrong file intermittently. And to resolve this, we have recreate the task.

We have multiple projects and tasks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: To triage
Development

No branches or pull requests

4 participants