Hi,
On Tue, Feb 08, 2022 at 11:03:11PM +, Wayne Warren wrote:
> > Do you have the possiblity to test the most current 4.19.y version?
>
> I'm currently attempting to do this following instructions on
>
Hi,
On Tue, Feb 08, 2022 at 01:11:47AM +, Wayne Warren wrote:
> Hey there, if I understand correctly this bug which definitely affects
> linux 4.19.208-1 was closed because it doesn't affect some other version?
> 5.10.40-1?
Right, and because the BTS can then close a bug in multiple
Processing control commands:
> severity -1 important
Bug #1003844 [src:linux] linux-image-4.19.0-18-amd64: Cilium fails on linux
4.19.0-18
Severity set to 'important' from 'grave'
> forwarded -1 https://issueexplorer.com/issue/cilium/cilium/17647
Bug #1003844 [src:linux] linux-image-4.1
Control: severity -1 important
Control: forwarded -1 https://issueexplorer.com/issue/cilium/cilium/17647
Control: fixed -1 5.10.40-1
Hi Vladimir,
On Sun, Jan 16, 2022 at 07:45:31PM +, Vladimir Tiukhtin wrote:
> Package: src:linux
> Version: 4.19.208-1
> Severity: grave
> Justification:
Here is an interesting discussion in cilium thread
https://issueexplorer.com/issue/cilium/cilium/17647
Package: src:linux
Version: 4.19.208-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
Regular "apt upgrade" made kubernetes cluster driven by cilium unusable
* What exactly did you do (or not do) that was effective (or ineffective)?
6 matches
Mail list logo
