500 Internal Server Error when updating MetalLB IPAddressPool

Bug #2060819 reported by Jeffrey Chang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MetalLB Operator
New
Undecided
Unassigned

Bug Description

In SolQA deployment - https://solutions.qa.canonical.com/testruns/7d453465-200d-496c-8178-81a8267c9bf7
with juju 3.1.8 candidate, deploy mk8s on MAAS cloud, and then metallb.
metallb unit stuck in waiting.

We see errors from pods log
2024-04-09T23:27:58.602628123Z stdout F 2024-04-09T23:27:58.602Z [container-agent] 2024-04-09 23:27:58 INFO juju-log Updating MetalLB IPAddressPool to reflect charm configuration
2024-04-09T23:27:58.688986251Z stdout F 2024-04-09T23:27:58.688Z [container-agent] 2024-04-09 23:27:58 INFO juju-log HTTP Request: PATCH https://10.152.183.1/apis/metallb.io/v1beta1/namespaces/metallb-system/ipaddresspools/juju-system-microk8s-metallb?force=true&fieldManager=metallb "HTTP/1.1 500 Internal Server Error"
2024-04-09T23:28:00.048052799Z stderr F 2024-04-09T23:28:00.047Z [pebble] Check "readiness" failure 1 (threshold 3): received non-20x status code 418
2024-04-09T23:28:00.787491149Z stdout F 2024-04-09T23:28:00.787Z [container-agent] 2024-04-09 23:28:00 INFO juju-log HTTP Request: PATCH https://10.152.183.1/apis/metallb.io/v1beta1/namespaces/metallb-system/ipaddresspools/juju-system-microk8s-metallb?force=true&fieldManager=metallb "HTTP/1.1 500 Internal Server Error"
2024-04-09T23:28:02.827366646Z stdout F 2024-04-09T23:28:02.827Z [container-agent] 2024-04-09 23:28:02 INFO juju-log HTTP Request: PATCH https://10.152.183.1/apis/metallb.io/v1beta1/namespaces/metallb-system/ipaddresspools/juju-system-microk8s-metallb?force=true&fieldManager=metallb "HTTP/1.1 500 Internal Server Error"
2024-04-09T23:28:06.9128421Z stdout F 2024-04-09T23:28:06.912Z [container-agent] 2024-04-09 23:28:06 INFO juju-log HTTP Request: PATCH https://10.152.183.1/apis/metallb.io/v1beta1/namespaces/metallb-system/ipaddresspools/juju-system-microk8s-metallb?force=true&fieldManager=metallb "HTTP/1.1 500 Internal Server Error"
2024-04-09T23:28:10.047780077Z stderr F 2024-04-09T23:28:10.047Z [pebble] Check "readiness" failure 2 (threshold 3): received non-20x status code 418

2024-04-09T23:28:15.182761591Z stdout F 2024-04-09T23:28:15.182Z [container-agent] 2024-04-09 23:28:15 INFO juju-log HTTP Request: PATCH https://10.152.183.1/apis/metallb.io/v1beta1/namespaces/metallb-system/ipaddresspools/juju-system-microk8s-metallb?force=true&fieldManager=metallb "HTTP/1.1 500 Internal Server Error"
2024-04-09T23:28:20.048023315Z stderr F 2024-04-09T23:28:20.047Z [pebble] Check "readiness" failure 3 (threshold 3): received non-20x status code 418
2024-04-09T23:28:20.048037115Z stderr F 2024-04-09T23:28:20.047Z [pebble] Check "readiness" failure threshold 3 hit, triggering action
2024-04-09T23:28:30.04548424Z stderr F 2024-04-09T23:28:30.045Z [pebble] Check "readiness" failure 4 (threshold 3): received non-20x status code 418

More artifacts could be found from https://oil-jenkins.canonical.com/artifacts/7d453465-200d-496c-8178-81a8267c9bf7/index.html

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.