Bug 1811636 - [buildcop] oc adm must-gather runs successfully test fails
Summary: [buildcop] oc adm must-gather runs successfully test fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: openshift-apiserver
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
urgent
Target Milestone: ---
: 4.4.0
Assignee: Stefan Schimanski
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On: 1808568
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-09 12:00 UTC by Stefan Schimanski
Modified: 2020-05-13 22:01 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1808568
Environment:
Last Closed: 2020-05-13 22:00:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-openshift-apiserver-operator pull 332 0 None closed [release-4.4] Bug 1811636: Fix rollout strategy to never run more than one pod per node 2020-07-08 14:48:37 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-13 22:00:59 UTC

Comment 3 Xingxing Xia 2020-04-17 11:29:56 UTC 
Checked the issue code a while, especially the PR comment and the YAML comment that explain the issue and fix purpose. Checked bug 1808568#c2 saying Not actionable for QE. Though, BTW checked 4.4.0-0.nightly-2020-04-17-044622:
$ oc get deployment apiserver -n openshift-apiserver -o yaml
...
  strategy:
    rollingUpdate:
      maxSurge: 0
      maxUnavailable: 1
    type: RollingUpdate
...
      affinity:
        podAntiAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
          - labelSelector:
              matchLabels:
                apiserver: "true"
                app: openshift-apiserver-a
            topologyKey: kubernetes.io/hostname

Its deployment strategy and scheduling setting as as the PR. Moving to VERIFIED.
Comment 5 errata-xmlrpc 2020-05-13 22:00:58 UTC 
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/RHBA-2020:0581
Note You need to log in before you can comment on or make changes to this bug.