Bug 1848408

Summary:	DeploymentConfig is rejected by client-side validation
Product:	OpenShift Container Platform	Reporter:	Stefan Schimanski <sttts>
Component:	oc	Assignee:	Nobody <nobody>
oc sub component:	oc	QA Contact:	zhou ying <yinzhou>
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	medium
Priority:	medium	CC:	annelson, aos-bugs, juzhao, mfojtik
Version:	4.6
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-12-12 12:15:23 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:

Description Stefan Schimanski 2020-06-18 10:30:44 UTC

Description of problem:

Use kubectl with client validation enabled (tried 1.18.3 kubectl from upstream). Then

  kubectl create -f
https://raw.githubusercontent.com/sttts/sttts-bot/master/manifests/sttts-bot-deploymentconfig.yaml

error: error validating "sttts-bot-deploymentconfig.yaml": error validating data: ValidationError(DeploymentConfig.spec.template.spec.containers[0].env[6].valueFrom.fieldRef): unknown field "name" in io.k8s.api.core.v1.ObjectFieldSelector; if you choose to ignore these errors, turn validation off with --validate=false

The server accepts the file using oc.

Comment 2 Maciej Szulik 2020-07-09 11:08:03 UTC

I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.

Comment 3 Maciej Szulik 2020-08-11 10:25:28 UTC

*** Bug 1844957 has been marked as a duplicate of this bug. ***

Comment 4 Maciej Szulik 2020-08-21 14:10:03 UTC

I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.

Comment 5 Michal Fojtik 2020-09-10 10:37:52 UTC

This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.

Comment 6 Maciej Szulik 2020-09-10 13:19:15 UTC

I don't we'll be able to tackle this for 4.6, moving to 4.7.

Comment 7 Maciej Szulik 2020-10-01 14:48:53 UTC

I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.

Comment 8 Michal Fojtik 2020-10-10 13:20:58 UTC

This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.

Comment 9 Maciej Szulik 2020-10-12 09:42:50 UTC

It's still an important topic for us we want to pursue.

Comment 10 Maciej Szulik 2020-10-23 10:37:05 UTC

I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.

Comment 11 Michal Fojtik 2020-11-11 10:12:06 UTC

This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.

Comment 12 Maciej Szulik 2020-11-12 12:10:08 UTC

I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.

Comment 13 Maciej Szulik 2020-12-04 16:27:10 UTC

This is being actively worked on.

Comment 14 Michal Fojtik 2021-01-03 16:58:21 UTC

This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.

Comment 15 Michal Fojtik 2021-01-21 12:20:30 UTC

The LifecycleStale keyword was removed because the needinfo? flag was reset.
The bug assignee was notified.

Comment 16 Maciej Szulik 2021-02-05 14:11:15 UTC

It's still in-progress pushing over to 4.8.

Comment 17 Maciej Szulik 2021-02-25 18:36:19 UTC

I'll be revisiting in the next few weeks.

Comment 18 Michal Fojtik 2021-03-27 18:50:50 UTC

This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.

Comment 20 Maciej Szulik 2021-05-21 17:47:02 UTC

There are still API changes needed to make this over the hump :-( this won't make 4.8

Comment 22 Maciej Szulik 2022-12-12 12:15:23 UTC

Given the sig-cli and sig-apimachinery direction towards making validation optional, and the switch to openapi v3 I'm closing this as won't fix.