Bug 1953563 - Control plane components don't declare build-root-image in repo
Summary: Control plane components don't declare build-root-image in repo
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.10.0
Assignee: Stefan Schimanski
QA Contact: Ke Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-26 11:56 UTC by Stefan Schimanski
Modified: 2023-01-16 11:29 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-16 11:29:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-authentication-operator pull 439 0 None open Bug 1953563: Add .ci-operator.yaml with build_root_image 2021-05-11 11:13:25 UTC
Github openshift cluster-bootstrap pull 60 0 None open Bug 1953563: Add .ci-operator.yaml with build_root_image 2021-05-11 11:51:12 UTC
Github openshift cluster-config-operator pull 198 0 None open Bug 1953563: Add .ci-operator.yaml with build_root_image 2021-05-11 11:15:48 UTC
Github openshift cluster-etcd-operator pull 574 0 None open Bug 1953563: Add .ci-operator.yaml with build_root_image 2021-04-26 14:27:03 UTC
Github openshift cluster-kube-apiserver-operator pull 1116 0 None open Bug 1953563: Add .ci-operator.yaml with build_root_image 2021-04-26 11:58:38 UTC
Github openshift cluster-kube-controller-manager-operator pull 523 0 None open Bug 1953563: Makefile: add verify-golang-versions 2021-04-26 11:58:47 UTC
Github openshift cluster-kube-scheduler-operator pull 349 0 None open Bug 1953563: Add .ci-operator.yaml with build_root_image 2021-05-11 11:15:43 UTC
Github openshift cluster-openshift-apiserver-operator pull 448 0 None open Bug 1953563: Add .ci-operator.yaml with build_root_image 2021-05-11 11:15:36 UTC
Github openshift cluster-openshift-apiserver-operator pull 452 0 None open Bug 1953563: Add .ci-operator.yaml with build_root_image 2021-05-12 14:56:27 UTC
Github openshift must-gather pull 228 0 None open Bug 1953563: Switch build root to golang 1.15 2021-05-11 11:13:35 UTC
Github openshift must-gather pull 232 0 None open Bug 1953563: Add .ci-operator.yaml with build_root_image 2021-05-11 11:13:29 UTC
Github openshift oauth-apiserver pull 51 0 None open Bug 1953563: Add .ci-operator.yaml with build_root_image 2021-04-26 11:57:35 UTC
Github openshift oauth-server pull 76 0 None open Bug 1953563: Add .ci-operator.yaml with build_root_image 2021-05-11 11:16:10 UTC
Github openshift oc pull 814 0 None open Bug 1953563: Makefile: add verify-golang-versions 2021-05-11 11:16:02 UTC
Github openshift openshift-apiserver pull 203 0 None open Bug 1953563: Add .ci-operator.yaml with build_root_image 2021-04-26 11:57:14 UTC
Github openshift release pull 18021 0 None open Bug 1953563: oauth-server/auth-operator: get build_root_image from repo 2021-05-11 11:14:00 UTC
Github openshift service-ca-operator pull 158 0 None open Bug 1953563: Add .ci-operator.yaml with build_root_image 2021-05-11 11:14:40 UTC

Description Stefan Schimanski 2021-04-26 11:56:33 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Ke Wang 2021-05-08 02:42:25 UTC
Talked to sttts in Slack, confirmed with him that the bug has plenty of PRs missing and shouldn't be ON_QA yet, so assign the bug back.

Comment 7 Michal Fojtik 2023-01-16 11:29:46 UTC
Dear reporter, we greatly appreciate the bug you have reported here. Unfortunately, due to migration to a new issue-tracking system (https://issues.redhat.com/), we cannot continue triaging bugs reported in Bugzilla. Since this bug has been stale for multiple days, we, therefore, decided to close this bug.

If you think this is a mistake or this bug has a higher priority or severity as set today, please feel free to reopen this bug and tell us why. We are going to move every re-opened bug to https://issues.redhat.com. 

Thank you for your patience and understanding.


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