fleet needs to write to etcd while gracefully shutting
down, which typically requires the etcd unit to be
active locally. Define this relation explicitly in
the fleet unit with an After=etcd.service option.
In addition to bumping to the latest stable this tweaks the default
settings for panics and lockups so that they do not need to be set in
sysctl configs. We needed to update these settings anyway and setting it
here means they will apply before boot gets around loading sysctl confs.
Previously the sysctl options set the hardlockup threshold to 5 seconds
and the softlockup threshold to 10 seconds. This is perhaps a bit too
aggressive, just use the default values of 10 and 20 seconds.
Also sysctl enabled an immediate reboot after panic, using a friendlier
60 seconds gives users a chance to see the error before the reboot.
The new Update() performs the same tasks as the old Resize()
in addition to formatting previously-unformatted partitions. This
allows children disk-layouts to repartition the base layout in
addition to resizing.
A few things of note:
- Adds patch to fix tmpfiles regression.
- Adds patch to fix VMware bridged network interfaces.
- Drops all other patches, all merged or otherwise fixed.
- v213 is a pretty big release overall, could use more testing.
This release features two new services that like networkd before it get
enabled in /etc instead of /usr. Move things back to where they belong.
Original patch from Camilo Aguilar <camilo.aguilar@gmail.com>
I started to move board files under a boards/ directory similar to how
the SDK is under sdk/ but didn't do so everywhere. This should finish
the job so everything is consistent now.
Note: This prefix is only used in developer and buildbot uploads. When
final releases are copied to $channel.release.core-os.net it doesn't use
the prefix since a) I already published urls without the prefix and b)
no sdk files are ever posted to the public release locations.
Since it isn't simple for us to provide the Python based Google Cloud
SDK tools users should be directed to the Docker container instead.
Also fix the bug report URL, not that anyone looks at it... :)
There is no need to arbitrarily bind mount all of the host system's /run
into the chroot. In fact this causes issues when the host system's /run
isn't set up in a way this script anticipates. Namely the user runtime
directory in /run/usr/$UID is another tmpfs mount on my system, leaving
the underlying directory node that is bind-mounted in with the wrong
ownership. Behave a little more like a responsible container and use a
fresh /run but continue binding /run/shm for whatever versions of Ubuntu
that depended on that behavior. Not strictly needed but go ahead and
create the user runtime directory with the correct permissions.
- Don't copy known_hosts if it doesn't exist.
- Don't bother with copying *.pub, not sure what that was for.
- Don't rewrite .ssh/config to remove internal Google ssh options.
