search

application-research / estuary-hosted-infrastructure

The main repository for EHI
MIT License
3 stars 0 forks source link

Re-integrate the CheckMK playbook #6

Closed PC-Admin closed 1 year ago

PC-Admin commented 1 year ago

We had a minor regression lately with these commits,

https://github.com/application-research/estuary-hosted-infrastructure/commit/b3dc8c35eaa25418d29243be7942b72ac28cbc2e https://github.com/application-research/estuary-hosted-infrastructure/commit/1a9d102c43acef016e83fb7eff71e48403338f3a

It seems like there was a permission error or something with the https://github.com/application-research/checkmk-playbook repository.

Here was the related error message:

TASK [Update project using git] ************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to init/update submodules: Submodule 'playbooks/checkmk-playbook' (git@github.com:application-research/checkmk-playbook.git) registered for path 'playbooks/checkmk-playbook'\nCloning into '/var/lib/awx/projects/_15__estuary_hosted_infrastructure/playbooks/checkmk-playbook'...\ngit@github.com: Permission denied (publickey).\r\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\nfatal: clone of 'git@github.com:application-research/checkmk-playbook.git' into submodule path '/var/lib/awx/projects/_15__estuary_hosted_infrastructure/playbooks/checkmk-playbook' failed\nFailed to clone 'playbooks/checkmk-playbook'. Retry scheduled\nCloning into '/var/lib/awx/projects/_15__estuary_hosted_infrastructure/playbooks/checkmk-playbook'...\ngit@github.com: Permission denied (publickey).\r\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct a…

Worth investigating later on just to keep things neat.

Zorlin commented 1 year ago

it looks like the issue was probably that it was missing a master branch and broke AWX

TASK [Update project using git] ************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Unable to determine hashes of submodules", "rc": 128, "stderr": "fatal: ambiguous argument 'origin/master': unknown revision or path not in the working tree.\nUse '--' to separate paths from revisions, like this:\n'git  [...] -- [...]'\nfatal: run_command returned non-zero status for playbooks/logtail-playbook\n.\n", "stderr_lines": ["fatal: ambiguous argument 'origin/master': unknown revision or path not in the working tree.", "Use '--' to separate paths from revisions, like this:", "'git  [...] -- [...]'", "fatal: run_command returned non-zero status for playbooks/logtail-playbook", "."], "stdout": "Entering 'playbooks/delta-playbook'\nd00738c7ed8ec8d2d8ed16082039421e55b42cdc\nEntering 'playbooks/ehi-proxmaas'\nd70041668f2376581fcc2eb0061a4b585bb9f13f\nEntering 'playbooks/estuary-postgres-playbook'\n558dbded5bc90dde1de9a888ac1c9eaf4fa05f3e\nEntering 'playbooks/haproxy-cluster-playbook'\nbe754d…

I remember being essentially forced to delete it to complete my work that day

Zorlin commented 1 year ago

Oh. You registered the submodule with its SSH path. You MUST use the https path instead, that is probably the issue.

See https://github.com/application-research/estuary-hosted-infrastructure/blob/main/.gitmodules for reference, none of those use git+ssh

PC-Admin commented 1 year ago

Resolved with: https://github.com/application-research/estuary-hosted-infrastructure/pull/14