[jbosstools-issues] [JBoss JIRA] (JBIDE-21849) [AP] Not able to list services under a project after login to AP

[Jeff Cantrill (JIRA)]

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

Jeff Cantrill commented on JBIDE-21849:
---------------------------------------

[~maxandersen] I don't recall ever being directed to have to support Atomic Platform.  This will require many changes to account for the missing Openshift bits as we are making assumptions to the resource kinds that are available.  AP is basically just kubernetes which means we will need to account for missing functionality and how to NOT surface it in the platform.  One example alone is the new deployment view as walk a resource tree to map out associations.  We can probably still make it work, but I don't think its a reasonable short term goal.

> [AP] Not able to list services under a project after login to AP
> ----------------------------------------------------------------
>
>                 Key: JBIDE-21849
>                 URL: https://issues.jboss.org/browse/JBIDE-21849
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.3.1.Beta2
>         Environment: -JBoss OpenShift 3 Tools        3.2.0.Alpha1-v20160310-0336-B1191        
> -AP puddle: 2016-03-09.2
> -oc version:
> oc v3.2.0.1
> kubernetes v1.2.0-alpha.7-703-gbc4550d
>            Reporter: Xia Zhao
>            Assignee: Viacheslav Kabanovich
>            Priority: Critical
>              Labels: openshift_v3
>
> -Not able to list services under a project after login to RHAP, get error message "Could not list BuildConfig resources in namespace xia: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}"
> -Issue did not repro if switch to OSE
> -Repro on Linux/Windows/Mac OS



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