Description of problem: I have upgraded by OpenShift cluster to 3.3.0. I have upgraded the logging EFK stack. Upgrading the metrics stack fails. I am running [root@master ~]# oc new-app -f /usr/share/openshift/examples/infrastructure-templates/enterprise/metrics-deployer.yaml -p HAWKULAR_METRICS_HOSTNAME=metrics.xxxxx.xxx.xxxxxxxxx.xx,CASSANDRA_PV_SIZE=10Gi,METRIC_DURATION=800,MODE=refresh this ends up with the following message: 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 (leaving route and PVCs) POD_NAME metrics-deployer-hxetq The Pod "metrics-deployer-hxetq" 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): OCP 3.3 How reproducible: Always Steps to Reproduce: 1.Mentioned in the description 2. 3. Actual results: Expected results: Additional info:
This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1381336 The solution is to slightly change how your run the command so that is has consistent behaviour, and its actually a more correct way of doing it. The old documented way of doing things works in most situations, unless you happen to give your admin the anyuid permission, then you can run into problems. PR for doc update: https://github.com/openshift/openshift-docs/pull/3018 In essence, when you deploy metrics you need to run it as the deployer user. Eg: $ oc new-app --as=system:serviceaccount:openshift-infra:metrics-deployer \ -f metrics-deployer.yaml \ -p HAWKULAR_METRICS_HOSTNAME=hawkular-metrics.example.com *** This bug has been marked as a duplicate of bug 1381336 ***