[JBoss JIRA] (JBIDE-23814) Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23814?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23814:
-------------------------------------
Story Points: 8
> Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error
> -----------------------------------------------------------------
>
> Key: JBIDE-23814
> URL: https://issues.jboss.org/browse/JBIDE-23814
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: Red Hat JBoss Developer Studio
> Version: 10.2.0.GA
> Build id: GA-v20161125-1418-B55
> Build date: 20161125-1418
> JBoss Openshift UI Plugin
> Version: 3.3.1.v20161125-0956
> OpenShift
> openshift v3.3.1.3
> Reporter: Siamak Sadeghianfar
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.4.AM2
>
> Attachments: jbds-error.png, jboss-eap70-openshift.png
>
>
> When adding a Server Adapter for an JBoss EAP 7 based deployments on OpenShift, operation fails with this error:
> {{Could not sync /private/tmp/workspace-demo/.metadata/.plugins/org.jboss.ide.eclipse.as.core/inventory-dev-ssadeghi@inventory/deploy to all pods running the service inventory
> OpenShiftBinaryCapability process exited: error: auth info "ssadeghi-redhat.com" does not exist}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24048) Import application: would like to get a workspace project that's using the context-dir and branch used in OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24048?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24048:
-------------------------------------
Story Points: 8
> Import application: would like to get a workspace project that's using the context-dir and branch used in OpenShift
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24048
> URL: https://issues.jboss.org/browse/JBIDE-24048
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: import_wizard, openshift_v3
> Fix For: 4.4.4.AM2
>
> Attachments: CONTEXT_DIR.png, SOURCE_REPOSITORY_REF.png, jboss-eap-quickstarts.png, jboss-kitchensink.png
>
>
> We're missing the ability to provide a context dir within a git repo when importing an application from OpenShift. The application wizard allows the user to set a context dir, which is used when importing right after the successfull creation. The (standalone) import is lacking this.
> steps to reproduce:
> # EXEC: launch openshift application wizard and pick "eap64-basic-s2i"
> # ASSERT: in the next page make sure there is "kitchensink" set to the CONTEXT_DIR template parameter
> !CONTEXT_DIR.png!
> # ASSERT: in the parameters, make sure that the SOURCE_REPOSITORY_REF is set to "6.4.x"
> !SOURCE_REPOSITORY_REF.png!
> # EXEC: finish the wizard and once the resources are created, simply confirm the import dialog that pops up
> # ASSERT: you get a "jboss-kitchensink" in your workspace. The import actually cloned the whole repo "jboss-eap-quickstarts" and imported the project within the "kitchensink" (the CONTEXT_DIR) folder as a workspace project
> !jboss-kitchensink.png!
> # EXEC: switch the branch in the git repo that already exists (ex. switch to master)
> # EXEC: in OpenShift Explorer: kill your workspace project, select the "eap-app" service and choose "Import Application" in the context-menu.
> # EXEC: in the upcoming import wizard, check "reuse existing repository" and then hit "Finish"
> Result:
> You get a project "jboss-eap-quickstart".
> !jboss-eap-quickstarts.png!
> There was no way to provide a context dir. To get the kitchensink project you need to remove the jboss-eap-quickstart" project, checkout the correct branch and reimport "kitchensink" (kitchensink only exists in the 6.4.x branch, not in the 7.x branches) manually as an existing maven project.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-3799) Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3799?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-3799:
-------------------------------------
[~rob.stryker] to be honest I've never seen this. And I'm not sure how exactly to reproduce. But the referenced github issue is resolved.
[~odockal] or [~jrichter1] does this say anything to you? Have you seen this?
> Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime
> -----------------------------------------------------------------------------------------
>
> Key: JBDS-3799
> URL: https://issues.jboss.org/browse/JBDS-3799
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Priority: Critical
> Labels: havoc
> Fix For: 10.4.0.AM2
>
>
> This unresolved issue: https://github.com/projectatomic/adb-atomic-developer-bundle/issues/272
> Is causing rsync issues such as:
> default: Rsyncing folder: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant
> There was an error when attempting to rsync a synced folder.
> Please inspect the error message below for more info.
> Host path: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/
> Guest path: /vagrant
> Command: rsync --verbose --archive --delete -z --copy-links --chmod=ugo=rwX --no-perms --no-owner --no-group --rsync-path sudo rsync -e ssh -p 2222 -o StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/private_key' --exclude .vagrant/ /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ vagrant@127.0.0.1:/vagrant
> Error: Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts.
> dup() in/out/err failed
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4301) Allow loading a variable set of components
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4301?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-4301:
------------------------------
Story Points: 14 (was: 12)
Sprint: devex #128 February 2017
> Allow loading a variable set of components
> ------------------------------------------
>
> Key: JBDS-4301
> URL: https://issues.jboss.org/browse/JBDS-4301
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.4.0.AM1
> Reporter: Jan Richter
> Assignee: Jan Richter
> Fix For: 10.4.0.AM2
>
>
> Currently all the components are hardcoded into the initialization procedure. It would help if there was a way to have them loaded somewhat dynamically form the requirements.json file.
> For example it would allow us to really remove cygwin from unix systems.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24083) Debug NodeJS app is broken - Failed to connect to Standalone V8 VM
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24083?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-24083:
----------------------------------
Assignee: Andre Dietisheim
> Debug NodeJS app is broken - Failed to connect to Standalone V8 VM
> ------------------------------------------------------------------
>
> Key: JBIDE-24083
> URL: https://issues.jboss.org/browse/JBIDE-24083
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.4.4.AM1
> Reporter: Pavol Srna
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: regression
> Fix For: 4.4.4.AM2
>
> Attachments: jbide-23961-restart-1.png
>
>
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24083) Debug NodeJS app is broken - Failed to connect to Standalone V8 VM
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24083?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24083:
-------------------------------
Sprint: devex #129 March 2017
> Debug NodeJS app is broken - Failed to connect to Standalone V8 VM
> ------------------------------------------------------------------
>
> Key: JBIDE-24083
> URL: https://issues.jboss.org/browse/JBIDE-24083
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.4.4.AM1
> Reporter: Pavol Srna
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: regression
> Fix For: 4.4.4.AM2
>
> Attachments: jbide-23961-restart-1.png
>
>
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4123) Progress sometimes not updating for multiple file downloads
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4123?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-4123:
------------------------------
Sprint: devex #123 November 2016, devex #126 January 2017, devex #128 February 2017 (was: devex #123 November 2016, devex #126 January 2017)
> Progress sometimes not updating for multiple file downloads
> -----------------------------------------------------------
>
> Key: JBDS-4123
> URL: https://issues.jboss.org/browse/JBDS-4123
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.2.0.AM2
> Reporter: Jan Richter
> Assignee: Jan Richter
> Fix For: 10.4.0.AM2
>
>
> Namely for CDK, sometimes the progress doesn't register that it should start. The handler that should set the correct values does not seem to fire properly every time. The result is a progress bar stuck on 0% for the entirety of the download.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24048) Import application: would like to get a workspace project that's using the context-dir and branch used in OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24048?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24048:
-------------------------------------
Sprint: devex #129 March 2017
> Import application: would like to get a workspace project that's using the context-dir and branch used in OpenShift
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24048
> URL: https://issues.jboss.org/browse/JBIDE-24048
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: import_wizard, openshift_v3
> Fix For: 4.4.4.AM2
>
> Attachments: CONTEXT_DIR.png, SOURCE_REPOSITORY_REF.png, jboss-eap-quickstarts.png, jboss-kitchensink.png
>
>
> We're missing the ability to provide a context dir within a git repo when importing an application from OpenShift. The application wizard allows the user to set a context dir, which is used when importing right after the successfull creation. The (standalone) import is lacking this.
> steps to reproduce:
> # EXEC: launch openshift application wizard and pick "eap64-basic-s2i"
> # ASSERT: in the next page make sure there is "kitchensink" set to the CONTEXT_DIR template parameter
> !CONTEXT_DIR.png!
> # ASSERT: in the parameters, make sure that the SOURCE_REPOSITORY_REF is set to "6.4.x"
> !SOURCE_REPOSITORY_REF.png!
> # EXEC: finish the wizard and once the resources are created, simply confirm the import dialog that pops up
> # ASSERT: you get a "jboss-kitchensink" in your workspace. The import actually cloned the whole repo "jboss-eap-quickstarts" and imported the project within the "kitchensink" (the CONTEXT_DIR) folder as a workspace project
> !jboss-kitchensink.png!
> # EXEC: switch the branch in the git repo that already exists (ex. switch to master)
> # EXEC: in OpenShift Explorer: kill your workspace project, select the "eap-app" service and choose "Import Application" in the context-menu.
> # EXEC: in the upcoming import wizard, check "reuse existing repository" and then hit "Finish"
> Result:
> You get a project "jboss-eap-quickstart".
> !jboss-eap-quickstarts.png!
> There was no way to provide a context dir. To get the kitchensink project you need to remove the jboss-eap-quickstart" project, checkout the correct branch and reimport "kitchensink" (kitchensink only exists in the 6.4.x branch, not in the 7.x branches) manually as an existing maven project.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23814) Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23814?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23814:
-------------------------------------
Sprint: devex #129 March 2017 (was: devex #128 February 2017)
> Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error
> -----------------------------------------------------------------
>
> Key: JBIDE-23814
> URL: https://issues.jboss.org/browse/JBIDE-23814
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: Red Hat JBoss Developer Studio
> Version: 10.2.0.GA
> Build id: GA-v20161125-1418-B55
> Build date: 20161125-1418
> JBoss Openshift UI Plugin
> Version: 3.3.1.v20161125-0956
> OpenShift
> openshift v3.3.1.3
> Reporter: Siamak Sadeghianfar
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.4.AM2
>
> Attachments: jbds-error.png, jboss-eap70-openshift.png
>
>
> When adding a Server Adapter for an JBoss EAP 7 based deployments on OpenShift, operation fails with this error:
> {{Could not sync /private/tmp/workspace-demo/.metadata/.plugins/org.jboss.ide.eclipse.as.core/inventory-dev-ssadeghi@inventory/deploy to all pods running the service inventory
> OpenShiftBinaryCapability process exited: error: auth info "ssadeghi-redhat.com" does not exist}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years