Loading...

XML

Word

Printable

Type: Bug
Resolution: Unresolved
Priority: Normal
Fix Version/s: None
Affects Version/s: 4.16.z
Component/s: Insights Operator
Labels:
- obsint-io
- obsint-quality

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
None
Regression:
None

Target Backport Versions:
None
Target Version:
None
Release Blocker:
None
Sprint:
CCXDEV Sprint 151, CCXDEV Sprint 152
sprint_count:
2

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Impact Score:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

    Even after the DataGather/InsightsDataGather CRD had generated the report, the clusteroperator.insights still didn't update its lastReportTime field.

Version-Release number of selected component (if applicable):

    4.16.z

How reproducible:

Trigger periodic gathering and on-demand-gathering in the TP, then check if the lastReportTime is updated.

Steps to Reproduce:

1. Enabling TP.
2. Trigger periodic gathering and on-demand-gathering in the TP.
3. Check if the relevant DataGather/InsightsDataGather CRD generate the report.(Insights will generate recommendations by default when enabling the TP.)
4. Check the lastReportTime field of clusteroperator.insights.

Actual results:

4. The lastReportTime field of clusteroperator.insights was still null.

Expected results:

4. The lastReportTime field of clusteroperator.insights should be updated accordingly.

Additional info:

Assignee:: Katarina Borgulova

Reporter:: Baiyang Zhou

Need Info From:: None

Contributors:: None

QA Contact:: Baiyang Zhou

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2025/08/01 8:32 AM

Updated:: 2025/10/06 2:39 PM