metallb-speaker pod logs error "selfLink was empty, can't make reference"

[George Kraft]

Originally reported here: https://bugs.launchpad.net/operator-metallb/+bug/1919479

Upstream issue: https://github.com/metallb/metallb/issues/794

This should be fixed in MetalLB 0.9.6, whenever that is released. The charms will need to be updated to use that version when it comes out.

Reproduction steps:
1. Deploy Charmed Kubernetes on MAAS.
2. Deploy the metallb-operator to a k8s model.
3. Create a Service with type=LoadBalancer.
4. Check the metallb-speaker pod logs for the error.

[Bas de Bruijne (basdbruijne)]

We are seeing this in the microk8s release testing too. MetalLB 0.9.6 is released by now, did the fix for this get picked up in the metallb charms?

[George Kraft (cynerva)]

Oops. Not at the time you posted the comment, no. But now, yes, when you deploy MetalLB charms from the 1.26/beta channel, you should get MetalLB 0.12.

A PR[1] to metallb-operator updated the charm resource metadata to reference MetalLB 0.12 images. However, our CI did not do anything with the updated metadata, so the 1.26/beta charms were erroneously pushed with the old images. For now, we have manually attached the correct images. We will look into fixing this in our CI so image updates like this don't get missed again.

[1]: https://github.com/charmed-kubernetes/metallb-operator/pull/27