[JBoss JIRA] (JBIDE-11072) OpenShift Express Tool: Create a way to invoke rhc-sshkey functionality which posts a newly created key-pair's public key to the user's domain.
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11072?page=com.atlassian.jira.plugi... ]
Stefan Bunciak closed JBIDE-11072.
----------------------------------
SSH Keys can be managed directly in JBDS. Verified - duplicated by JBIDE-11912.
> OpenShift Express Tool: Create a way to invoke rhc-sshkey functionality which posts a newly created key-pair's public key to the user's domain.
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11072
> URL: https://issues.jboss.org/browse/JBIDE-11072
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Beta1
> Environment: JBoss OpenShift Express Tools (on Eclipse)
> Reporter: Nam Duong
> Assignee: Andre Dietisheim
> Fix For: 4.0.x
>
>
> Since the RHC tools leverages GIT, we enable the user to create/generate ssh keys on the fly via the OpenShift Express Tool. But that newly created ssh key's public key needs to be associated to the user before it can be used. rhc-sshkey is used for that purpose on the commandline, but we don't have similar functionality in the OpenShift Express tools today. Here is what the Console should include:
> {quote}
> Usage: rhc sshkey (<command> | --help) [<args>]
> Manage multiple keys for the registered rhcloud user.
> List of commands
> list Display all the SSH keys for the user account
> add Add SSH key to the user account
> update Update SSH key for the user account
> remove Remove SSH key from the user account
> List of arguments
> -l|--rhlogin rhlogin Red Hat login (RHN or OpenShift login with OpenShift Express access) (Default: nduong+mac(a)redhat.com)
> -p|--password password RHLogin password (optional, will prompt)
> -i|--identifier key-name User-specified identifier for the key
> -k|--ssh key-filepath SSH public key filepath
> -d|--debug Print Debug info
> -h|--help Show Usage info
> --config path Path of alternate config file
> --timeout # Timeout, in seconds, for connection
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13892) Warn users before embedding switchyard into non JBoss application
by Stefan Bunciak (JIRA)
Stefan Bunciak created JBIDE-13892:
--------------------------------------
Summary: Warn users before embedding switchyard into non JBoss application
Key: JBIDE-13892
URL: https://issues.jboss.org/browse/JBIDE-13892
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.1.0.Alpha1
Reporter: Stefan Bunciak
Assignee: Andre Dietisheim
Fix For: 4.1.0.Beta1
SwitchYard can be embedded only into JBoss application, so we could warn users with some error dialog to prevent following exception from PaaS:
{code}
com.openshift.client.OpenShiftEndpointException: Could not request https://openshift.redhat.com/broker/rest/domains/pipistiks/applications/n...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. SwitchYard is only supported for JBoss AS/EAP
"
at com.openshift.internal.client.RestService.request(RestService.java:103)
at com.openshift.internal.client.RestService.request(RestService.java:91)
at com.openshift.internal.client.RestService.request(RestService.java:76)
at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137)
at com.openshift.internal.client.ApplicationResource$AddEmbeddedCartridgeRequest.execute(ApplicationResource.java:926)
at com.openshift.internal.client.ApplicationResource.addEmbeddableCartridge(ApplicationResource.java:353)
at com.openshift.internal.client.ApplicationResource.addEmbeddableCartridges(ApplicationResource.java:371)
at org.jboss.tools.openshift.express.internal.ui.job.EmbedCartridgesJob.addEmbeddedCartridges(EmbedCartridgesJob.java:102)
at org.jboss.tools.openshift.express.internal.ui.job.EmbedCartridgesJob.doRun(EmbedCartridgesJob.java:64)
at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:35)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: com.openshift.internal.client.httpclient.HttpClientException: {"data":null,"errors":{},"messages":[{"exit_code":109,"field":"cartridge","severity":"error","text":"Invalid cartridge. SwitchYard is only supported for JBoss AS/EAP\n"}],"status":"unprocessable_entity","supported_api_versions":[1.0,1.1,1.2,1.3],"type":null,"version":"1.0"}
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:189)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:161)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:128)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:124)
at com.openshift.internal.client.RestService.request(RestService.java:141)
at com.openshift.internal.client.RestService.request(RestService.java:97)
... 10 more
Caused by: java.io.IOException: Server returned HTTP response code: 422 for URL: https://openshift.redhat.com/broker/rest/domains/pipistiks/applications/n...
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:156)
... 14 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBDS-2505) JBDS 6.0.1 is based on Juno SR0 instead of SR2
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2505?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-2505:
-------------------------------------
[~maxandersen] I think this is resolved, let's wait for [~nickboldt] to resolve this JIRA.
Yes, I know I can check the Eclipse About box, too.
AFAICS, JBDS 6.0.0.CR1b B361 is fine in this respect.
What is also interesting is that while the org.eclipse.platform feature stayed at 4.2.1, the plugin version is 4.2.2.
> JBDS 6.0.1 is based on Juno SR0 instead of SR2
> ----------------------------------------------
>
> Key: JBDS-2505
> URL: https://issues.jboss.org/browse/JBDS-2505
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 6.0.1.GA
> Environment: JBDS 6.0.1.CR1a B354
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-b
> Fix For: 6.0.1.GA
>
>
> JBDS 6.0.1.CR1a B354 is based on Eclipse Juno SR0, but should be Juno SR2.
> I know about the recent issue where TP wasn't updated to 4.22.2, so I would expect something 4.22.1 (still Juno SR2). But in fact it is SR0.
> My assumption is that while JBDS BYOE can be installed on the minimal version of Eclipse, the JBDS installer should contain the maximum TP. I hope I'm not wrong here.
> Now I also checked the previous build - JBDS 6.0.1.CR1 B338 and that is based on Eclipse Juno 4.2.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-12219) Seam project cannot be properly removed from server
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12219?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-12219:
--------------------------------
Fix Version/s: 4.1.0.Final
(was: LATER)
> Seam project cannot be properly removed from server
> ---------------------------------------------------
>
> Key: JBIDE-12219
> URL: https://issues.jboss.org/browse/JBIDE-12219
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 3.3.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.0.Final
>
>
> When you create a Seam 2.2 EAR project and deploy it to EAP 5.1.2 it cannot be properly removed - if you select both the ear and the -ds.xml in the server view and press Delete, they will be first both undeployed, but right after that the ear will be deployed again and will fail to do so without the datasource.
> So the main problem is that even after removing everything from the server, the ear project somehow is still there in the deploy directory.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-12219) Seam project cannot be properly removed from server
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12219?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-12219:
-------------------------------------
this has been pushed to wtp 3.5 master
> Seam project cannot be properly removed from server
> ---------------------------------------------------
>
> Key: JBIDE-12219
> URL: https://issues.jboss.org/browse/JBIDE-12219
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 3.3.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.0.Final
>
>
> When you create a Seam 2.2 EAR project and deploy it to EAP 5.1.2 it cannot be properly removed - if you select both the ear and the -ds.xml in the server view and press Delete, they will be first both undeployed, but right after that the ear will be deployed again and will fail to do so without the datasource.
> So the main problem is that even after removing everything from the server, the ear project somehow is still there in the deploy directory.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBDS-2505) JBDS 6.0.1 is based on Juno SR0 instead of SR2
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-2505?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-2505:
--------------------------------------
[~maxandersen] I think [~nickboldt] fixed TP versions in CI job, so it should be OK.
> And yes seems weird if eclipse.org forgot to punt their eclipse feature - they normally do that afaik.
That's not exactly how they work. They only change versions of bundles that actually have changed. So no change in org.eclipse.platform since SR1 makes them re-use this bundle instead of creating a new one.
We'll do the same one day ;)
> JBDS 6.0.1 is based on Juno SR0 instead of SR2
> ----------------------------------------------
>
> Key: JBDS-2505
> URL: https://issues.jboss.org/browse/JBDS-2505
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 6.0.1.GA
> Environment: JBDS 6.0.1.CR1a B354
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-b
> Fix For: 6.0.1.GA
>
>
> JBDS 6.0.1.CR1a B354 is based on Eclipse Juno SR0, but should be Juno SR2.
> I know about the recent issue where TP wasn't updated to 4.22.2, so I would expect something 4.22.1 (still Juno SR2). But in fact it is SR0.
> My assumption is that while JBDS BYOE can be installed on the minimal version of Eclipse, the JBDS installer should contain the maximum TP. I hope I'm not wrong here.
> Now I also checked the previous build - JBDS 6.0.1.CR1 B338 and that is based on Eclipse Juno 4.2.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBDS-2505) JBDS 6.0.1 is based on Juno SR0 instead of SR2
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2505?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2505:
-------------------------------------------
Nick - is this resolved (QE to verify) or not (dev need to finish work) ?
Martin - you can check plugin versions in Eclipse about box'es too.
And yes seems weird if eclipse.org forgot to punt their eclipse feature - they normally do that afaik.
> JBDS 6.0.1 is based on Juno SR0 instead of SR2
> ----------------------------------------------
>
> Key: JBDS-2505
> URL: https://issues.jboss.org/browse/JBDS-2505
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 6.0.1.GA
> Environment: JBDS 6.0.1.CR1a B354
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-b
> Fix For: 6.0.1.GA
>
>
> JBDS 6.0.1.CR1a B354 is based on Eclipse Juno SR0, but should be Juno SR2.
> I know about the recent issue where TP wasn't updated to 4.22.2, so I would expect something 4.22.1 (still Juno SR2). But in fact it is SR0.
> My assumption is that while JBDS BYOE can be installed on the minimal version of Eclipse, the JBDS installer should contain the maximum TP. I hope I'm not wrong here.
> Now I also checked the previous build - JBDS 6.0.1.CR1 B338 and that is based on Eclipse Juno 4.2.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13631) URL for embedded cartridges is empty
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13631?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13631:
-------------------------------------------------
xiaoli <xtian(a)redhat.com> made a comment on [bug 923442|https://bugzilla.redhat.com/show_bug.cgi?id=923442]
PROD has not yet been upgraded yet, this fix has been in STG now.
> URL for embedded cartridges is empty
> ------------------------------------
>
> Key: JBIDE-13631
> URL: https://issues.jboss.org/browse/JBIDE-13631
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
> Attachments: existing-application.json, mysql-url-after-creation.png, mysql-url-at-creation.png, mysql-url-listed.png, new-user-creation-dialog.png, new-user-mongo-url-listed.png, new-user-mysql-url-listed.png, no-url.png
>
>
> Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13631) URL for embedded cartridges is empty
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13631?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13631:
-------------------------------------------------
xiaoli <xtian(a)redhat.com> made a comment on [bug 923442|https://bugzilla.redhat.com/show_bug.cgi?id=923442]
PROD has not yet been upgraded yet, this fix has been in STG now.
> URL for embedded cartridges is empty
> ------------------------------------
>
> Key: JBIDE-13631
> URL: https://issues.jboss.org/browse/JBIDE-13631
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
> Attachments: existing-application.json, mysql-url-after-creation.png, mysql-url-at-creation.png, mysql-url-listed.png, new-user-creation-dialog.png, new-user-mongo-url-listed.png, new-user-mysql-url-listed.png, no-url.png
>
>
> Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13631) URL for embedded cartridges is empty
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13631?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13631:
-------------------------------------------------
xiaoli <xtian(a)redhat.com> made a comment on [bug 923442|https://bugzilla.redhat.com/show_bug.cgi?id=923442]
PROD has not yet been upgraded yet, this fix has been in STG now.
> URL for embedded cartridges is empty
> ------------------------------------
>
> Key: JBIDE-13631
> URL: https://issues.jboss.org/browse/JBIDE-13631
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
> Attachments: existing-application.json, mysql-url-after-creation.png, mysql-url-at-creation.png, mysql-url-listed.png, new-user-creation-dialog.png, new-user-mongo-url-listed.png, new-user-mysql-url-listed.png, no-url.png
>
>
> Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years