Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NETOBSERV-922 - Flaky topology data #301

Merged
merged 3 commits into from
Apr 7, 2023

Conversation

jpinsonneau
Copy link
Contributor

@jpinsonneau jpinsonneau commented Mar 13, 2023

  • updated cypress testing
  • fixed topology crash on unknown nodes while grouping

@codecov
Copy link

codecov bot commented Mar 13, 2023

Codecov Report

Merging #301 (f52050f) into main (644410a) will decrease coverage by 0.06%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #301      +/-   ##
==========================================
- Coverage   58.41%   58.35%   -0.06%     
==========================================
  Files         148      148              
  Lines        6581     6587       +6     
  Branches      786      792       +6     
==========================================
  Hits         3844     3844              
- Misses       2520     2526       +6     
  Partials      217      217              
Flag Coverage Δ
uitests 58.97% <0.00%> (-0.08%) ⬇️
unittests 56.59% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
web/src/model/topology.ts 33.51% <0.00%> (-1.15%) ⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Comment on lines +414 to +415
const parent = data.nodeType !== 'unknown' ? addPossibleGroups(data.peer) : undefined;
let node = nodes.find(n => n.type === 'node' && n.id === data.peer.id);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The root cause of this issue is that unknown nammed items were generating nodes with the same peer id as groups.

To avoid such issues 'unknown' nodes can't have parents + nodes find function will return only node types

parent.children!.push(node.id);
if (parent) {
if (parent.id == node.id) {
console.error('addNode parent === node', parent, node);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also console will throw error in case of similar issue

@jotak
Copy link
Member

jotak commented Apr 3, 2023

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Apr 3, 2023
@Amoghrd
Copy link
Contributor

Amoghrd commented Apr 3, 2023

/ok-to-test

@openshift-ci openshift-ci bot added the ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. label Apr 3, 2023
@github-actions
Copy link

github-actions bot commented Apr 3, 2023

New image: ["quay.io/netobserv/network-observability-console-plugin:2faf5f7"]. It will expire after two weeks.

@Amoghrd
Copy link
Contributor

Amoghrd commented Apr 3, 2023

@jpinsonneau All the cola layouts and force layouts look weird. This occurred after I refreshed after encountering the below error(was clicking a lot of things and ended up on this error, dont know the exact scope and group)

Screenshot 2023-04-03 at 5 07 14 PM

This is how topology looks

Screenshot 2023-04-03 at 5 19 41 PM

@jpinsonneau
Copy link
Contributor Author

@jpinsonneau All the cola layouts and force layouts look weird. This occurred after I refreshed after encountering the below error(was clicking a lot of things and ended up on this error, dont know the exact scope and group)

Screenshot 2023-04-03 at 5 07 14 PM

I can't reproduce this on OCP 4.12.10 + chrome 110.0.5481.100

  • Are you using others versions ?
  • Do you reproduce multiple times or just once ?
    If you try again, feel free to start a recording before so we can easilly post analyse what happened.

This is how topology looks
Screenshot 2023-04-03 at 5 19 41 PM

I'm also having this while playing with groups. Switching "Collapse groups" option usually fix that. We can create a followup for that as it's not related to parent / children crash.

@Amoghrd
Copy link
Contributor

Amoghrd commented Apr 6, 2023

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved QE has approved this pull request label Apr 6, 2023
@jpinsonneau
Copy link
Contributor Author

/approve

@openshift-ci
Copy link

openshift-ci bot commented Apr 7, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jpinsonneau

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved label Apr 7, 2023
@openshift-merge-robot openshift-merge-robot merged commit 882a2f0 into netobserv:main Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. qe-approved QE has approved this pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants