Bug 1313158
| Summary: | Only the first deployment of router could be successful | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Gaoyun Pei <gpei> |
| Component: | openshift-controller-manager | Assignee: | Michail Kargakis <mkargaki> |
| Status: | CLOSED ERRATA | QA Contact: | Gaoyun Pei <gpei> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.2.0 | CC: | anli, aos-bugs, tdawson |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-12 16:30:48 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
QE will verify this bug once related PR https://github.com/openshift/origin/pull/7796 merged into ose. Thanks! Should be in v3.2.0.1 built today. Verify this with openshift v3.2.0.1 Deploy router for more times, the deployer is working well, new router pod would be created successfully. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2016:1064 |
Description of problem: In an ose-3.2 env, router service is created during installation, when try to deploy router again, the second attempt is failing with error message: I0229 22:07:59.524961 1 deployer.go:201] Deploying from default/router-1 to default/router-3 (replicas: 1) I0229 22:08:00.634903 1 rolling.go:228] RollingUpdater: Continuing update with existing controller router-3. F0229 22:08:00.634955 1 deployer.go:69] one of maxSurge or maxUnavailable must be specified Version-Release number of selected component (if applicable): openshift v3.1.1.908 kubernetes v1.2.0-alpha.7-703-gbc4550d etcd 2.2.5 How reproducible: Always Steps to Reproduce: 1.[root@openshift-137 ~]# oc get pod NAME READY STATUS RESTARTS AGE router-1-f2d9z 1/1 Running 0 3m [root@openshift-137 ~]# oc get dc router -o yaml ... spec: replicas: 1 selector: router: router strategy: resources: {} rollingParams: intervalSeconds: 1 maxSurge: 0 maxUnavailable: 25% timeoutSeconds: 600 updatePercent: -25 updatePeriodSeconds: 1 type: Rolling ... 2. [root@openshift-137 ~]# oc deploy router --latest Started deployment #2 [root@openshift-137 ~]# oc get pod NAME READY STATUS RESTARTS AGE router-1-f2d9z 1/1 Running 0 6m router-2-deploy 0/1 Error 0 10s [root@openshift-137 ~]# oc logs router-2-deploy I0229 21:59:01.994987 1 deployer.go:201] Deploying from default/router-1 to default/router-2 (replicas: 1) I0229 21:59:03.100406 1 rolling.go:228] RollingUpdater: Continuing update with existing controller router-2. F0229 21:59:03.138800 1 deployer.go:69] one of maxSurge or maxUnavailable must be specified [root@openshift-137 ~]# oc get rc CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS AGE router-1 router registry.x.x.com/openshift3/ose-haproxy-router:v3.1.1.908 deployment=router-1,deploymentconfig=router,router=router 1 14m router-2 router registry.x.x.com/openshift3/ose-haproxy-router:v3.1.1.908 deployment=router-2,deploymentconfig=router,router=router 0 1m Actual results: Expected results: The redeployment should be successful Additional info: