Bug 1382783

Summary: Metrics redeploy fails with "spec: Forbidden: pod updates may not change fields"
Product: OpenShift Container Platform Reporter: Mike Fiedler <mifiedle>
Component: HawkularAssignee: Matt Wringe <mwringe>
Status: CLOSED DUPLICATE QA Contact: Peng Li <penli>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.3.1CC: aos-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-07 18:18:54 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:
Attachments:
Description Flags
Deployer yaml
none
Deployer log none

Description Mike Fiedler 2016-10-07 17:46:33 UTC
Created attachment 1208205 [details]
Deployer yaml

Description of problem:

Tried to run the metrics deployer with MODE=redeploy and it failed with the following messages (full log attached):

PREFLIGHT CHECK SUCCEEDED
validate_master_accessible: ok
validate_hostname: The HAWKULAR_METRICS_HOSTNAME value is deemed acceptable.
validate_deployer_secret: ok
Deleting any previous deployment
POD_NAME metrics-deployer-yoscr
The Pod "metrics-deployer-yoscr" is invalid.
spec: Forbidden: pod updates may not change fields other than `containers[*].image` or `spec.activeDeadlineSeconds`



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


How reproducible: always on the cluster I hit it on.  Not sure about other clusters.


Steps to Reproduce:
1. I ran the metrics deployer but hit an issue where the heapster pod was Running but did not go to ready - it was having an issue talking to the Hawkular pod using the internal DNS service name.
2. Decided to try redeploying.   Instead of a manual cleanup, decided to try the redeploy.   Ran the deployer with the exact same parameters as on deploy, but specified MODE=redeploy (deployer yaml attached).


Actual results:

Redeploy failed with the messages above

Expected results:

Redeploy succeeds (or at least gets me back to where I was)

Comment 1 Mike Fiedler 2016-10-07 17:47:01 UTC
Created attachment 1208206 [details]
Deployer log

Comment 2 Matt Wringe 2016-10-07 18:18:54 UTC

*** This bug has been marked as a duplicate of bug 1381336 ***