Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1364030 - When use `oc annotate` to update the immutalbe field should give some failed info
Summary: When use `oc annotate` to update the immutalbe field should give some failed ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Pod
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: dhodovsk
QA Contact: DeShuai Ma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-04 10:30 UTC by DeShuai Ma
Modified: 2016-08-09 16:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-09 16:46:02 UTC


Attachments (Terms of Use)

Description DeShuai Ma 2016-08-04 10:30:15 UTC
Description of problem:
When use `oc annotate` to update the pod annotations which is immutalbe, the command return annotated

Version-Release number of selected component (if applicable):
openshift v3.3.0.14
kubernetes v1.3.0+57fb9ac
etcd 2.3.0+git

oc v3.3.0.14

How reproducible:
Always

Steps to Reproduce:
1.Create a pod when the pod is running, update the annotations
# oc annotate --overwrite pods hello-pod openshift.io/scc='jfjjf'

Actual results:
1. return pod 'annotated'
[root@dhcp-128-7 dma]# oc annotate --overwrite pods hello-pod openshift.io/scc='jfjjf'
pod "hello-pod" annotated

Expected results:
1. return the field is immutable

Additional info:

Comment 1 Andy Goldstein 2016-08-09 16:46:02 UTC
The annotation on the pod is informative, not authoritative. While there is no real reason for a user to change that value, they are free to do so, and it won't affect the pod's SCC in any way.


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