galaxyproject / galaxyproject/training-material

Error related to automated cleanups of Galaxy created files - Hands-on: Configuring PostgreSQL Backups

Open
#4,519 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

admin question
Dominant language
HTML
Stars
367
Forks
1.1k
Avg merge
16h 27m
Merged PRs (30d)
49

Description

At this step https://training.galaxyproject.org/training-material/topics/admin/tutorials/backup-cleanup/tutorial.html#user-created-files after having installed gxadmin ( version: 0.0.12) with Ansible and made the changes to galaxy.yml and group_vars/galaxyservers.yml for Galaxy Created Files , I get this error when I run the playbook:

fatal: [galaxy.vm.fedcloud.eu]: FAILED! => 
  msg: |-
    An unhandled exception occurred while templating '{{ (galaxy_tmpclean_log is not true) | ternary(
        ((galaxy_tmpclean_log is none) | ternary(
            '>/dev/null',
            '>>' ~ galaxy_tmpclean_log
        )),
        ''
    ) }}'. Error was a <class 'ansible.errors.AnsibleError'>, original message: template error while templating string: no test named 'true'. String: {{ (galaxy_tmpclean_log is not true) | ternary(
        ((galaxy_tmpclean_log is none) | ternary(
            '>/dev/null',
            '>>' ~ galaxy_tmpclean_log
        )),
        ''
    ) }}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Hands-on: Configuring PostgreSQL Backups tutorial at the linked user-created-files step, then inspect the gxadmin 0.0.12 configuration in galaxy.yml and group_vars/galaxyservers.yml. Reproduce the playbook run and trace the galaxy_tmpclean_log template error; done means the cleanup configuration runs without the Ansible "no test named 'true'" failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
ansible, postgresql
Domain
devops, documentation
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.