Bug 1903639
Summary: | Hostsubnet gatherer produces wrong output | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Tomas Remes <tremes> | |
Component: | Insights Operator | Assignee: | Tomas Remes <tremes> | |
Status: | CLOSED ERRATA | QA Contact: | Pavel Šimovec <psimovec> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 4.7 | CC: | aos-bugs, inecas, mklika, tremes | |
Target Milestone: | --- | |||
Target Release: | 4.7.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Cause: Wrong value was serialized to the hostsubnet json file.
Consequence: Content of Hostsubnets config files gathered by Insights Operators was same for all hostsubnets.
Fix: Serialize the correct value of hostsubnet.
Result: Hostsubnet config files are gathered correctly.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1904014 (view as bug list) | Environment: | ||
Last Closed: | 2021-02-24 15:37:21 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1904014 |
Description
Tomas Remes
2020-12-02 14:40:16 UTC
I tried it with with IO at commit e6758baf6cf6c908474b21612e2a0fdf40663143 Bug was there, all 4 hostsubnet files in IO archive did have same "name", "host",.. Then I have tried it with a fix from this PR, and the files looked as expected (commit 40fa35943dce163ecc5fcf44555971323cc8b172) And the hostsubnet io archive files looked fine I was using cluster version 4.6.1 Verified on 40fa35943dce163ecc5fcf44555971323cc8b172 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: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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-2020:5633 |