Comment 18 for bug 1877089

@brian-murray and @acb
This bug is in between 'Fix Released' for groovy.
Please see also zfcpdump-kernel changelog:
zfcpdump-kernel (5.4-0ubuntu2) groovy; urgency=medium
  * Switch to 5.4 base from focal (5.4.0-49.53).
  * Drop fix to zfcpdump config, included in 5.4.
  * Rename zfcpdump_part.image, to zfcpdump-image, to match current
    s390-tools expectations. LP: #1877089
The zfcpdump kernel got now updated to the focal kernel.

I think that this bug was raised right after focal was released (and probably before groovy development was really open) - it had initially only a series entry for focal and it was at the beginning assumed that only focal is affected (groovy s390-tool was not there yet).
It took a while to get this topics discussed and achieve more clarification (and the bug states changed quite a bit).
At some point in time a first upload was done on focal - that got dropped then and replaced by a revised version that still sits in focal unapproved (since 2020-09-17)
https://launchpad.net/ubuntu/focal/+queue?queue_state=1&queue_text=zfcpdump-kernel

Meanwhile groovy evolved and it became clear that this needs to be tacked too, but the first focal upload was already out. Hence the groovy upload came late, means after focal (so too late according to the SRU process, hence comment #15).

Since the zfcpdump-kernel package/image is quite self sufficient and static, the regression risk is very low, since the zfcpdump-kernel image is even independent from the OS series, hence it can be build in one series (now focal) and then be used in focal or newer. Please see also bug description: [Publication] and [Regression Potential]