[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 commented on JBDS-3624:
-----------------------------------
I'm struggling to reproduce this even without the fix. [~ppitonak] , could you try this one out?
> 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] (JBDS-3985) Modify installation progress bar to include supplemental runtimes
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3985?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3985.
-----------------------------
Tried with both standard devstudio installers and the IS one - devstudio (without the additional runtimes) seems unaffected and IS installer looks just like on the screenshots. So I guess this is ready to be closed.
> Modify installation progress bar to include supplemental runtimes
> -----------------------------------------------------------------
>
> Key: JBDS-3985
> URL: https://issues.jboss.org/browse/JBDS-3985
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.1.0.AM1
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Priority: Minor
> Fix For: 10.1.0.AM3
>
> Attachments: x1.png, x2.png
>
>
> At install time, if an additional runtime is specified it does not appear in the overall progress bar.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBTIS-827) Update site for JBDS-IS 9.0.1.GA-EA still refers to JBDS-IS 9.0.1.CR2-EA
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-827:
---------------------------------------
Summary: Update site for JBDS-IS 9.0.1.GA-EA still refers to JBDS-IS 9.0.1.CR2-EA
Key: JBTIS-827
URL: https://issues.jboss.org/browse/JBTIS-827
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Reporter: Andrej Podhradsky
Priority: Blocker
The composite files are not consistent
{code:title=compositeArtifacts.xml}
<children size='2'>
<!-- IS ONLY -->
<child location='../9.0.1.GA/earlyaccess/'/>
<child location='../9.0.1.GA/earlyaccess/targetplatform/'/>
</children>
{code}
{code:title=compositeContent.xml}
<children size='2'>
<!-- IS ONLY -->
<child location='../9.0.1.CR3/earlyaccess/'/>
<child location='../9.0.1.CR3/earlyaccess/targetplatform/'/>
</children>
{code}
--
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 Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22913?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-22913:
------------------------------------
This has been fixed by https://github.com/openshift/openshift-restclient-java/commit/72cc3c6f32d...
> 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
>
> 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.
--
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:
---------------------------------------
Yes, it is 100 % reproducible. Tried it also on build with ID AM3-v20160808-1058-B5722 and still able to reproduce it.
> 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
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22959) Renamte Deployment to Replication Controller
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22959?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22959:
----------------------------------
Labels: openshift_v3 (was: )
> Renamte Deployment to Replication Controller
> --------------------------------------------
>
> Key: JBIDE-22959
> URL: https://issues.jboss.org/browse/JBIDE-22959
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Labels: openshift_v3
>
> We should rename Deployment in tabbed properties to Replication Controller. I was complaining about it some times ago, but now I found also good reason to change it - underlying Kubernetes technology has Deployment resources and ReplicaSets (new generation of replication controller). And those resources are something a bit different although it has similar functionality. For users coming from Kubernetes world or those who are familiar with Kubernetes, could this be a bit misleading.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22959) Renamte Deployment to Replication Controller
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22959:
-------------------------------------
Summary: Renamte Deployment to Replication Controller
Key: JBIDE-22959
URL: https://issues.jboss.org/browse/JBIDE-22959
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.1.AM3
Reporter: Marián Labuda
We should rename Deployment in tabbed properties to Replication Controller. I was complaining about it some times ago, but now I found also good reason to change it - underlying Kubernetes technology has Deployment resources and ReplicaSets (new generation of replication controller). And those resources are something a bit different although it has similar functionality. For users coming from Kubernetes world or those who are familiar with Kubernetes, could this be a bit misleading.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months