You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Describe the bug
I ran a few migrations against a single MigPlan while working on #723 . I found that the PodVolumeRestores and PodVolumeBackups will sometimes only show up in the plan tree view if you kill mig-controller, which also kills the discovery service, and let it restart.
The PodVolumeRestores and PodVolumeBackups are also missing from JSON output of /plan/tree.
What I expected
What I saw
Same as above, but with PodVolumeBackups and PodVolumeRestores missing until I restarted the controller.
To Reproduce
Steps to reproduce the behavior:
Run a few migrations against the same MigPlan
Check the debug tree view in the UI
Notice that the output received from the discovery service is missing PodVolumeBackups that are present on the cluster
The text was updated successfully, but these errors were encountered:
I saw similar behavior when preparing MTC labs with MTC 1.3.1.
I consistently failed to see any PVB/PVR data in my debug views.
I was using a stock MTC 1.3.1 install from production.
jwmatthews
changed the title
Discovery Service requires restart to get latest changes to Plan Tree view
BZ#1896015: Discovery Service requires restart to get latest changes to Plan Tree view
Nov 9, 2020
djwhatle
changed the title
BZ#1896015: Discovery Service requires restart to get latest changes to Plan Tree view
Bug 1896015: Discovery Service requires restart to get latest changes to Plan Tree view
Nov 9, 2020
See: https://bugzilla.redhat.com/show_bug.cgi?id=1896015
Describe the bug
I ran a few migrations against a single MigPlan while working on #723 . I found that the PodVolumeRestores and PodVolumeBackups will sometimes only show up in the plan tree view if you kill mig-controller, which also kills the discovery service, and let it restart.
The PodVolumeRestores and PodVolumeBackups are also missing from JSON output of /plan/tree.
What I expected

What I saw
Same as above, but with PodVolumeBackups and PodVolumeRestores missing until I restarted the controller.
To Reproduce
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: