Details
-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.14
-
No
-
CNF Network Sprint 239
-
1
-
False
-
Description
Description of problem:
Trying to deploy the latest from staging repo fails :
(.venv) [kni@ocp-edge77 ocp-edge-auto_cluster]$ oc -n metallb-system get csv metallb-operator.v4.14.0-202307181355 NAME DISPLAY VERSION REPLACES PHASE metallb-operator.v4.14.0-202307181355 MetalLB Operator 4.14.0-202307181355 Failed (.venv) [kni@ocp-edge77 ocp-edge-auto_cluster]$ oc -n metallb-system describe csv metallb-operator.v4.14.0-202307181355 | tail -15 Message: Name: speaker Status: Present Version: v1 Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal RequirementsUnknown 21m operator-lifecycle-manager requirements not yet checked Normal RequirementsNotMet 21m (x2 over 21m) operator-lifecycle-manager one or more requirements couldn't be found Warning InstallCheckFailed 16m operator-lifecycle-manager install timeout Normal NeedsReinstall 16m operator-lifecycle-manager installing: waiting for deployment metallb-operator-controller-manager to become ready: deployment "metallb-operator-controller-manager" not available: Deployment does not have minimum availability. Normal AllRequirementsMet 16m (x2 over 21m) operator-lifecycle-manager all requirements found, attempting install Normal InstallSucceeded 16m (x2 over 21m) operator-lifecycle-manager waiting for install components to report healthy Normal InstallWaiting 16m (x2 over 21m) operator-lifecycle-manager installing: waiting for deployment metallb-operator-controller-manager to become ready: deployment "metallb-operator-controller-manager" not available: Deployment does not have minimum availability. Warning InstallCheckFailed 11m operator-lifecycle-manager install failed: deployment metallb-operator-controller-manager not ready before timeout: deployment "metallb-operator-controller-manager" exceeded its progress deadline
Version-Release number of selected component (if applicable):
metallb-operator.v4.14.0-202307181355 http://external-ci-coldstorage.datahub.redhat.com/cvp/cvp-redhat-operator-bundle-image-validation-test/ose-metallb-operator-bundle-container-v4.14.0.202307181355.p0.g0d9faad.assembly.stream-1/c3d3a9f3-681c-42ef-9f6a-278fd5ad8d7e/index_images.yml '[v4.14:registry-proxy.engineering.redhat.com/rh-osbs/iib:537756]' (.venv) [kni@ocp-edge77 ocp-edge-auto_cluster]$ oc version Client Version: 4.14.0-0.nightly-2023-07-19-141104 Kustomize Version: v5.0.1 Server Version: 4.14.0-0.nightly-2023-07-19-141104 Kubernetes Version: v1.27.3+4aaeaec
How reproducible:
Happans all the time
Steps to Reproduce:
0.reproduced by this jenkins job run: https://auto-jenkins-csb-kniqe.apps.ocp-c1.prod.psi.redhat.com/job/CI/job/vm-disconnected-ipv4_ctlplane-ipv6_provisioning-snr_nhc/346/ that is doing the folowing steps: 1.deploye an v4.14 openshift hub-cluster on BM with 3 master nodes. 2.bring up a catalog source named catalogsource.operators.coreos.com/redhat-operators-stage with registry-proxy.engineering.redhat.com/rh-osbs/iib:537756 entery 3. deploye metalld from redhat-operators-stage
Actual results:
The image is is installed but fail to bring up
Expected results:
metallb up and running
Additional info:
with V4.13 from the catalog our setup deployes fine