-
Notifications
You must be signed in to change notification settings - Fork 166
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
"balena os configure" induces hundreds of AccessDenied errors in api container and crashes #165
"balena os configure" induces hundreds of AccessDenied errors in api container and crashes #165
Comments
Can you try deleting all resources related to the |
Unfortunately I don't see anythin with such device types or aliases . Strange types are: srd3-xavier, ccon-01, pc-20, lv-dart, nitrogen8mm-dwe, srd3-xavier . Acttually I grepped both database dump, openbalena runtime folder and balena-cli source (from which I build cli I use) and I didn't manage to find anything. What can it be? May 06 16:00:59 1b8ea8a621f5 api[1211]: Failed to get device type build data for srd3-xavier/2.101.3 Access Denied AccessDenied: Access Denied |
I still don't get any idea where could those types could be stored. I tried grepping both database sql dump and balena code, found no clues. |
Those errors are all related to balena-io/open-balena-api#1433 , which is fixed in balena-io/open-balena-api#1434 ... but requires that you specify the exact device types you want, see: |
I have a related question.
How does one figure out all dependent slugs given device type? What should CONTRACT_ALLOWLIST look like? |
@DoJuSm - I would suggest looking through https://github.com/balena-io/contracts/tree/master/contracts For example, start with hw.device-type/raspberrypi3/contract.json and you'll see it references
Doing the same for hw.device-type/raspberrypi4-64/contract.json gets you:
And for Doing the same for hw.device-type/asus-tinker-board-s/contract.json gets you'll see both
... but if you check hw.device-family/tinkerboard/contract.json you'll see that it references
|
Hi, Kind regards, |
If device is to be configured first time, client side "balena os configure" command induces a hundreds if not thousands of such errors in API container:
Mar 15 19:26:05 1b8ea8a621f5 api[1214]: Failed to get device type build data for ccon-01/2.102.0 Access Denied AccessDenied: Access Denied
Mar 15 19:26:05 1b8ea8a621f5 api[1214]: at Request.extractError (/usr/src/app/node_modules/aws-sdk/lib/services/s3.js:711:35)
Mar 15 19:26:05 1b8ea8a621f5 api[1214]: at Request.callListeners (/usr/src/app/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
Mar 15 19:26:05 1b8ea8a621f5 api[1214]: at Request.emit (/usr/src/app/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
Mar 15 19:26:05 1b8ea8a621f5 api[1214]: at Request.emit (/usr/src/app/node_modules/aws-sdk/lib/request.js:686:14)
Mar 15 19:26:05 1b8ea8a621f5 api[1214]: at Request.transition (/usr/src/app/node_modules/aws-sdk/lib/request.js:22:10)
Mar 15 19:26:05 1b8ea8a621f5 api[1214]: at AcceptorStateMachine.runTo (/usr/src/app/node_modules/aws-sdk/lib/state_machine.js:14:12)
Mar 15 19:26:05 1b8ea8a621f5 api[1214]: at /usr/src/app/node_modules/aws-sdk/lib/state_machine.js:26:10
and 4 from 5 times "balena os configure" ends with "ECONNRESET" error. But, sometimes (1 from 5 times) this command succeeds.
I'm using versions from master branch:
OPENBALENA_API_VERSION_TAG=v0.209.2
OPENBALENA_DB_VERSION_TAG=v5.1.2
OPENBALENA_MDNS_PUBLISHER_VERSION_TAG=v1.9.2
OPENBALENA_REGISTRY_VERSION_TAG=v2.25.3
OPENBALENA_S3_VERSION_TAG=v2.13.10
OPENBALENA_VPN_VERSION_TAG=v11.4.6
The text was updated successfully, but these errors were encountered: