[roll] Roll fuchsia [netstack-migration] Schedule Collaborative Reboot

When stack_migration observes a change to the automated/user setting
that is different from its `current_boot` value, it schedules a
collaborative reboot.

Once the collaborative reboot is initiated by the product, the device
will reboot and start up with the automated setting. This effectively
allows the device to self apply changes in the Netstack version.

There's additional logic in place to cancel the collaborative reboot,
should the setting change again (back to the original value).

Original-Bug: 380873116
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1193375
Original-Revision: b5f19927864bd0ee99ddfd8644f0e06614e3599b
GitOrigin-RevId: 6396f7b4e549f4f192d3a519e5edb6dbdfeb020e
Change-Id: I1cff3502611fd413110fa96f63aa905b880a2dc0
1 file changed
tree: c1b28d85e8932e643841f2db6cdf2991ad2bead6
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.