-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.11, 4.9
-
None
-
False
-
Description of problem:
Installation of zabbix-agent from operator in marketplace fails with message: Image registry.connect.redhat.com/zabbix/zabbix-agent-50@sha256:229562a27ed45319ef17397fe81cac81129c84eccd2c14f6085531a86ef9b87d not found
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. From OCP web console, go to Operators > OperatorHub 2. Search "Zabbix" 3. Install Zabbix Operator from Certified channel 4. go to Operators > Installed Operators > Zabbix Operator > Zabbix Agent and create a new Zabbix Agent instance
Actual results:
Installation fails. Pods in ImagePullBackOff state
Expected results:
Pods in Running state
Additional info:
I think the problem is that this manifest doesn't exist (anymore): ~~~ $ skopeo inspect docker://registry.connect.redhat.com/zabbix/zabbix-agent-50@sha256:229562a27ed45319ef17397fe81cac81129c84eccd2c14f6085531a86ef9b87d FATA[0001] Error parsing image name "docker://registry.connect.redhat.com/zabbix/zabbix-agent-50@sha256:229562a27ed45319ef17397fe81cac81129c84eccd2c14f6085531a86ef9b87d": Error reading manifest sha256:229562a27ed45319ef17397fe81cac81129c84eccd2c14f6085531a86ef9b87d in registry.connect.redhat.com/zabbix/zabbix-agent-50: name unknown: Image not found ~~~ I found the problem in OCP 4.9 and 4.11, so I tend to believe that the problem is not on index images but rather in the fact that the image was probably removed from the registry for some reason