Description of problem: Setting alerting.storage.persistent.storageResources has no effect. Version-Release number of selected component (if applicable): STF-1.1 How reproducible: Always Steps to Reproduce: 1. Set alerting.alertmanager.storage.persistent.storageResources in your STF manifest Actual results: Nothing you set appears as part of the resulting alertmanager manifest Expected results: I expected these to become part of the storage definition in the alertmanager manifest as shown here: https://github.com/infrawatch/service-telemetry-operator/blob/f84753a2a70ff1cc8d5ad888654f253f4f7c6c92/roles/servicetelemetry/templates/manifest_alertmanager.j2#L17 Additional info: * This parameter, along with the selector and class are in the wrong part of the manifest. Resources belongs under volumeClaimTemplate.spec * However, the storageSize is the only resource we can manage this way, and it is already accounted for with this pvc_storage_request parameter * Therefore this parameter is useless and can be removed (it never worked, so won't cause any regression) This problem is already fixed upstream, this BZ exists to track the resulting CRD change during the release process.
Getting flags aligned. Target is STF 1.2 as the fix is merged upstream and will be imported into stable-1.2 when that branch is created. Will move to MODIFIED once we have a service-telemetry-operator-container image built downstream.
Moved back to ON_DEV due to issue in https://bugzilla.redhat.com/show_bug.cgi?id=1918781. Will require a re-spin.
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 (Release of components for Service Telemetry Framework 1.2 - Operator Container), 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/RHEA-2021:0649