GKE test request won't get processed properly

[Po-Hsu Lin]

It looks like the flavour is not what we're expecting here:

{
    "date": "2019-04-19 09:37:11.887054",
    "flavour": "gke-4.15",
    "kernel-version": "4.15.0-1030.32",
    "key": "kernel.publish.proposed.bionic",
    "op": "sru",
    "package": "linux-gke-4.15",
    "pocket": "proposed",
    "series-name": "bionic",
    "sru-cycle": "2019.04.01-1",
    "who": [
        "kernel"
    ]
}

It's gke-4.15 instead of gke.
I think this is the reason why it's not working well with the request handler.

[Po-Hsu Lin (cypressyew)]

I tried to change "flavour": "gke-4.15", to "gke", but it's still not working.

[Po-Hsu Lin (cypressyew)]

OK the key is:
    "package": "linux-gke-4.15",

Should be:
    "package": "linux-gke"
in this case

[Po-Hsu Lin (cypressyew)]

There are two meta packages for the GKE kernel:
ii linux-gke 4.15.0.1030.33 amd64 Complete Google Container Engine (GKE) Linux kernel and headers
ii linux-gke-4.15 4.15.0.1030.33 amd64 Complete Google Container Engine (GKE) Linux kernel and headers

Both of them works, but we're only expecting the "linux-gke" package in CKCT gke.yaml.

We will need to decide how to fix this, from kernel-series.yaml or just add this package into gke.yaml.

(Also I assume the flavour will cause some blacklist issue)

[Sean Feole (sfeole)]

I just started looking at this yesterday as I found the issue early in the morning. I'll own this and get it resolved

[Sean Feole (sfeole)]

We have transitioned to incorporating the major version into the kernel names. This has been resolved and fixed for a while now