Skip to content

Mongo CE deployment hangs #15

@grtn316

Description

@grtn316

When deploying Mongo CE, sometimes it hangs indefinately due to the OCP API pods restarting (or something else).

See error:

customresourcedefinition.apiextensions.k8s.io/mongodbcommunity.mongodbcommunity.mongodb.com created
serviceaccount/mongodb-kubernetes-operator created
role.rbac.authorization.k8s.io/mongodb-kubernetes-operator created
rolebinding.rbac.authorization.k8s.io/mongodb-kubernetes-operator created
clusterrole.rbac.authorization.k8s.io/system:openshift:scc:anyuid added: "default"
clusterrole.rbac.authorization.k8s.io/system:openshift:scc:anyuid added: "mongodb-kubernetes-operator"
error: error when creating "config/manager/manager.yaml": Post "https://api.tempcluster.clustermaximo.com:6443/apis/apps/v1/namespaces/mongo/deployments?fieldManager=kubectl-create": dial tcp 10.0.0.5:6443: connect: connection refused
 - Waiting for MongoDB CE Operator  -Error from server (NotFound): deployments.apps "mongodb-kubernetes-operator" not found
^H/The connection to the server api.tempcluster.clustermaximo.com:6443 was refused - did you specify the right host or port?
^H|Error from server (NotFound): deployments.apps "mongodb-kubernetes-operator" not found
^H|Error from server (NotFound): deployments.apps "mongodb-kubernetes-operator" not found
^H\Error from server (NotFound): deployments.apps "mongodb-kubernetes-operator" not found
^H-Error from server (NotFound): deployments.apps "mongodb-kubernetes-operator" not found
^H/Error from server (NotFound): deployments.apps "mongodb-kubernetes-operator" not found
^H|Error from server (NotFound): deployments.apps "mongodb-kubernetes-operator" not found
^H\Error from server (NotFound): deployments.apps "mongodb-kubernetes-operator" not found

Is it possible to add a retry or check that these scripts are executing without error? Current error is here:

sed "s|{{MONGO_NAMESPACE}}|${MONGO_NAMESPACE}|g" config/manager/__manager__.yaml > config/manager/manager.yaml

However, I have seen it at different lines just depending on when one of the OCP API pods is restarted. We are taking this project as a dependancy for our automated deployments on azure found here: Maximo on Azure

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions