[jbosstools-issues] [JBoss JIRA] (JBIDE-23622) Build Log: impossible to get logs once the build pod is completed

[Andre Dietisheim (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-23622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated JBIDE-23622:
-------------------------------------
    Steps to Reproduce: 
EXEC: Create a new OpenShift 3 application from a template/builder image.
ASSERT: Build is triggered and visible in Properties view
EXEC: Wait until build is finished, in "Properties"/"Build" tab you can see your build in state "Competed"
EXEC: In "Properties" view, select "Builds" tab and pick "Build Log..."

Result:
You cannot get the log of the finished build, you're told that the pod for the build is Completed.
!cannot-build-log.png! 

Excepted result:
You should be able to get the build logs even once they're finished. In oc you can do this 

  was:
EXEC: Create a new OpenShift 3 application from a template/builder image.
EXEC: Wait until build of an application finish.
ASSERT: There is a build pod with COMPLETE state.
EXEC: Select Pod Log... if opening via context menu of a pod, or Build Log... if opening via context menu of a build.

RESULT: Error dialog is shown.
EXPECTED RESULT: Log of completed build is shown in console.



> Build Log: impossible to get logs once the build pod is completed
> -----------------------------------------------------------------
>
>                 Key: JBIDE-23622
>                 URL: https://issues.jboss.org/browse/JBIDE-23622
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.2.Final
>            Reporter: Marián Labuda
>              Labels: openshift_v3
>         Attachments: log_build.png
>
>
> When I am trying to get a log of completed build, either via context menu of a pod in tabbed property Pods or via context menu of a build in tabbed property Builds, I get following error dialog
> !log_build.png!
> There is no error in log.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)