Previously, there was an invalid configuration in the example Custom Resource and the x-descriptor of the ClusterServiceVersion resource.
Installation of a ServiceTelemetry manifest from the OpenShift UI resulted in an invalid CustomResource manifest, which could cause issues upgrading to STF 1.4.
In this update, the CustomResource example and the ClusterServiceVersion x-descriptors for the alertmanager parameters were fixed.
Now, when you deploy STF 1.3 with a default UI configuration, STF successfully upgrades from 1.3 to 1.4.
Description of problem: The example CR for alertmanager receivers is improperly indented which results in the fields not populating correctly in the OCP UI x-descriptors. Additionally, the UI x-descriptors for the webhook snmptrap target is referring to the incorrect field, also resulting in the wrong value populating.
This can potentially cause issues with upgrades to STF 1.4 due to the resulting CR being invalid for the CRD in STF 1.4, which will cause the Service Telemetry Operator CSV to fail the InstallPlan and sit in the Pending state indefinitely.
Version-Release number of selected component (if applicable): STF 1.3.3
How reproducible: If the UI is used and the alertmanager webhook SNMPtrap feature is enabled, the resulting CR will be invalid for upgrades.
Steps to Reproduce:
1. load the OCP UI and create a ServiceTelemetry object
2. leave all defaults, but enable SNMPtrap delivery and populate the target field with an IP address
Actual results: The CR will populate like so:
...
spec:
alerting:
alertmanager:
receivers:
snmpTraps:
enabled: 10.10.10.10
storage:
persistent:
pvcStorageRequest: 20G
storageClass: standard
storageSelector: {}
receivers:
snmpTraps:
enabled: false
target: 192.168.24.254
strategy: persistent
enabled: true
...
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.3.4 - Container Images), 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-2022:0586
Description of problem: The example CR for alertmanager receivers is improperly indented which results in the fields not populating correctly in the OCP UI x-descriptors. Additionally, the UI x-descriptors for the webhook snmptrap target is referring to the incorrect field, also resulting in the wrong value populating. This can potentially cause issues with upgrades to STF 1.4 due to the resulting CR being invalid for the CRD in STF 1.4, which will cause the Service Telemetry Operator CSV to fail the InstallPlan and sit in the Pending state indefinitely. Version-Release number of selected component (if applicable): STF 1.3.3 How reproducible: If the UI is used and the alertmanager webhook SNMPtrap feature is enabled, the resulting CR will be invalid for upgrades. Steps to Reproduce: 1. load the OCP UI and create a ServiceTelemetry object 2. leave all defaults, but enable SNMPtrap delivery and populate the target field with an IP address Actual results: The CR will populate like so: ... spec: alerting: alertmanager: receivers: snmpTraps: enabled: 10.10.10.10 storage: persistent: pvcStorageRequest: 20G storageClass: standard storageSelector: {} receivers: snmpTraps: enabled: false target: 192.168.24.254 strategy: persistent enabled: true ...