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

[Bug]: Cosmovisor's add-upgrade creates a binary that's not executable #20061

Closed
1 task done
freak12techno opened this issue Apr 16, 2024 · 0 comments · Fixed by #20062
Closed
1 task done

[Bug]: Cosmovisor's add-upgrade creates a binary that's not executable #20061

freak12techno opened this issue Apr 16, 2024 · 0 comments · Fixed by #20062
Assignees
Labels
C:Cosmovisor Issues and PR related to Cosmovisor T:Bug

Comments

@freak12techno
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

Better show on example:

validator@pion-testnet ~/neutron #v3.0.4 ❯ cosmovisor add-upgrade v3.0.4 ~/go/bin/neutrond
9:04PM INF Using /home/validator/go/bin/neutrond for v3.0.4 upgrade module=cosmovisor
9:04PM INF Upgrade binary located at /home/validator/.neutrond/cosmovisor/upgrades/v3.0.4/bin/neutrond module=cosmovisor
validator@pion-testnet ~/neutron #v3.0.4 ❯ /home/validator/.neutrond/cosmovisor/upgrades/v3.0.4/bin/neutrond version
zsh: permission denied: /home/validator/.neutrond/cosmovisor/upgrades/v3.0.4/bin/neutrond

I guess it's because of this line

if err := os.WriteFile(path, data, 0o600); err != nil {
that assigns the permissions as 600 (owner can read and write but not execute, others cannot read and write) and it should be changed to something more relaxed (not sure yet what).

Feel free to assign me to this issue if you want btw.

Cosmos SDK Version

cosmovisor version: v1.5.0

How to reproduce?

See above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C:Cosmovisor Issues and PR related to Cosmovisor T:Bug
Projects
Status: 🥳 Done
Development

Successfully merging a pull request may close this issue.

2 participants