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

Error in last change template: '>' is not supported between instances of 'str' and 'int' #21

Open
maurorosero opened this issue Dec 31, 2019 · 2 comments

Comments

@maurorosero
Copy link

#13 ### SUMMARY
<When run the playbook get following error:
'>' is not supported between instances of 'str' and 'int'

ISSUE TYPE
  • Bug Report
COMPONENT NAME

template: templates/001_admin.rb.j2

ANSIBLE VERSION

ansible 2.9.2 python version = 3.6.9 (default, Nov 7 2019, 10:44:02) [GCC 8.3.0]


CONFIGURATION

ANSIBLE_NOCOWS(/etc/ansible/ansible.cfg) = True
ANSIBLE_PIPELINING(/etc/ansible/ansible.cfg) = True
ANSIBLE_SSH_CONTROL_PATH_DIR(/etc/ansible/ansible.cfg) = /tmp/ansible/cp
CACHE_PLUGIN_CONNECTION(/etc/ansible/ansible.cfg) = /tmp
COMMAND_WARNINGS(/etc/ansible/ansible.cfg) = False
DEFAULT_EXECUTABLE(/etc/ansible/ansible.cfg) = /bin/bash
DEFAULT_LOG_PATH(/etc/ansible/ansible.cfg) = /var/log/ansible.log
DEFAULT_MANAGED_STR(/etc/ansible/ansible.cfg) = Ansible managed: {file} modified
DEFAULT_ROLES_PATH(/etc/ansible/ansible.cfg) = ['/etc/ansible/roles']
DEPRECATION_WARNINGS(/etc/ansible/ansible.cfg) = False
DISPLAY_SKIPPED_HOSTS(/etc/ansible/ansible.cfg) = True
HOST_KEY_CHECKING(/etc/ansible/ansible.cfg) = False
INTERPRETER_PYTHON(/etc/ansible/ansible.cfg) = auto_silent
RETRY_FILES_ENABLED(/etc/ansible/ansible.cfg) = False

OS / ENVIRONMENT

Centos 7

STEPS TO REPRODUCE

run playbook :

ansible-playbook -i inventory/hosts install-gitlab.yml  -l gitlab -vv
TEMPORAL SOLUTION

revert to previous changes of last commit

@maurorosero
Copy link
Author

if playbook run succesfully once time, the following runs don get this error. Fail in clean first time running.

@pavelpikta
Copy link
Member

@maurorosero hi, thanks for the issue. Will be investigated and fixed on new release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants