Comment 15 for bug 1888000

We have determined nothing has changed in those kernels from last cycle or this cycle. We think something changed in the CPC environment that might have triggered what we think might be an old bug. But we need to CPC help to identify the "last good kernel" and the "first bad kernel". Once we can isolate, we can have a more useful investigation

We have determined that ib_iser.ko is not in 4.15.0-1069-kvm but it wasn't there in the previous cycle's kernel and is not in the current proposed 4.15.0-1071.72 cycle either. I don't think we should try to make a change, re-spin, then ask the CPC team to test, especially since we never made the breaking-change in the first place (as far as we know at least). Once we know what changed we can make the right choice.

Hopefully this is a reasonable approach