This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2232307 - NetworkAddonsConfigNotReady alert didn't fire
Summary: NetworkAddonsConfigNotReady alert didn't fire
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Networking
Version: 4.14.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.14.2
Assignee: Ram Lavi
QA Contact: Yossi Segev
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-16 08:44 UTC by Ohad
Modified: 2024-04-13 04:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-12-14 16:14:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
A screenshot from the metric (46.64 KB, image/png)
2023-08-16 08:44 UTC, Ohad
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   CNV-32101 0 None None None 2023-12-14 16:14:25 UTC

Description Ohad 2023-08-16 08:44:16 UTC
Created attachment 1983537 [details]
A screenshot from the metric

Description of problem:
When trying to test "NetworkAddonsConfigNotReady" alert, the metric catch the condition for more than the evaluation time and it still didn't make it to the "firing" state.

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


How reproducible:
https://polarion.engineering.redhat.com/polarion/#/project/CNV/workitem?id=CNV-7274

Steps to Reproduce:
1.
2.
3.

Actual results:
The alert didn't fire


Expected results:
Alert should be in "firing" state

Additional info:
Added screenshot from the metric

Comment 1 Krzysztof Majcher 2023-09-13 10:27:37 UTC
Hi,
this looks like the alert that should be owned by a network team. Can you fix it? (we can assist if needed)

Comment 2 Petr Horáček 2023-09-13 13:57:30 UTC
Thanks for reporting this.

Ram, would you own this BZ?

Comment 3 Petr Horáček 2023-09-14 10:35:40 UTC
Since this is not a blocker, I'm moving the target to 4.14.1

Comment 4 Ram Lavi 2023-09-14 10:44:39 UTC
Hey Ohad
Do you have a cluster where I can look at this?

I'm missing key information in order to recreate this from https://polarion.engineering.redhat.com/polarion/#/project/CNV/workitem?id=CNV-7274 (it's not clear to me how you created "a bad CNAO deployment with a non-existing Linux bridge image" if CNV is reconciling the CNAO deployment back to the original)

Comment 5 Red Hat Bugzilla 2024-04-13 04:25:18 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


Note You need to log in before you can comment on or make changes to this bug.