We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I deployed cos proxy from edge
cos-proxy-monitors n/a error 1 cos-proxy edge 70 no hook failed: "monitors-relation-joined"
and its in error on
FileNotFoundError: [Errno 2] No such file or directory: 'nrpe_exporter-amd64'
As a result of 883ede2 the only binary that gets downloaded is named nrpe_exporter-aarch64
nrpe_exporter-aarch64
# ls /var/lib/juju/agents/unit-cos-proxy-monitors-0/charm LICENSE README.md dispatch hooks icon.svg lib manifest.yaml metadata.yaml nrpe_exporter-aarch64 revision src templates vector venv
Im not sure what the cleanest fix is given that https://github.com/canonical/nrpe_exporter/releases/tag/0.2.6 only has releases for arm64 and amd64 but not aarch64.
Perhaps you could release a binary for aarch64 and simplify the curl logic in charmcraft.yaml?
charmcraft.yaml
cos-proxy-operator/charmcraft.yaml
Line 29 in 4e65ee9
The text was updated successfully, but these errors were encountered:
monitors_relation_joined
nrpe_exporter-amd64
Successfully merging a pull request may close this issue.
Enhancement Proposal
I deployed cos proxy from edge
cos-proxy-monitors n/a error 1 cos-proxy edge 70 no hook failed: "monitors-relation-joined"
and its in error on
FileNotFoundError: [Errno 2] No such file or directory: 'nrpe_exporter-amd64'
As a result of 883ede2
the only binary that gets downloaded is named
nrpe_exporter-aarch64
Im not sure what the cleanest fix is given that https://github.com/canonical/nrpe_exporter/releases/tag/0.2.6 only has releases for arm64 and amd64 but not aarch64.
Perhaps you could release a binary for aarch64 and simplify the curl logic in
charmcraft.yaml
?cos-proxy-operator/charmcraft.yaml
Line 29 in 4e65ee9
The text was updated successfully, but these errors were encountered: