[JBoss JIRA] (JBDS-3624) Error while parsing response from auth server
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3624?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3624.
-----------------------------
Looks like this got patched up in some of the libraries as well. I think we can close this issue.
> Error while parsing response from auth server
> ---------------------------------------------
>
> Key: JBDS-3624
> URL: https://issues.jboss.org/browse/JBDS-3624
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.GA
> Reporter: Pavol Pitonak
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.1.0.AM3
>
> Attachments: auth-error.png
>
>
> # npm start
> # type "asdf" to username field
> # type "asdf" to password field
> # open dev tools (Ctrl + Shift + i on Linux)
> # click "Log in" button
> result:
> This stack trace appears in console log:
> {code}
> SyntaxError: Unexpected token I
> at Object.parse (native)
> at fromJson (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:1274:14)
> at defaultHttpResponseTransform (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:9463:16)
> at file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:9554:12
> at forEach (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:343:20)
> at transformData (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:9553:3)
> at transformResponse (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:10322:21)
> at processQueue (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:14795:28)
> at file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:14811:27
> at Scope.$eval (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:16055:28)
> {code}
> JSON.parse failes because the server returned "Invalid user credentials for user asdf"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22966) create bzira fork that supports scraping RH bugzilla
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22966?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-22966:
---------------------------------------------
[~rgrunber] I Agree that would be nice and i'm all for it - but just to let you know why I didn't bother implementing it initially was the following:
A) often when an upstream eclipse issue is resolved/closed it does not mean we are actually done with it on our side - so not changing the state was the simplest.
B) in many cases jira workflows might prevent setting the state - we could of course just fail silently in that case, but it was this issue + A that made me skip it.
If someone does implement then awesome - but I think it might want to be a setting based on products whether you really want the eclipse issue to disappear from view/boards in jira. It might be we learned we do all the work anyway and thus not worth the complexity. In any case - just explaning the reasons why it was not there initially.
> create bzira fork that supports scraping RH bugzilla
> ----------------------------------------------------
>
> Key: JBIDE-22966
> URL: https://issues.jboss.org/browse/JBIDE-22966
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.4.1.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> Sample issue to scrape:
> https://bugzilla.redhat.com/show_bug.cgi?id=1363849
> More issues:
> https://bugzilla.redhat.com/buglist.cgi?component=rh-eclipse46&list_id=56...
> Target method:
> * look for whiteboard = RHT (then filter by date since last change, as current bzira.py [1] does)
> Mappings:
> * BZ Product = Red Hat Software Collections --> RH-ECLIPSE jira
> * BZ component = rh-eclipse46 (maybe others in future, eg., eclipse-cdt, eclipse-docker) --> same component in jira (python script will generate new components automatically)
> * Version = rh-eclipse46 --> "rh-eclipse46" version in JIRA
> * Target Milestone --> label in JIRA
> * Target Release -> label in JIRA
> [1] https://github.com/maxandersen/jiralint/blob/master/bzira.py
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22969:
---------------------------------------
[~akazakov] It's more about of configuration of environment than writing new tests. I can point Dmitry to how to set up proxy in Eclipse via RedDeer (native or manual). Can someone bring light on this? In which area we expect proxy come to game in relation to OpenShift tooling and CDK OpenShift instance? I can only see the DevSuite installer stuff affected by this. And than OpenShift working with external docker registries/docker hub. Not sure whether there could be some specific tests, it would be more like about having a proxy-using machine and running existing tests on it.
There is also another very important point of view - remote OpenShift instance. If customer/user works with remote OpenShift server, proxy affects this area much wider. Much more places where things could get broken (e.g. rsync stuff).
> Make sure OpenShift Tools support proxies
> -----------------------------------------
>
> Key: JBIDE-22969
> URL: https://issues.jboss.org/browse/JBIDE-22969
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Reporter: Alexey Kazakov
> Assignee: Dmitry Bocharov
> Fix For: 4.4.1.Final
>
>
> CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too.
> If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side.
> This issue covers:
> - testing
> - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests)
> - fixing any problems we have in OpenShift tooling regarding proxy support.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22913) Server Adapter: Publish does not work
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22913?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22913:
---------------------------------------
[~jeffmaury] it looks ok. Latest changes to org.jboss.tool.openshift.client plugin has been merged on 2016-07-26 so latest build of this plugin is from 2016-07-26. If there are no commits to a specific plugin, the plugin is not rebuild, because it is not necessary.
> Server Adapter: Publish does not work
> -------------------------------------
>
> Key: JBIDE-22913
> URL: https://issues.jboss.org/browse/JBIDE-22913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.1.AM3
>
>
> When I create a new OpenShift 3 server adapter with already running application pod, I get following error in error dialog and initial publish does not work. Autopublish does not work at all and also manual triggering of publishment throws same error.
> {code}
> Could not sync /home/mlabuda/workspaces/0804/.metadata/.plugins/org.jboss.ide.eclipse.as.core/projectname000@eap-app/deploy to all pods running the service eap-app
> OpenShiftBinaryCapability process exited: WARNING: rsync command not found in path. Please use your package manager to install it.
> Ignoring the following flags because they only apply to rsync: --exclude, --no-perms
> tar: ROOT.war/META-INF/MANIFEST.MF: Cannot open: Not a directory
> tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.properties: Cannot open: Not a directory
> tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/beans.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/META-INF/persistence.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/import.sql: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/controller/MemberController.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberListProducer.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberRepository.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/model/Member.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/JaxRsActivator.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/MemberResourceRESTService.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/service/MemberRegistration.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/util/Resources.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/faces-config.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/kitchensink-quickstart-ds.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/templates/default.xhtml: Cannot open: Not a directory
> tar: ROOT.war/index.html: Cannot open: Not a directory
> tar: ROOT.war/index.xhtml: Cannot open: Not a directory
> tar: ROOT.war/resources/css/screen.css: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/asidebkg.png: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/banner.png: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/bkg-blkheader.png: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/headerbkg.png: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/rhjb_eap_logo.png: Cannot open: Not a directory
> tar: Exiting with failure status due to previous errors
> error: error extracting tar at destination directory: error executing remote command: Error executing command in container: Error executing in Docker Container: 2
> {code}
> I have installed rsync rsync-3.1.2-2.fc24.x86_64. I tried oc binary 1.2.0. and also 1.2.1. Issue describes not found rsync on PATH, although it is present there.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3965) Add a note on how to launch cdk in last page of devsuite installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3965?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3965:
-------------------------------------
Martin, that is good Idea, but installer has at least three component to install CDK, DevStudio and OpenJDK, which gives us twice more combinations. What if new component added in future. I'd rather put link to knowledge base search with tag 'get-started' plus tag for each installed component and start button for DevStudio if installed.
> Add a note on how to launch cdk in last page of devsuite installer
> ------------------------------------------------------------------
>
> Key: JBDS-3965
> URL: https://issues.jboss.org/browse/JBDS-3965
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.1.0.AM2
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Fix For: 10.1.0.AM3
>
>
> Recently, [~rick_wagner] gave us some feedback on how he tried to use the devsuite installer and then connect to the docker daemon running in cdk.
> This is described here: JBIDE-22734
> What happened was that Rick didn't know he was supposed to start CDK from the Servers view. Having some prior knowledge of CDK, he started it from CLI. Then he went to the Docker Explorer view and wanted to connect to cdk's docker daemon.
> Normally, the docker connection will be created for you automatically, but that assumes you start the cdk adapter in Servers View.
> So here's a proposal:
> Perhaps at the end of the devsuite installer, just before devstudio is launched, we could briefly note that to start using CDK, you can start it from the Server view, once devstudio is launched?
> Please note that the actual name of the server adapter is probably Container Runtime Environment, but I'm not 100 % sure, this needs to be verified.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-21744) cdk-created docker connection can have wrong name if you have multiple cdk server adapters
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21744?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-21744.
---------------------------------
Resolution: Done
Done
> cdk-created docker connection can have wrong name if you have multiple cdk server adapters
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21744
> URL: https://issues.jboss.org/browse/JBIDE-21744
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.1.AM3
>
>
> I noticed that if I have two cdk server adapters, start the first one, stop it, start the second, then docker explorer will only show a connection of the first server name, not the second.
> This is probably because the connection will stay there after the first server start and on second server start, the tooling only checks if the docker host url matches. If it does, it will just reuse it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3983) Development Suite Installer should work behind proxy
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3983?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3983:
--------------------------------------
If user is using a proxy for the installer then we could configure the system environments for CDK so it will work out of the box.
> Development Suite Installer should work behind proxy
> ----------------------------------------------------
>
> Key: JBDS-3983
> URL: https://issues.jboss.org/browse/JBDS-3983
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Affects Versions: 10.1.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.1.0.AM3
>
>
> DevSuite installer cannot download stack software form external links because it uses nodejs request module without proxy settings.
> CDK also requires proxy to be configured to have vagrant up working after installation, which could affect CDK Server Adapter Implementation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22913) Server Adapter: Publish does not work
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22913?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22913:
--------------------------------------
Assignee: Nick Boldt (was: Jeff MAURY)
> Server Adapter: Publish does not work
> -------------------------------------
>
> Key: JBIDE-22913
> URL: https://issues.jboss.org/browse/JBIDE-22913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.1.AM3
>
>
> When I create a new OpenShift 3 server adapter with already running application pod, I get following error in error dialog and initial publish does not work. Autopublish does not work at all and also manual triggering of publishment throws same error.
> {code}
> Could not sync /home/mlabuda/workspaces/0804/.metadata/.plugins/org.jboss.ide.eclipse.as.core/projectname000@eap-app/deploy to all pods running the service eap-app
> OpenShiftBinaryCapability process exited: WARNING: rsync command not found in path. Please use your package manager to install it.
> Ignoring the following flags because they only apply to rsync: --exclude, --no-perms
> tar: ROOT.war/META-INF/MANIFEST.MF: Cannot open: Not a directory
> tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.properties: Cannot open: Not a directory
> tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/beans.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/META-INF/persistence.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/import.sql: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/controller/MemberController.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberListProducer.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberRepository.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/model/Member.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/JaxRsActivator.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/MemberResourceRESTService.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/service/MemberRegistration.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/util/Resources.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/faces-config.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/kitchensink-quickstart-ds.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/templates/default.xhtml: Cannot open: Not a directory
> tar: ROOT.war/index.html: Cannot open: Not a directory
> tar: ROOT.war/index.xhtml: Cannot open: Not a directory
> tar: ROOT.war/resources/css/screen.css: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/asidebkg.png: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/banner.png: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/bkg-blkheader.png: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/headerbkg.png: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/rhjb_eap_logo.png: Cannot open: Not a directory
> tar: Exiting with failure status due to previous errors
> error: error extracting tar at destination directory: error executing remote command: Error executing command in container: Error executing in Docker Container: 2
> {code}
> I have installed rsync rsync-3.1.2-2.fc24.x86_64. I tried oc binary 1.2.0. and also 1.2.1. Issue describes not found rsync on PATH, although it is present there.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22913) Server Adapter: Publish does not work
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22913?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22913:
-----------------------------------
Fix Version/s: 4.4.1.AM3
> Server Adapter: Publish does not work
> -------------------------------------
>
> Key: JBIDE-22913
> URL: https://issues.jboss.org/browse/JBIDE-22913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.1.AM3
>
>
> When I create a new OpenShift 3 server adapter with already running application pod, I get following error in error dialog and initial publish does not work. Autopublish does not work at all and also manual triggering of publishment throws same error.
> {code}
> Could not sync /home/mlabuda/workspaces/0804/.metadata/.plugins/org.jboss.ide.eclipse.as.core/projectname000@eap-app/deploy to all pods running the service eap-app
> OpenShiftBinaryCapability process exited: WARNING: rsync command not found in path. Please use your package manager to install it.
> Ignoring the following flags because they only apply to rsync: --exclude, --no-perms
> tar: ROOT.war/META-INF/MANIFEST.MF: Cannot open: Not a directory
> tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.properties: Cannot open: Not a directory
> tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/beans.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/META-INF/persistence.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/import.sql: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/controller/MemberController.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberListProducer.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberRepository.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/model/Member.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/JaxRsActivator.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/MemberResourceRESTService.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/service/MemberRegistration.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/util/Resources.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/faces-config.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/kitchensink-quickstart-ds.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/templates/default.xhtml: Cannot open: Not a directory
> tar: ROOT.war/index.html: Cannot open: Not a directory
> tar: ROOT.war/index.xhtml: Cannot open: Not a directory
> tar: ROOT.war/resources/css/screen.css: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/asidebkg.png: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/banner.png: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/bkg-blkheader.png: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/headerbkg.png: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/rhjb_eap_logo.png: Cannot open: Not a directory
> tar: Exiting with failure status due to previous errors
> error: error extracting tar at destination directory: error executing remote command: Error executing command in container: Error executing in Docker Container: 2
> {code}
> I have installed rsync rsync-3.1.2-2.fc24.x86_64. I tried oc binary 1.2.0. and also 1.2.1. Issue describes not found rsync on PATH, although it is present there.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months