[JBoss JIRA] (JBIDE-20568) Application wizard: Duplicate templates in different OpenShift projects are not distinguishable from each other
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20568?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20568:
-------------------------------------
Summary: Application wizard: Duplicate templates in different OpenShift projects are not distinguishable from each other (was: Duplicate templates in different OpenShift projects are not distinguishable from each other)
> Application wizard: Duplicate templates in different OpenShift projects are not distinguishable from each other
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20568
> URL: https://issues.jboss.org/browse/JBIDE-20568
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Jeff Cantrill
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: screenshot-1.png, TemplateLableWithNamespace.png
>
>
> New app from template should allow a user to pick templates form either the 'OpenShift' project or their own and they should be able to tell the difference. The attached screen show displays the same template twice but actually, one is in the openshift project and the other is in the 'hello-world'
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-20568) Application wizard: Duplicate templates in different OpenShift projects are not distinguishable from each other
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20568?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20568:
-------------------------------------
Labels: openshift_v3 (was: )
> Application wizard: Duplicate templates in different OpenShift projects are not distinguishable from each other
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20568
> URL: https://issues.jboss.org/browse/JBIDE-20568
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Jeff Cantrill
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: screenshot-1.png, TemplateLableWithNamespace.png
>
>
> New app from template should allow a user to pick templates form either the 'OpenShift' project or their own and they should be able to tell the difference. The attached screen show displays the same template twice but actually, one is in the openshift project and the other is in the 'hello-world'
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21825) Application wizard: Duplicate templates in different OpenShift projects are not distinguishable from each other
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21825?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21825:
-------------------------------------
Summary: Application wizard: Duplicate templates in different OpenShift projects are not distinguishable from each other (was: Duplicate templates in different OpenShift projects are not distinguishable from each other)
> Application wizard: Duplicate templates in different OpenShift projects are not distinguishable from each other
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21825
> URL: https://issues.jboss.org/browse/JBIDE-21825
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Jeff Cantrill
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.3.1.CR1
>
> Attachments: screenshot-1.png, TemplateLableWithNamespace.png
>
>
> New app from template should allow a user to pick templates form either the 'OpenShift' project or their own and they should be able to tell the difference. The attached screen show displays the same template twice but actually, one is in the openshift project and the other is in the 'hello-world'
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21823) Unable to re-edit Service config
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21823:
---------------------------------------
[~adietish] I believe im thinking of https://issues.jboss.org/browse/JBIDE-21665
> Unable to re-edit Service config
> --------------------------------
>
> Key: JBIDE-21823
> URL: https://issues.jboss.org/browse/JBIDE-21823
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> Once a service config has been changed, closing and reopening the config editor does not reveal the latest config, which then causes 409 error when saving subsequent changes, making it impossible to submit new changes.
> Steps to reproduce:
> - select a service in the OpenShift Explorer
> - click on the {{Edit...}} command.
> - in the JSON editor for the service config, note the resource version. Eg:
> {code}
> {
> "metadata" : {
> "name" : "jee-sample",
> "namespace" : "sample",
> "selfLink" : "/api/v1/namespaces/sample/services/jee-sample",
> "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e",
> "resourceVersion" : "38301",
> "creationTimestamp" : "2016-02-23T16:06:03Z",
> "labels" : {"app" : "jee-sample"},
> "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"}
> },
> ...
> {code}
> - make some changes and save
> - the service config version should have incremented:
> {code}
> {
> "kind" : "Service",
> "apiVersion" : "v1",
> "metadata" : {
> "name" : "jee-sample",
> "namespace" : "sample",
> "selfLink" : "/api/v1/namespaces/sample/services/jee-sample",
> "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e",
> "resourceVersion" : "38390",
> "creationTimestamp" : "2016-02-23T16:06:03Z",
> "labels" : {"app" : "jee-sample"},
> "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"}
> }
> ....
> {code}
> - close the config editor
> - re-open the config editor
> *ASSERT: the editor displays the latest config*
> *FAIL the editor displays the initial config*
> *Also, on subsequent changes, the OpenShift server responds with a {{409}} error because the new config to save is based out-dated version*
> {code}
> Could not update "[sample] Service : jee-sample.json" for project "sample" : services "jee-sample" cannot be updated: the object has been modified; please apply your changes to the latest version and try again
> Could not update resource jee-sample: {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "services \"jee-sample\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again",
> "reason": "Conflict",
> "details": {
> "name": "jee-sample",
> "kind": "services"
> },
> "code": 409
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[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 updated JBIDE-21744:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
> 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.0.Alpha1
>
>
> 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)
10 years, 1 month
[JBoss JIRA] (JBDS-3617) Cannot run vagrant after running installer
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBDS-3617?page=com.atlassian.jira.plugin.... ]
Rob Stryker updated JBDS-3617:
------------------------------
Fix Version/s: 9.1.0.CR1
> Cannot run vagrant after running installer
> ------------------------------------------
>
> Key: JBDS-3617
> URL: https://issues.jboss.org/browse/JBDS-3617
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Environment: Windows 10
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.CR1
>
> Attachments: Vagrant.png
>
>
> See attached screenshot - the same error is seen when running with the CDK configured as a runtime - or by running vagrant/vagrant.bat form the CLI after running the installer.
> Exception occurred executing command line.
> {{Cannot run program c:\DeveloperPlatform\vagrant\bin\vagrant) (in directory {{C:\DeveloperPlatform\cdk\plugins): CreateProcess error=193, %1 is not a valid Win32 application}}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3658) CDK server start times out after 900s at the first start
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3658?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov edited comment on JBDS-3658 at 3/7/16 12:19 PM:
---------------------------------------------------------------
{quote}We'll see how long it takes when the installer uses the latest Vagrantfile, then we can decide whether extending the timeout is relevant or not{quote}
+1
was (Author: akazakov):
+1
> CDK server start times out after 900s at the first start
> --------------------------------------------------------
>
> Key: JBDS-3658
> URL: https://issues.jboss.org/browse/JBDS-3658
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Reporter: Fred Bricon
> Fix For: 9.1.0.CR1
>
>
> Starting the CDK for the 1st time on my win10 laptop (5yo thinkpad t510, 8GB ram, no SSD, dual Core i7) timed out after 900s.
> We might want to double that timeout.
> This is using the installer on windows.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21825) Duplicate templates in different OpenShift projects are not distinguishable from each other
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-21825:
----------------------------------------
Summary: Duplicate templates in different OpenShift projects are not distinguishable from each other
Key: JBIDE-21825
URL: https://issues.jboss.org/browse/JBIDE-21825
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Jeff Cantrill
Assignee: Viacheslav Kabanovich
Priority: Minor
Fix For: 4.4.0.Alpha1
New app from template should allow a user to pick templates form either the 'OpenShift' project or their own and they should be able to tell the difference. The attached screen show displays the same template twice but actually, one is in the openshift project and the other is in the 'hello-world'
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month