Bug 1772948 - Control plane upgrade playbook removes etcd secret mount from prometheus-k8s statefulset
Summary: Control plane upgrade playbook removes etcd secret mount from prometheus-k8s ...
Keywords:
Status: CLOSED DUPLICATE of bug 1703032
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.11.z
Assignee: Simon Pasquier
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-15 16:40 UTC by Nicolas Nosenzo
Modified: 2023-09-07 21:00 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-18 11:00:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


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