-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Bump OS to release version 13.0 #3520
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
sairon
commented
Aug 13, 2024
- Improve resiliency of skopeo operations in hassio package (Improve resiliency of skopeo operations in hassio package #3416)
- Linux: Update kernel to 6.6.34 (Linux: Update kernel to 6.6.34 #3420)
- Bump docker/build-push-action from 5.4.0 to 6.0.0 (Bump docker/build-push-action from 5.4.0 to 6.0.0 #3421)
- Fix boot slot A marked as bad on the very first boot (Fix boot slot A marked as bad on the very first boot #3435)
- Generate version information for RAUC when rauc.db is empty (Generate version information for RAUC when rauc.db is empty #3436)
- Bump docker/build-push-action from 6.0.0 to 6.1.0 (Bump docker/build-push-action from 6.0.0 to 6.1.0 #3444)
- Linux: Update kernel to 6.6.35 (Linux: Update kernel to 6.6.35 #3443)
- Linux: Update kernel to 6.6.36 (Linux: Update kernel to 6.6.36 #3448)
- Bump docker/build-push-action from 6.1.0 to 6.2.0 (Bump docker/build-push-action from 6.1.0 to 6.2.0 #3454)
- Bump OS to development version 13.0.dev0
- Fix rauc hook to save and restore the grub environment (Fix rauc hook to restore machine-id in new grub environment #3451)
- Remove old code from rauc-hook and GRUB env initialization (Remove old code from rauc-hook and GRUB env initialization #3457)
- Populate grubenv with RAUC data in clean aarch64 OS image (Populate grubenv with RAUC data in clean aarch64 OS image #3458)
- Linux: Update kernel to 6.6.37 (Linux: Update kernel to 6.6.37 #3463)
- Refer to GRUB instead of Barebox in top-level readme (Refer to GRUB instead of Barebox in top-level readme #3464)
- Bump docker/build-push-action from 6.2.0 to 6.3.0 (Bump docker/build-push-action from 6.2.0 to 6.3.0 #3466)
- Bump docker/setup-buildx-action from 3.3.0 to 3.4.0 (Bump docker/setup-buildx-action from 3.3.0 to 3.4.0 #3465)
- Enable aQuantia AQtion ethernet driver (Enable aQuantia AQtion ethernet driver #3467)
- Linux: Update kernel to 6.6.38 (Linux: Update kernel to 6.6.38 #3469)
- Enable i6300ESB watchdog driver for generic-aarch64 (Enable i6300ESB watchdog driver for generic-aarch64 #3468)
- Revert "Revert GRUB2 patch causing boot failure on some old x86_64 BIOSes (Revert GRUB2 patch causing boot failure on some old x86_64 BIOSes #3324)" (Revert "Revert GRUB2 patch causing boot failure on some old x86_64 BIOSes (#3324)" #3470)
- Bump docker/build-push-action from 6.3.0 to 6.4.0 (Bump docker/build-push-action from 6.3.0 to 6.4.0 #3475)
- Linux: Update kernel to 6.6.41 (Linux: Update kernel to 6.6.41 #3482)
- Bump docker/setup-buildx-action from 3.4.0 to 3.5.0 (Bump docker/setup-buildx-action from 3.4.0 to 3.5.0 #3485)
- Bump docker/build-push-action from 6.4.0 to 6.5.0 (Bump docker/build-push-action from 6.4.0 to 6.5.0 #3486)
- Bump docker/login-action from 3.2.0 to 3.3.0 (Bump docker/login-action from 3.2.0 to 3.3.0 #3484)
- Bump buildroot to 2024.02.4 (Bump buildroot to 2024.02.4 #3487)
- Use EROFS for the root filesystem (Use EROFS for the root filesystem #3456)
- Reduce log spam from Docker health checks (Reduce log spam from Docker health checks #3491)
- Enable Netfilter MARK match kernel configuration (Enable Netfilter MARK match kernel configuration #3492)
- Allow EROFS compression for Rockchip kernels (Allow EROFS compression for Rockchip kernels #3493)
- Linux: Update kernel to 6.6.43 (Linux: Update kernel to 6.6.43 #3495)
- Bump docker/setup-buildx-action from 3.5.0 to 3.6.0 (Bump docker/setup-buildx-action from 3.5.0 to 3.6.0 #3496)
- Patch genimage to force first usable LBA @ 34 to fix RPi 5/Windows issues (Patch genimage to force first usable LBA @ 34 to fix RPi 5/Windows issues #3497)
- Use GRUB2 legacy loader only on some Intel Atom boards specifically (Use GRUB2 legacy loader only on some Intel Atom boards specifically #3498)
- Linux: Update kernel to 6.6.44 (Linux: Update kernel to 6.6.44 #3500)
- Bump docker/setup-buildx-action from 3.6.0 to 3.6.1 (Bump docker/setup-buildx-action from 3.6.0 to 3.6.1 #3501)
- Test landing page is reachable without internet connection (Test landing page is reachable without internet connection #3499)
- Bump OS to pre-release version 13.0.rc1
- Bump ODROID N2's U-Boot to v2024.01 again (Bump ODROID N2's U-Boot to v2024.01 again #3508)
- Increase block size of kernel squashfs image to 128K (Increase block size of kernel squashfs image to 128K #3509)
- Fix writing U-Boot environment on ODROID-M1 (Fix writing U-Boot environment on ODROID-M1 #3510)
- Enable eMMC HS200 mode in Green's U-Boot defconfig (Enable eMMC HS200 mode in Green's U-Boot defconfig #3511)
- Bump OS to pre-release version 13.0.rc2
- Bump OS to release version 13.0
We still face occasional build errors when fetching from the Docker registry fails and is not retried with the Skopeo's built-in retry mechanism that was enabled in #1866. This happens on some network failures, or when premature EOF is returned when fetching the HTTP data. Seems we're not the only ones having such issues [1]. To workaround this, add a generic retry shell function that simply retries when the command ends with a non-zero status, no matter what was the actual cause of the error. [1] https://www.github.com/containers/common/issues/654
Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 5.4.0 to 6.0.0. - [Release notes](https://github.com/docker/build-push-action/releases) - [Commits](docker/build-push-action@v5.4.0...v6.0.0) --- updated-dependencies: - dependency-name: docker/build-push-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
On the very first boot, grubenv doesn't exist and loading and saving it silently fails. However, it is later created by the hassos-persists script and the missing information are added by grub.cfg on the next boot. As the consequence, when RAUC tries to get information from grubenv on the first boot, ORDER variable is missing and the slot is reported as bad. Fixes #3376
RAUC currently doesn't know the version of the booted slot when booted for the first time or after wiping the data partition. As a result `ha os info` is missing this information too. As there's no built-in mechanism for generating these data by RAUC itself, add a oneshot service that checks if the boot slot information is contained in the rauc.db and if not, then generate it. RAUC seems to cope quite well even with bogus data contained in rauc.db but in any case, a test has been added to check that everything works as expected.
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 6.1.0 to 6.2.0. - [Release notes](https://github.com/docker/build-push-action/releases) - [Commits](docker/build-push-action@v6.1.0...v6.2.0) --- updated-dependencies: - dependency-name: docker/build-push-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Without a machine-id, the next boot will be considered as a first boot, and any external data disk will be disabled. Fixes #3247.
With upgrade path enforced in standard HAOS upgrade procedure, we don't need to keep some old code anymore. This means that upgrade from some very old HAOS version (pre-8.0) to HAOS 13+ will fail in the install-check hook but this is rather desirable.
While not as bad as in 87a6c84, because the grubenv already exists in the image, RAUC still complains about missing ORDER on the very first boot on aarch64. Populate the environment in the same way as we do for other GRUB platforms.
We don't use Barebox for over two years since d1cc739, remove the forgotten mention of it in readme.
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Enable driver for wide range of multi-gigabit NICs. Fixes #3438
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 6.4.0 to 6.5.0. - [Release notes](https://github.com/docker/build-push-action/releases) - [Commits](docker/build-push-action@v6.4.0...v6.5.0) --- updated-dependencies: - dependency-name: docker/build-push-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [docker/login-action](https://github.com/docker/login-action) from 3.2.0 to 3.3.0. - [Release notes](https://github.com/docker/login-action/releases) - [Commits](docker/login-action@v3.2.0...v3.3.0) --- updated-dependencies: - dependency-name: docker/login-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* buildroot d03dda4fcf...baa16784d2 (5): > Merge tag '2024.02.4' into 2024.02.x-haos > fs/erofs: add config options for dedupe, fragments and ztailpacking > fs/erofs: add LZMA compression, allow configurable compression level > package/erofs-utils: add config option for LZMA compression > package/erofs-utils: bump to 1.7.1
* Use name.sh functions for paths in genimage Paths for images generated outside of genimage were not used in genimage definitions. Use them as the single source of truth. Images generated by genimage itself (e.g. kernel.img) don't need to use those functions, so remove the unused ones. * Use EROFS instead of SquashFS for root FS * Enabled EROFS in common kernel fragment * RootFS image switched to EROFS with options to get decent compression * rootfstype removed from kernel command line * Get size of correct FS image in GH build summary
Reduce verbosity from deactivated Docker mounts, triggered by the Docker healthcheck. These messages do not carry any value for us and logs supplied by users are often spammed mostly with these. Moreover, they sometimes cause confusion that something is wrong, see for example #3021. Unfortunately, it's not possible to use LogFilterPatterns= here, because it's not applied to these messages, as explicitly said in the docs: Filtering is based on the unit for which LogFilterPatterns= is defined meaning log messages coming from systemd(1) about the unit are not taken into account. runc 1.2.0 supposedly should fix this, but it's unclear when it would be available, so let's stick to this solution (reducing verbosity from debug to notice for all units `run-docker-*.mount`) for the time being.
Make the Netfitler MARK match kernel config a OS required configuration. This config is required by the OpenThread Border Router add-on. Fixes: home-assistant/addons#3698
Rockchip config fragment had EROFS compression explicitly disabled. Remove that option and also remove the EROFS one, as it's already set in common config.
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…sues (#3497) Genimage sets the first usable LBA to the offset of the first partition. While it shouldn't be an issue in theory, Windows may do some nasty things with the GPT header afterwards which breaks the Raspberry Pi bootloader, manifesting as Before purpose of this behavior is clarified in [1], add a downstream patch that sets the first usable LBA back to 34, which was the value that was used before migrating to Genimage in #3388. Since changing this value (hopefully) doesn't have any other consequences, and the images now should be closer to pre-genimage builds, no more side-effects are expected from this change. [1] https://www.github.com/pengutronix/genimage/issues/262 Fixes #3437
…3498) * Use GRUB2 legacy loader only on some Intel Atom boards specifically Previous revert of GRUB2 change that introduced usage of the generic EFI loader for all x86 boards in #3324 caused regressions, the one confirmed is #3348. This commit adds a specific patch that identifies the broken platforms based on SMBIOS data gathered in #3305 and falls back to the legacy loader there. Tested on Intel D525MW (falls back) and QEMU (no fallback). * Enable GRUB's smbios module Having smbios command in GRUB can help in future debugging, e.g. to add more CPUs that should use the linux loader fallback.
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Test landing page is reachable without internet connection Add test that checks user is able to access the landing page even when HAOS has no internet connection. We still need some sort of outgoing connectivity, so outgoing connection attempts don't end up with "network is unreachable". To simulate this, restricted network is created for the QEMU instance used in the test, and when everything is started, unresponsive default gateway is added. This intents to test regression that was fixed by home-assistant/supervisor#5204, Supervisor 2024.7.0+ is thus needed for this test to pass. * Bump requirements for tests
We previously reverted the bump because we were unsure where the eMMC issues are coming from. Now we know some of them were caused by incompatible eMMCs then never worked from the beggining, and attempt to fix them (by changing the frequency) caused some other side effects. Bump U-Boot back to the version used generally and continue from there. (cherry picked from commit 50a0062)
While mksquashfs uses this value by default, Genimage's default is 4K. This is far too low value and results in slower kernel load, especially on embedded boards with a flash drive. Explicitly set it to 128K to generate same images as in pre-genimage builds. (cherry picked from commit edba18f)
Apply the same patch we applied in #3412 for Green. At that time I thought the patch was already applied upstream for M1 and haven't checked, but it turns out it wasn't true. Apply it here before we get U-Boot with that patch series [1] included. [1] https://patchwork.ozlabs.org/project/uboot/cover/[email protected]/ (cherry picked from commit d6fa83a)
agners
approved these changes
Aug 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.