Comment # 11 on bug 1171770 from Richard Brown

(In reply to Francisco Freitas from comment #10)
> (In reply to Richard Brown from comment #9)
> > Hi all - I've been looking at this all day, here is the current status:
> > 
> > I can confirm it happens with both kubicctl and kubeadm clusters made from
> > the current snapshots.
> > 
> > We know this doesn't occur on kubicctl clusters with multi-masters, which
> > suggests haproxy somehow works around the issue.
> 
> Might want to verify this. Tried a multi-master deployment two releases
> back. I had no issue with the master nodes but I still got the issue on the
> worker nodes. (Will test it on the latest release again tonight).
> 
> > This now leads me to wonder if the kernel or runc updates are to blame,
> > which I will look at tomorrow, unless someone beats me to it first.
> > 
> > Sorry that this doesn't look like it will be a quick fix. Anyone got any
> > other info that might help?
> 
> Couldn't it be tested by downgrading the kernel ?

Sure but a) from where?
and b) I've worked enough today, I think I'd like a bit of a break before
picking this up tomorrow ;)