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

/etc/step-ca/.ansible/tmp has the wrong permission #251

Open
ethrgeist opened this issue Feb 1, 2023 · 0 comments
Open

/etc/step-ca/.ansible/tmp has the wrong permission #251

ethrgeist opened this issue Feb 1, 2023 · 0 comments

Comments

@ethrgeist
Copy link

When running the example ca.yml playbook for the first time on a fresh vm, there is an error from Ansible:

TASK [maxhoesel.smallstep.step_ca : Initialize CA] ********************************************************************************************************************************************************************************************************************************************
[WARNING]: Module remote_tmp /etc/step-ca/.ansible/tmp did not exist and was created with a mode of 0700, this may cause issues when running as another user. To avoid this, create the remote_tmp dir with the correct permissions manually

The Step Remove initial provisioner then fails:

TASK [maxhoesel.smallstep.step_ca : Remove initial provisioner] *******************************************************************************************************************************************************************************************************************************
fatal: [manager-1]: FAILED! => {"changed": false, "msg": "Error running command 'step-cli ca provisioner remove tmp_provisioner --ca-config=/etc/step-ca/config/ca.json'. See stderr for details.", "stderr": "client GET https://manager-1.example.local/admin/admins failed: dial tcp 10.254.254.240:443: connect: connection refused\n", "stderr_lines": ["client GET https://manager-1.example.local/admin/admins failed: dial tcp 10.254.254.240:443: connect: connection refused"], "stdout": "", "stdout_lines": []}

Running the playbook a second time is without error and everything is setup.

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

1 participant