Bug 2011603
| Summary: | STF multi-cloud setup misinterprets name if a "-" is being used | ||
|---|---|---|---|
| Product: | Service Telemetry Framework | Reporter: | Chris Janiszewski <cjanisze> |
| Component: | service-telemetry-operator-container | Assignee: | Leif Madsen <lmadsen> |
| Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> |
| Severity: | high | Docs Contact: | Joanne O'Flynn <joflynn> |
| Priority: | high | ||
| Version: | 1.3 | CC: | augol, lmadsen, mmagr, mrunge |
| Target Milestone: | z3 | Keywords: | Triaged, ZStream |
| Target Release: | 1.3 (STF) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | service-telemetry-operator-container-1.3.7-1 | Doc Type: | Bug Fix |
| Doc Text: |
With this update, the servicetelemetrys.infra.watch CRD has a validation that limits the clouds[].name to 10 characters and alphanumeric to avoid issues with extra characters in the cloud name and names being too long.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-10 11:55:14 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: | |||
Solution: add a `pattern` regex to the `clouds.name` field to limit length and valid characters. Merged upstream. 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 (Moderate: Release of components for Service Telemetry Framework 1.3.3 - 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/RHSA-2021:4582 |
Description of problem: I have created a multi-cloud STF setup and named my second cloud as a "dcn-cloud" Even though the metrics seems to be flowing fine from overcloud to STF, the grafana has trimmed the name down to "cloud". We could either advise operators via docs to not use "-" or accommodate it in the regex Version-Release number of selected component (if applicable): STF 1.3.1632277596 OSP 16.2 How reproducible: everytime Steps to Reproduce: 1. Use a "-" for your cloud in multicloud STF setup 2. 3. Actual results: misinterpreted name Expected results: Additional info: clouds: - events: collectors: - collectorType: collectd subscriptionAddress: collectd/cloud1-notify - collectorType: ceilometer subscriptionAddress: anycast/ceilometer/cloud1-event.sample metrics: collectors: - collectorType: collectd subscriptionAddress: collectd/cloud1-telemetry - collectorType: sensubility subscriptionAddress: sensubility/cloud1-telemetry - collectorType: ceilometer subscriptionAddress: anycast/ceilometer/cloud1-metering.sample name: cloud1 - events: collectors: - collectorType: collectd subscriptionAddress: collectd/dcn-cloud-notify - collectorType: ceilometer subscriptionAddress: anycast/ceilometer/dcn-cloud-event.sample metrics: collectors: - collectorType: collectd subscriptionAddress: collectd/dcn-cloud-telemetry - collectorType: sensubility subscriptionAddress: sensubility/dcn-cloud-telemetry - collectorType: ceilometer subscriptionAddress: anycast/ceilometer/dcn-cloud-metering.sample name: dcn-cloud