Bug 1670676 - Deployment config does not have minimum availability.
Summary: Deployment config does not have minimum availability.
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: openshift-controller-manager
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.1.0
Assignee: Tomáš Nožička
QA Contact: zhou ying
URL:
Whiteboard:
Depends On:
Blocks: 1664187
TreeView+ depends on / blocked
 
Reported: 2019-01-30 07:12 UTC by Jaspreet Kaur
Modified: 2023-09-14 04:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-14 09:14:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jaspreet Kaur 2019-01-30 07:12:39 UTC
Description of problem: Created a demo application from webconsole using quickstarts and it just shows one messages as below :

Deployment config does not have minimum availability.

kind: DeploymentConfig
apiVersion: apps.openshift.io/v1
metadata:
  name: newapp
  namespace: mytest
  selfLink: /apis/apps.openshift.io/v1/namespaces/mytest/deploymentconfigs/newapp
  uid: 96596e24-245d-11e9-b360-0a580a81006e
  resourceVersion: '1830234'
  generation: 1
  creationTimestamp: '2019-01-30T07:06:38Z'
  labels:
    app: newapp
spec:
  strategy:
    type: Rolling
    rollingParams:
      updatePeriodSeconds: 1
      intervalSeconds: 1
      timeoutSeconds: 600
      maxUnavailable: 25%
      maxSurge: 25%
    resources: {}
    activeDeadlineSeconds: 21600
  triggers:
    - type: ImageChange
      imageChangeParams:
        automatic: true
        containerNames:
          - newapp
        from:
          kind: ImageStreamTag
          namespace: mytest
          name: 'newapp:latest'
    - type: ConfigChange
  replicas: 1
  revisionHistoryLimit: 10
  test: false
  selector:
    app: newapp
    deploymentconfig: newapp
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: newapp
        deploymentconfig: newapp
    spec:
      containers:
        - name: newapp
          image: 'newapp:latest'
          ports:
            - containerPort: 8080
              protocol: TCP
            - containerPort: 8443
              protocol: TCP
          resources: {}
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
          imagePullPolicy: Always
      restartPolicy: Always
      terminationGracePeriodSeconds: 30
      dnsPolicy: ClusterFirst
      securityContext: {}
      schedulerName: default-scheduler
status:
  latestVersion: 0
  observedGeneration: 1
  replicas: 0
  updatedReplicas: 0
  availableReplicas: 0
  unavailableReplicas: 0
  conditions:
    - type: Available
      status: 'False'
      lastUpdateTime: '2019-01-30T07:06:38Z'
      lastTransitionTime: '2019-01-30T07:06:38Z'
      message: Deployment config does not have minimum availability.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results: Deployment doesnt suceeds


Expected results: Quickstarts should have worked


Additional info:

Comment 3 Red Hat Bugzilla 2023-09-14 04:45:55 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.