View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0015756 | Buildsys | Ci.centos.org Ecosystem Testing | public | 2019-01-28 16:46 | 2019-02-07 22:09 |
Reporter | lmilbaum | ||||
Priority | normal | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Summary | 0015756: ReplicaSet doesn't scale up | ||||
Description | I have a Deployment object with 1 desired replica configured. ReplicaSet generated automatically with 0 desired replicas, with no option to change it. Here is the link: https://console.apps.ci.centos.org:8443/console/project/ember-csi-stage/browse/rs/ci-stage-master-1495213486 | ||||
Tags | No tags attached. | ||||
Where is the DeploymentConfig for this? are you tracking that in git somewhere? | |
Is a DeploymentConfig required when I use a Deployment? BTW, the same automation works on another OpenShift Cluster (version 3.9). |
|
I don't think they're strictly necessary, but I was hoping to take a look at whichever configs you have to compare with what got realized in the cluster. | |
Following a deep troubleshooting, the issue with the deployment.spec.strategy which was set to 'Recreate'. Did you see any errors in the kubernetes logs which can indicate this? |
|
There isn't anything in the logs that would point toward trouble one way or another. I see that the replicaset has fulfilled, so I'm going to close this. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2019-01-28 16:46 | lmilbaum | New Issue | |
2019-01-29 15:40 | bstinson | Note Added: 0033722 | |
2019-01-30 00:23 | lmilbaum | Note Added: 0033727 | |
2019-01-30 09:17 | bstinson | Note Added: 0033732 | |
2019-02-04 14:46 | lmilbaum | Note Added: 0033772 | |
2019-02-07 22:09 | bstinson | Status | new => resolved |
2019-02-07 22:09 | bstinson | Resolution | open => fixed |
2019-02-07 22:09 | bstinson | Note Added: 0033788 |