1.24/beta MetalLB charms stay blocked: Error fetching image information
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MetalLB Operator |
Fix Released
|
Undecided
|
Adam Dyess |
Bug Description
Testing the latest/beta MetalLB charms with the bundle:
```
bundle: kubernetes
applications:
metallb-
charm: metallb-controller
channel: latest/beta
scale: 1
options:
iprange: "10.246.
metallb-speaker:
charm: metallb-speaker
scale: 1
channel: latest/beta
```
The charms get stuck
```
Model Controller Cloud/Region Version SLA Timestamp
metallb-maas foundations-maas microk8s_
App Version Status Scale Charm Channel Rev Address Exposed Message
metallb-controller blocked 1 metallb-controller beta 11 no Error fetching image information
metallb-speaker blocked 1 metallb-speaker beta 6 no Error fetching image information
Unit Workload Agent Address Ports Message
metallb-
metallb-speaker/0* blocked idle Error fetching image information
```
In the juju debug-log we see:
```
application-
Traceback (most recent call last):
File "/var/lib/
result = run(args, **kwargs)
File "/usr/lib/
raise CalledProcessEr
subprocess.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/var/lib/
resource_path = self.model.
File "/var/lib/
self.
File "/var/lib/
return self._run(
File "/var/lib/
raise ModelError(
ops.model.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "./src/charm.py", line 63, in _on_start
image_info = self.image.fetch()
File "/var/lib/
raise MissingResource
oci_image.
application-
application-
application-
application-
application-
application-
application-
application-
application-
application-
application-
application-
application-
application-
application-
Traceback (most recent call last):
File "/var/lib/
result = run(args, **kwargs)
File "/usr/lib/
raise CalledProcessEr
subprocess.
```
For comparison, when I deploy the bundle:
```
bundle: kubernetes
applications:
metallb-
charm: containers-
scale: 1
options:
iprange: "10.246.
metallb-speaker:
charm: containers-
scale: 1
```
The charms come up as expected:
```
Model Controller Cloud/Region Version SLA Timestamp
metallb-maas foundations-maas microk8s_
App Version Status Scale Charm Channel Rev Address Exposed Message
metallb-controller res:metallb-
metallb-speaker res:metallb-
Unit Workload Agent Address Ports Message
metallb-
metallb-speaker/0* active idle 10.246.165.200 7472/TC
```
Is there a configuration that I am missing for the new charms?
these charms (metallb-controller and metalb-speaker) have OCI images that should have been uploaded to charmhub during the build automation step but were missed. I've manually attached the OCI images to the following releases of those charms:
Revision 13 of charm 'metallb- controller' released to 1.24/stable (attaching resources: 'metallb- controller- image' r1) controller' released to latest/stable (attaching resources: 'metallb- controller- image' r1) controller' released to 1.24/beta (attaching resources: 'metallb- controller- image' r1) speaker- image' r1) speaker- image' r1) speaker- image' r1)
Revision 13 of charm 'metallb-
Revision 13 of charm 'metallb-
Revision 8 of charm 'metallb-speaker' released to 1.24/stable (attaching resources: 'metallb-
Revision 8 of charm 'metallb-speaker' released to 1.24/beta (attaching resources: 'metallb-
Revision 8 of charm 'metallb-speaker' released to latest/stable (attaching resources: 'metallb-
Subsequent deployments of these charms should pull the necessary images from charmhub.
Sorry for the inconvenience.