Bug 1639739
| Summary: | OpenShift Cluster monitoring Operator needs option to specify storageclass | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Wolfgang Kulhanek <wkulhane> |
| Component: | Monitoring | Assignee: | Frederic Branczyk <fbranczy> |
| Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.11.0 | CC: | aos-bugs, dapark, jokerman, juzhao, minden, mmccomas, sponnaga, vigoyal |
| 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-04-11 05:38:23 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: | |||
There is already a pull request out to fix this: https://github.com/openshift/openshift-ansible/pull/10387 This is an entirely new stack, it has nothing to do with the old tech preview stack. This has now been merged into master and the 3.11 release. Issue is fixed. openshift_cluster_monitoring_operator_prometheus_storage_class_name and openshift_cluster_monitoring_operator_alertmanager_storage_class_name are added. # rpm -qa | grep ansible openshift-ansible-playbooks-3.11.31-1.git.0.d4b5614.el7.noarch openshift-ansible-docs-3.11.31-1.git.0.d4b5614.el7.noarch openshift-ansible-roles-3.11.31-1.git.0.d4b5614.el7.noarch openshift-ansible-3.11.31-1.git.0.d4b5614.el7.noarch ansible-2.6.6-1.el7ae.noarch please change to ON_QA I've opened the PR about the related documentation here : https://github.com/openshift/openshift-docs/pull/13001 Setting to modified as the PR was merged. As per Comment 3, openshift_cluster_monitoring_operator_prometheus_storage_class_name and openshift_cluster_monitoring_operator_alertmanager_storage_class_name are added The 3.11 doc is updated, no issue Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0636 |
Description of problem: In 3.11.16 there is no option to define the storage class for the Monitoring Operator (prometheus) storage. The only options available (that I could find by looking through the playbooks, forget the docs...) are: openshift_cluster_monitoring_operator_install=True openshift_cluster_monitoring_operator_node_selector={"node-role.kubernetes.io/infra":"true"} openshift_cluster_monitoring_operator_prometheus_storage_capacity=20Gi openshift_cluster_monitoring_operator_alertmanager_storage_capacity=2Gi openshift_cluster_monitoring_operator_prometheus_storage_enabled=True openshift_cluster_monitoring_operator_alertmanager_storage_enabled=True With OCS this will create PVs of type gluster-fs rather than the required glusterfs-block. In 3.10 there were options: openshift_prometheus_storage_class='glusterfs-storage-block' openshift_prometheus_alertmanager_storage_class='glusterfs-storage-block' openshift_prometheus_alertbuffer_storage_volume_name=prometheus-alertbuffer Why do we keep losing foundational settings??