-
Notifications
You must be signed in to change notification settings - Fork 503
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
Bootstrap package upload failure over ~55MB. #25533
Comments
FYI @lukeheath |
We're missing an extended read timeout on this endpoint...just like I originally missed this on software edits. Will throw in a PR now for a fix and test in the AM. Should be able to repro this by uploading a large-ish package over a throttled connection. |
jk, testing tonight. To repro, grab the Chrome Enterprise pkg (~200MB) and try uploading as a bootstrap package on a connection throttled to 20 Mbps up. Time to upload will be ~80 sec., which is longer than our default request deadline. With the fix, the file eventually uploads. |
…5536) For #25533 - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files) for more information. - [x] A detailed QA plan exists on the associated ticket (if it isn't there, work with the product group's QA engineer to add it) - [x] Manual QA for all new/changed functionality
…5536) For #25533 - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files) for more information. - [x] A detailed QA plan exists on the associated ticket (if it isn't there, work with the product group's QA engineer to add it) - [x] Manual QA for all new/changed functionality
…5536) For #25533 - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files) for more information. - [x] A detailed QA plan exists on the associated ticket (if it isn't there, work with the product group's QA engineer to add it) - [x] Manual QA for all new/changed functionality
…5536) For #25533 - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files) for more information. - [x] A detailed QA plan exists on the associated ticket (if it isn't there, work with the product group's QA engineer to add it) - [x] Manual QA for all new/changed functionality
…5536) For #25533 - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files) for more information. - [x] A detailed QA plan exists on the associated ticket (if it isn't there, work with the product group's QA engineer to add it) - [x] Manual QA for all new/changed functionality
QA Notes First reproduced on 4.62.0, got the following in the logs: Tested on 4.62.2 Tested on 4.63.0 as well, and was able to successfully upload a package. |
Larger files in view, |
Fleet version: v4.61.0
Web browser and operating system: Chrome 131.0.6778.265
💥 Actual behavior
When uploading a file that is over ~55 MB or so, the upload fails and the following log entry shows up on the server:
🧑💻 Steps to reproduce
🕯️ More info (optional)
It looks like we should be limited to 512 MB here as it is hard coded at
https://github.com/fleetdm/fleet/blob/main/server/service/apple_mdm.go#L2240-L2277
This behavior may be inconsistent as customer reported eventual success after multiple tries.
The text was updated successfully, but these errors were encountered: