[JBoss JIRA] (JBIDE-21971) jboss-jsonp quickstart includes an empty description as displayed in Central
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21971?page=com.atlassian.jira.plugi... ]
Paul Robinson commented on JBIDE-21971:
---------------------------------------
[~fbricon] the DCP data is rebuilt daily. The source content needs fixing, as any manual change will be over-written.
We are allowed to make content changes to quickstart repos without going through QE. So it's just a matter of fixing the quickstart readme, creating a new tag, and updating the JBD and RHD websites to point to the new tag. Let me know if you decide to go down this route and need more details.
> jboss-jsonp quickstart includes an empty description as displayed in Central
> ----------------------------------------------------------------------------
>
> Key: JBIDE-21971
> URL: https://issues.jboss.org/browse/JBIDE-21971
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, upstream
> Affects Versions: 4.3.1.CR1
> Environment: 4.3.1-SNAPSHOT (CR1-v20160324-1710-B391)
> Reporter: Len DiMaggio
> Labels: havoc
> Fix For: 4.4.x
>
> Attachments: Empty_Desc.png
>
>
> See attached screenshot - the quickstart's description is empty.
> !Empty_Desc.png|width=800!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22818) vagrant service-manager call experiences timeout after output
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-22818:
-----------------------------------
Summary: vagrant service-manager call experiences timeout after output
Key: JBIDE-22818
URL: https://issues.jboss.org/browse/JBIDE-22818
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.4.1.AM2
Reporter: Rob Stryker
!ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:48:26.869
!MESSAGE Unable to successfully complete a call to vagrant service-manager.
!STACK 0
java.util.concurrent.TimeoutException: Process output:
^[[0m # docker env:^[[0m # Set the following environment variables to enable access to the # docker daemon running inside of the vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc login https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # run following command to configure your shell: # eval "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153)
at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108)
at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85)
at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67)
at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:185)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:174)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:154)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:133)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:250)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:242)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:235)
!ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:49:07.139
!MESSAGE Unable to successfully complete a call to vagrant service-manager.
!STACK 0
java.util.concurrent.TimeoutException: Process output:
^[[0m # docker env:^[[0m # Set the following environment variables to enable access to the # docker daemon running inside of the vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc login https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # run following command to configure your shell: # eval "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153)
at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108)
at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85)
at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67)
at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59)
at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:53)
at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:43)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22644) Unable to perform oc binary actions because of insecure flag
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22644?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22644:
-------------------------------
Sprint: devex #118 July 2016
> Unable to perform oc binary actions because of insecure flag
> ------------------------------------------------------------
>
> Key: JBIDE-22644
> URL: https://issues.jboss.org/browse/JBIDE-22644
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
>
> Trying to retrieve pod logs or any oc binary action results in warning of:
> specifying a root certificates file with the insecure flag is not allowed
> Per deads openshift dev "...it means that your kubeconfig file has a CA set, but you're trying to connect insecurely"
> Persumably this requires us to make sure KUBECONFIG env var is not set when executing oc binary commands.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22640) Server Adapter Editor: Update to Openshift server adapter is not saved
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22640?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22640:
-------------------------------
Sprint: devex #118 July 2016
> Server Adapter Editor: Update to Openshift server adapter is not saved
> ----------------------------------------------------------------------
>
> Key: JBIDE-22640
> URL: https://issues.jboss.org/browse/JBIDE-22640
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.4.0.Final
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.4.1.AM3
>
>
> ASSERT: create an Openshift3 connection
> ASSERT: create a server adapter from that connection
> ASSERT: delete the Openshift3 connection
> EXEC: open the server adapter
> ASSERT: the connection filed is blank
> EXEC: using the dropdown change the connection
> ASSERT: the dirty flag of the server editor is not set
> EXEC: close the server editor
> EXEC: open the server editor again
> ASSERT: the connection field is still blank
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22640) Server Adapter Editor: Update to Openshift server adapter is not saved
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22640?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-22640:
----------------------------------
Assignee: Andre Dietisheim
> Server Adapter Editor: Update to Openshift server adapter is not saved
> ----------------------------------------------------------------------
>
> Key: JBIDE-22640
> URL: https://issues.jboss.org/browse/JBIDE-22640
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.4.0.Final
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.4.1.AM3
>
>
> ASSERT: create an Openshift3 connection
> ASSERT: create a server adapter from that connection
> ASSERT: delete the Openshift3 connection
> EXEC: open the server adapter
> ASSERT: the connection filed is blank
> EXEC: using the dropdown change the connection
> ASSERT: the dirty flag of the server editor is not set
> EXEC: close the server editor
> EXEC: open the server editor again
> ASSERT: the connection field is still blank
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22625) Remote server with FS operations: Unable to retrieve a list of remote deployment scanners
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22625?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22625:
-------------------------------------
No... some users cannot expose the remote server on ports.... so we need to do our best to support it. this is a mess :(
> Remote server with FS operations: Unable to retrieve a list of remote deployment scanners
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22625
> URL: https://issues.jboss.org/browse/JBIDE-22625
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> Previously I reported this as part of JBIDE-22605, but I think it deserves its own issue.
> When I setup a remote EAP 7 server with FS operations and then start it, I always get this in the error log:
> Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss EAP 7.0
> Today, I also noticed this info message in the error view:
> org.eclipse.rse.core
> Saved passwords are not available for migration to secure storage. Deprecated authorization classes (org.eclipse.core.runtime.compatibility.auth) are not installed.
> I wonder if this is related? Do we require authentication to get the list of deployment scanners?
> BTW, org.eclipse.core.runtime.compatibility was removed in JBIDE-21382 and I suggested org.eclipse.core.runtime.compatibility.auth may be removed too - JBIDE-22602. But as of now it's still in the TP.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-21877) Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21877:
-------------------------------------
Issue Type: Enhancement (was: Bug)
> Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21877
> URL: https://issues.jboss.org/browse/JBIDE-21877
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: screenshot-1.png
>
>
> When I am trying to connect to OpenShift connection with outdated token stored in secure storage, an error tree item is shown in OpenShift Explorer under the connection. Erro tree item is "java.lang.NullPointerException", but it could be something more user friendly such as "Expired credentials" or the one we are already using in other scenarious - You must obtain an API token by .... Following stack trace is in error log
> {code}
> There was an error retrieving children in the OpenShift explorer
> java.lang.NullPointerException
> at org.eclipse.epp.internal.mpc.core.util.ProxyHelper$ProxyAuthenticator.getPasswordAuthentication(ProxyHelper.java:124)
> at java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getSystemCreds(SystemDefaultCredentialsProvider.java:92)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getCredentials(SystemDefaultCredentialsProvider.java:113)
> at com.openshift.internal.restclient.authorization.OpenShiftCredentialsProvider.getCredentials(OpenShiftCredentialsProvider.java:69)
> at org.apache.http.impl.client.AuthenticationStrategyImpl.select(AuthenticationStrategyImpl.java:184)
> at org.apache.http.impl.client.TargetAuthenticationStrategy.select(TargetAuthenticationStrategy.java:43)
> at org.apache.http.impl.auth.HttpAuthenticator.handleAuthChallenge(HttpAuthenticator.java:154)
> at org.apache.http.impl.execchain.MainClientExec.needAuthentication(MainClientExec.java:557)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:275)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:99)
> at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:504)
> at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:236)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226)
> at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:445)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:389)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:376)
> at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:59)
> at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:93)
> at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months