Bug 1942091 - New namespaces created outside the web console are not picked up by polling
Summary: New namespaces created outside the web console are not picked up by polling
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Virtualization
Classification: Red Hat
Component: General
Version: 2.0.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 2.0.0
Assignee: Mike Turley
QA Contact: Maayan Hadasi
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-23 16:08 UTC by Nandini Chandra
Modified: 2021-06-10 17:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-10 17:11:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github konveyor forklift-ui pull 505 0 None open Bug 1942091: Re-enable polling in the General step of the plan wizard to pick up new namespace options 2021-04-05 19:05:00 UTC
Red Hat Product Errata RHEA-2021:2381 0 None None None 2021-06-10 17:11:38 UTC

Description Nandini Chandra 2021-03-23 16:08:13 UTC
Description of problem:
----------------------
If a new namespace is created in OCP while the plan wizard is open, it is not automatically added to the list of options in the target namespace dropdown. If the user cancels and reopens the wizard, the new namespace does appear. Need to make sure polling is behaving properly while on this wizard step.


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


How reproducible:
----------------
Always


Steps to Reproduce:
------------------
1.
2.
3.

Actual results:
---------------


Expected results:
-----------------


Additional info:
---------------

Comment 1 Mike Turley 2021-04-06 16:40:19 UTC
Fix is merged (https://github.com/konveyor/forklift-ui/pull/505)

Comment 2 Fabien Dupont 2021-04-08 12:20:48 UTC
This fix should be part of build v2.0.0-14, iib:64369.

Comment 3 Maayan Hadasi 2021-04-19 11:45:23 UTC
Verified this issue with MTV 2.0.0-17 / iib:66911 and it is still relevant. It even seems that we have a regression
I was not able to choose a new created target namespace in migration plan wizard, even after reloading MTV page

Moving back to ASSIGNED

Comment 4 Mike Turley 2021-04-19 13:47:33 UTC
Hmm.. I verified the fix myself, so whatever is causing the regression must be blocking that list of namespaces from being updated at all. I think that must mean the new namespace isn't being picked up by the inventory API. @jortel do you know why that might be?

@mguetta how long after creating the namespace did you wait for it to appear? Would you be able to provide access to the cluster where you saw this regression?

Comment 5 Maayan Hadasi 2021-04-19 14:11:47 UTC
(In reply to Mike Turley from comment #4)
> 
> @mguetta how long after creating the namespace did you wait for
> it to appear? Would you be able to provide access to the cluster where you
> saw this regression?

I tried to update the namespaces dropdown list several times (by closing and reopening the list, cancel the migration plan and recreate, reload the MTV page, reload OCP), so I guess it took ~5 minutes
Regarding access to the cluser where I tested it - I sent in Gmail

Comment 7 Jeff Ortel 2021-04-19 21:49:55 UTC
The inventory is not (k8s) watching the correct `Kind` for namespaces.  Not a regression.  Fixing.

Comment 9 Jeff Ortel 2021-04-20 20:52:26 UTC
Merged to release branch.

Comment 10 Fabien Dupont 2021-05-03 12:10:07 UTC
The fix should be part of build mtv-operator-bundle-container-2.0.0-4 / iib:72115.

Comment 11 Maayan Hadasi 2021-05-06 08:29:11 UTC
Verified as fixed.
mtv-operator-bundle-container-2.0.0-7 / iib 72753

Comment 14 errata-xmlrpc 2021-06-10 17:11:29 UTC
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 (MTV 2.0.0 images), 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/RHEA-2021:2381


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