search

solita / ansible-role-solita.jenkins

Ansible role: Jenkins, completely configured with Ansible
MIT License
23 stars 10 forks source link

Failed to installing plugins #21

Open ismaelfernandezscmspain opened 7 years ago

ismaelfernandezscmspain commented 7 years ago

Hi,

I am having problems to install plugins with the role:

2017/04/19 09:52:10 ui:     amazon-ebs: TASK [solita.jenkins : Install Jenkins plugins.] *******************************
    amazon-ebs: TASK [solita.jenkins : Install Jenkins plugins.] *******************************
2017/04/19 09:52:14 ui:     amazon-ebs:  [WARNING]: Consider using 'become', 'become_method', and 'become_user' rather
    amazon-ebs:  [WARNING]: Consider using 'become', 'become_method', and 'become_user' rather
2017/04/19 09:52:14 ui:     amazon-ebs: than running sudo
    amazon-ebs: than running sudo
2017/04/19 09:52:14 ui:     amazon-ebs:
    amazon-ebs:
2017/04/19 09:52:14 ui:     amazon-ebs: failed: [127.0.0.1] (item=(censored due to no_log)) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"}
    amazon-ebs: failed: [127.0.0.1] (item=(censored due to no_log)) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"}
2017/04/19 09:52:18 ui:     amazon-ebs: failed: [127.0.0.1] (item=(censored due to no_log)) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"}
    amazon-ebs: failed: [127.0.0.1] (item=(censored due to no_log)) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"}
2017/04/19 09:52:23 ui:     amazon-ebs: failed: [127.0.0.1] (item=(censored due to no_log)) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"}
    amazon-ebs: failed: [127.0.0.1] (item=(censored due to no_log)) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"}

Later:

amazon-ebs: failed: [127.0.0.1] (item=(censored due to no_log)) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"}
2017/04/19 09:51:11 packer: 2017/04/19 09:51:11 Remote command exited with '2': cd /tmp/packer-provisioner-ansible-local/roles/ && ansible-galaxy install -v -r /tmp/provisioning/requirements.yml -p /tmp/packer-provisioner-ansible-local/roles/ && ANSIBLE_VAULT_PASSWORD_FILE=/tmp/.vault_pass ansible-playbook /tmp/packer-provisioner-ansible-local/roles/playbook.yml --extra-vars "boto_profile=global-dev install_autojobs_github=false" -c local -i /tmp/packer-provisioner-ansible-local/roles/packer-provisioner-ansible-local782692170
2017/04/19 09:51:11 packer: 2017/04/19 09:51:11 [INFO] RPC endpoint: Communicator ended with: 2
2017/04/19 09:51:11 [INFO] RPC client: Communicator ended with: 2
2017/04/19 09:51:11 [INFO] RPC endpoint: Communicator ended with: 2
2017/04/19 09:51:11 [INFO] 18634 bytes written for 'stdout'
2017/04/19 09:51:11 [INFO] 0 bytes written for 'stderr'
2017/04/19 09:51:11 packer: 2017/04/19 09:51:11 [INFO] 18634 bytes written for 'stdout'
2017/04/19 09:51:11 packer: 2017/04/19 09:51:11 [INFO] RPC client: Communicator ended with: 2
2017/04/19 09:51:11 packer: 2017/04/19 09:51:11 [INFO] 0 bytes written for 'stderr'
2017/04/19 09:51:11 ui:     amazon-ebs: failed: [127.0.0.1] (item=(censored due to no_log)) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"}
    amazon-ebs: failed: [127.0.0.1] (item=(censored due to no_log)) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"}
2017/04/19 09:51:11 ui:     amazon-ebs: to retry, use: --limit @/tmp/packer-provisioner-ansible-local/roles/playbook.retry
    amazon-ebs: to retry, use: --limit @/tmp/packer-provisioner-ansible-local/roles/playbook.retry
2017/04/19 09:51:11 ui:     amazon-ebs:
    amazon-ebs:
2017/04/19 09:51:11 ui:     amazon-ebs: PLAY RECAP *********************************************************************
    amazon-ebs: PLAY RECAP *********************************************************************
2017/04/19 09:51:11 ui:     amazon-ebs: 127.0.0.1                  : ok=41   changed=20   unreachable=0    failed=1
    amazon-ebs: 127.0.0.1                  : ok=41   changed=20   unreachable=0    failed=1
2017/04/19 09:51:11 ui:     amazon-ebs:
    amazon-ebs:
2017/04/19 09:51:11 ui: ==> amazon-ebs: Step "StepProvision" failed
==> amazon-ebs: Step "StepProvision" failed
2017/04/19 09:51:11 ui: ask: ==> amazon-ebs: [c] Clean up and exit, [a] abort without cleanup, or [r] retry step (build may fail even if retry succeeds)?
==> amazon-ebs: [c] Clean up and exit, [a] abort without cleanup, or [r] retry step (build may fail even if retry succeeds)?

Do you know what I do?

noidi commented 7 years ago

The latest version of solita.jenkins passes the Jenkins admin user's password to the Jenkins CLI on the command line. I added no_log: yes to the relevat tasks to keep the password from being printed in Ansible's output, which is fine when everything works correctly but makes debugging painful. I intend to explore other ways of hiding the password, so I can get rid of the no_log in a future release.

In the meantime, you can edit roles/solita.jenkins/tasks/plugins.yml and remove the line no_log: yes. This should hopefully give you some idea of what the error might be.

noidi commented 7 years ago

I've released v1.3.1 that removes most of the no_log statements. Could you give it a try?