Error deploying to fleet

balena deploy is resulting in an error:

Request error: The request was unsuccessful

When the balena-cli is rerun with --debug mode we get the following:

UnauthorisedError: Request error: The request was unsuccessful
    at wrapResponseError (/snapshot/balena-cli/node_modules/@balena/compose/dist/release/models.js:14:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async createRelease (/snapshot/balena-cli/node_modules/@balena/compose/dist/release/api.js:102:13)
    at async Object.create (/snapshot/balena-cli/node_modules/@balena/compose/dist/release/api.js:15:21)
    at async createRelease (/snapshot/balena-cli/build/utils/compose.js:75:40)
    at async runSpinner (/snapshot/balena-cli/build/utils/compose_ts.js:831:16)
    at async deployProject (/snapshot/balena-cli/build/utils/compose_ts.js:780:22)
    at async DeployCmd.deployProject (/snapshot/balena-cli/build/commands/deploy/index.js:146:27)
    at async DeployCmd.run (/snapshot/balena-cli/build/commands/deploy/index.js:50:25)
    at async DeployCmd._run (/snapshot/balena-cli/node_modules/@oclif/core/lib/command.js:302:22)
    at async Config.runCommand (/snapshot/balena-cli/node_modules/@oclif/core/lib/config/config.js:425:25)
    at async run (/snapshot/balena-cli/node_modules/@oclif/core/lib/main.js:95:16)
    at async /snapshot/balena-cli/build/app.js:81:13
    at async Promise.all (index 2)
    at async oclifRun (/snapshot/balena-cli/build/app.js:100:5)
    at async Object.run (/snapshot/balena-cli/build/app.js:113:9)

This has just begun to happen with multiple SWEs this morning (I deployed successfully 9:09 AM EST).

It was a permissions error! We changed the role of our developers and did not realize that you need edit permissions on a fleet to upload Balena releases.

1 Like

Hello @realz thanks for sharing the solution of your issue!

And welcome to the balena community!

1 Like