diff options
| author | Peter Hunt <pehunt@redhat.com> | 2020-05-12 14:32:00 -0400 |
|---|---|---|
| committer | Peter Hunt <pehunt@redhat.com> | 2020-05-12 15:36:33 -0400 |
| commit | f4b59c74a799a27d74ea23aca4e61df787b80647 (patch) | |
| tree | e0fc69a881be3e2d66d0507dff850325a11788b2 /vendor/go.etcd.io | |
| parent | 5b4e91db73a80f31f67b7c28832527e64b074b74 (diff) | |
| download | podman-f4b59c74a799a27d74ea23aca4e61df787b80647.tar.gz podman-f4b59c74a799a27d74ea23aca4e61df787b80647.tar.bz2 podman-f4b59c74a799a27d74ea23aca4e61df787b80647.zip | |
cgroup: skip unified if we are using v1
There exists a chance for a node to be booted in v1, but have reminents of v2. An example is this CRI-O ci run: https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gcs/origin-federated-results/pr-logs/pull/cri-o_cri-o/3565/test_pull_request_crio_critest_fedora/11243/
We fail because we are incorrectly writing to the unified path, because we are v1. We should not write to the unified path if we are v1
Signed-off-by: Peter Hunt <pehunt@redhat.com>
Diffstat (limited to 'vendor/go.etcd.io')
0 files changed, 0 insertions, 0 deletions