[jbosstools-issues] [JBoss JIRA] (JBIDE-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values

[Dmitrii Bocharov (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13303213#comment-13303213 ] 

Dmitrii Bocharov commented on JBIDE-22803:
------------------------------------------

[~jeffmaury], [~adietish] i talked to OS devs and they pointed me to https://github.com/openshift/origin/blob/master/pkg/cmd/cli/cmd/version.go#L147 on how to retrieve the OS version. I tested it on https://console.engint.openshift.com, e.g. https://console.engint.openshift.com/version/openshift, but had an error: User "openshift-dev" cannot "get" on "/version/openshift"
I talked to [~jcantrill] and [~deads2k]:
{quote}deads2k: dbocharo: it's an upgrade step: https://docs.openshift.org/latest/architecture/additional_concepts/authorization.html#updating-cluster-roles
deads2k: dbocharo: the roles are based on the client being used.  If you start a fresh server with a fresh etcd that has the /version/openshift endpoint, it's all set up already
deads2k: dbocharo: I think that server is too old.  Pretty sure we added it in 3.3{quote}

So we wanted to use the OS version to detect whether watching projects feature enabled or not. And now it turned out that the feature of getting OS version is version-dependent itself =(

> 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]



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)