Bug 1772948

Summary: Control plane upgrade playbook removes etcd secret mount from prometheus-k8s statefulset
Product: OpenShift Container Platform Reporter: Nicolas Nosenzo <nnosenzo>
Component: MonitoringAssignee: Simon Pasquier <spasquie>
Status: CLOSED DUPLICATE QA Contact: Junqi Zhao <juzhao>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: alegrand, anpicker, erooth, kakkoyun, lcosic, mloibl, pkrupa, spasquie, surbania
Target Milestone: ---   
Target Release: 3.11.z   
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: 2019-11-18 11:00:56 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 Nicolas Nosenzo 2019-11-15 16:40:04 UTC
Description of problem:
upgrade_control_plane.yml removes secret-kube-etcd-client-certs volume from statefulset/prometheus-k8s.

Version-Release number of the following components:
openshift-ansible-3.11.153-2

How reproducible:
100%

Steps to Reproduce:
1. Configure etcd endpoint monitoring (https://docs.openshift.com/container-platform/3.11/install_config/prometheus_cluster_monitoring.html#configuring-etcd-monitoring_prometheus-cluster-monitoring)
2. Run upgrade_control_plane.yml playbook

Actual results:
Etcd volume entry is removed from the statefulset/prometheus-k8s manifest:

$ oc set volume statefulset prometheus-k8s | grep etcd
$

Expected results:
After upgrade playbook completion, etcd secret volume should be kept:

$ oc set volume statefulset prometheus-k8s | grep etcd
  secret/kube-etcd-client-certs as secret-kube-etcd-client-certs
    mounted at /etc/prometheus/secrets/kube-etcd-client-certs in container prometheus


Additional info:

Comment 1 Russell Teague 2019-11-15 17:03:43 UTC
Moving to the monitoring team for monitoring upgrade investigation.

Comment 4 Simon Pasquier 2019-11-18 11:00:56 UTC

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

Comment 5 Simon Pasquier 2019-11-18 11:23:47 UTC

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