Skip to content

Problem: New template 'Ansible Playbook' do not work after Update #2879

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

Closed
recretix-support opened this issue Apr 3, 2025 · 4 comments
Closed
Assignees
Labels

Comments

@recretix-support
Copy link

Issue

After Update to 2.13.7 the copy and create function of New template 'Ansible Playbook' no not work anymore.

Image

Impact

Web-Frontend (what users interact with)

Installation method

Package

Database

MySQL

Browser

Firefox

Semaphore Version

2.13.7

Ansible Version

2.17.9

Logs & errors

Image

Manual installation - system information

No response

Configuration

No response

Additional information

No response

@jpdsc
Copy link

jpdsc commented Apr 6, 2025

Same issue here but it started for me around version: v2.13.2
Tried the new v2.13.8-beta3 version and same issue.

Cleared cache:

  • Creating a new task now works and editable / able to copy.
  • When trying to copy an existing task (created before upgrade), it fails with error in console:
    Image
  • After editing a task before upgrade and saving it, copy works again. However, a new error is in console:
    Image
    Edit: applies for any task

@fgimian
Copy link

fgimian commented Apr 7, 2025

For me everything worked correctly on v2.13.7, but all templates are blank on v2.13.8. I have rolled back to v2.13.7 until this is resolved. 😄

@Marcel-4210
Copy link

Since #2884 doesn't seem to get reopened I'll continue on here...

v2.13.10 fixed the add/edit functionalities, but copying templates still doesn't work on all templates.
Workaround 1: Edit the template, change anything about it and save it.
Workaround 2: In the database open the table "project_template" and set the templates "task_params" field to "{}" instead of NULL.

@fiftin fiftin self-assigned this Apr 19, 2025
@fiftin
Copy link
Collaborator

fiftin commented Apr 21, 2025

Fixed in 2.13.14

@fiftin fiftin closed this as completed Apr 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants