Before start use the container after it is installed is a good practice check if all is ok first.
$ oc login -u system:admin -n default
- Check the pods of default project
$ oc get pods
NAME READY STATUS RESTARTS AGE
docker-registry-1-deploy 0/1 DeadlineExceeded 0 17m
docker-registry-2-deploy 0/1 ContainerCreating 0 16m
router-1-deploy 0/1 ContainerCreating 0 17m
If the READY column is shown that 0/1 is because the pod is not deployed. In this moment all pods of the default project should are deployed.
If the pod of default router is not deployed it means that the other pods are not deployed because the router is missing ( was not created ). The pods need this one to running with success.
- Check the description/status of the pod to try to find the error.
$ oc describe pod/router-1-deploy
Following the events returned in my case as an example.
7m 53s 6 {kubelet ip-10-0-0-107.ec2.internal} WarningFailedSync (events with common reason combined)
19m 0s 424 {kubelet ip-10-0-0-107.ec2.internal} WarningFailedSync Error syncing pod, skipping: failed to “SetupNetwork” for “router-1-deploy_default” with SetupNetworkError: “Failed to setup network for pod \”router-1-deploy_default(b43bdd83-0a59-11e7-bfa4-02acbbb94784)\” using network plugins \”redhat/openshift-ovs-subnet\”: Error running network setup script: + brctl delif lbr0\nIncorrect number of arguments for command\nUsage: brctl delif <bridge> <device>\tdelete interface from bridge\n; Skipping pod”
In this scenario has some error that is causing: “Error running network setup script: + brctl delif lbr0\nIncorrect number of arguments for command\n” when the router was been created.
1 Comment