Description

A Fleet bug fix which affects use of fleetctl destroy in my deployment is available upstream in Fleet v0.12.0 and up, but the CoreOS Fleet is quite far behind the upstream Fleet.

Would it be possible either to backport the fix in coreos/fleet#1417 into Fleet v0.11.x or ship a standard train CoreOS which includes Fleet 0.12.x or up? Because no current version of CoreOS includes Fleet 0.12.x or up as of yet.

coreos/fleet#1383 (comment)
coreos/fleet#1417 (comment)

CoreOS Version

Issue applies to all published CoreOS releases up to and including the current latest, 1097.0.0. This can be confirmed by verifying the Fleet versions listed in all releases noted in the release notes at https://coreos.com/releases/ .

Environment

This is a base dependency issue which is independent of hardware, cloud, or hypervisor releases.

Expected Behavior

CoreOS should include more recent branches of upstream Fleet on a regular basis to prevent missing important bug fixes.

Actual Behavior

CoreOS does not include more recent branches of upstream Fleet on a regular basis to prevent missing important bug fixes.

Reproduction Steps

NOTE: See coreos/fleet#1383 for more details.

1. Run fleetctl destroy on a service that's not active for whatever reason.
2. Obsolete copies of Fleet print storms of Error destroying units: googleapi: Error 404: unit does not exist messages and return spurious POSIX process return codes.
3. Current copies of Fleet do not print the messages or return errors and just work.

Other Information

N/A.