]
Jeff Cantrill commented on JBIDE-22803:
---------------------------------------
* I presume the openshift/version should be allowable by an anonymous user. I would
expect that to be a bug.
* I think 101 is a client upgrade code related to using websockets and it maybe the rest
client needs to be tweaked to support watching project. I might suggest playing with the
Watch integration test in the REST client to confirm it works as expected
* There is a timeout from the server that drops websockets after a given time period (5
min i think) and requires clients to reconnect. The restclient does not handle any
reconnect logic; all of it was pushed into jbt
Explorer: When OS projects are created and deleted, seems Openshift
explorer restores non existing values
---------------------------------------------------------------------------------------------------------
Key: JBIDE-22803
URL:
https://issues.jboss.org/browse/JBIDE-22803
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.1.AM2
Reporter: Jeff MAURY
Assignee: Dmitrii Bocharov
Labels: explorer, openshift, openshift_v3
Fix For: 4.4.2.AM2
Attachments: after application creation.png, after build finished.png, Openshift
Web Console.png, screenshot-1.png
EXEC: create an Openshift project
EXEC: expand it
EXEC: Create an application in this project (nodejs-example)
ASSERT: wait for the pod to be available
EXEC: delete the Openshit project
EXEC: create an Openshift project (using the same name. You may have to repeat this step
as you may got error that it still exists)
EXEC: expand it
EXEC: Create an application in this project (nodejs-example)
EXEC: expand the nodejs-example node
ASSERT: you should see 2 pods the old one and the build pod you just created:
[^screenshot-1.png]