[JBoss JIRA] (JBIDE-21731) Server Adapter: Error shown when image is not created/pushed yet, sould be more user friendly
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21731?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21731 at 3/3/16 7:38 AM:
------------------------------------------------------------------
[~scabanovich]
* Preloading services and projects (for the services tree) as we do now already takes quite some time. Loading the services can also easily be deferred but this would make the UI less handy, since the user would have to unfold the projects to discover the services.
* Given the substantial amount of time required to load the projects/services (for the tree) we should try to create ProjectImageStreamTags upfront but defer #createImageStreamMaps or just the deploymentMapper#refresh() (which do the actual laoding) to the time the user selects in the UI. Loading upon selection changes will slow down things but if we do this with a progress (WizardUtils#runInWizard(job) which displays the progress bar and disables all the widgets) and only when selecting for the 1st time (caching for latter reuse), this might be acceptable? I would guess so, WDYT? Alternatively we could just disable the text field for the deployment path, launch the loading in the background without progress/disabling other widgets and enable it once the value was loaded.
* Checkbox: yes, I was referring to you suggestion (any to my earlier thoughts). But I am wondering if we should display the deployment path at all which would free us from loading.
was (Author: adietish):
[~scabanovich] I guess that preloading services and projects as we do now already takes quite some time. Given that we should try to create ProjectImageStreamTags upfront but defer #createImageStreamMaps or just the deploymentMapper#refresh() to the actual selecting in the UI. Loading the services can also easily be deferred but this would make the UI less handy, since the user would have to unfold the projects to discover the services.
Loading upon selection changes will slow down things but if we do this with a progress (WizardUtils#runInWizard(job) which displays the progress bar and disables all the widgets) and only when selecting for the 1st time (caching for latter reuse), this might be acceptable? I would guess so, WDYT?
> Server Adapter: Error shown when image is not created/pushed yet, sould be more user friendly
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21731
> URL: https://issues.jboss.org/browse/JBIDE-21731
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
> Attachments: cannot_get_image.png
>
>
> When I create a new OS3 application and then I want to create a new server adapter, an image for this application has to be built and pushed to OpenShift's local image registry. If build is still running, what is often happening on internal OSE instance (it takes minutes - pushing of images), then there is an error message that loading of image failed. User without solid overview of OS3 background would not be able to figure out why it is happening, because even Image stream is shown, but the image is not there yet.
> Full error log:
> {code}
> com.openshift.restclient.OpenShiftException: Could not get resource django-example:latest in namespace image: {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "imageStreamTag \"django-example:latest\" not found",
> "reason": "NotFound",
> "details": {
> "name": "django-example:latest",
> "kind": "imageStreamTag"
> },
> "code": 404
> }
> at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:481)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:306)
> at org.jboss.tools.openshift.core.connection.Connection.getResource(Connection.java:378)
> at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.lambda$5(DeploymentResourceMapper.java:106)
> at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1540)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.getImageStreamTagsFor(DeploymentResourceMapper.java:107)
> at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.lambda$2(DeploymentResourceMapper.java:87)
> at java.util.stream.Collectors.lambda$toMap$213(Collectors.java:1321)
> at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
> at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1540)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.getAllImageStreamTags(DeploymentResourceMapper.java:85)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel$ProjectImageStreamTags.createImageStreamsMap(ServerSettingsViewModel.java:334)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel$ProjectImageStreamTags.<init>(ServerSettingsViewModel.java:327)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.lambda$1(ServerSettingsViewModel.java:279)
> at java.util.stream.Collectors.lambda$toMap$213(Collectors.java:1321)
> at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
> at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.createImageStreamTagsMap(ServerSettingsViewModel.java:277)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.loadResources(ServerSettingsViewModel.java:261)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.loadResources(ServerSettingsViewModel.java:255)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardFragment$15.run(ServerSettingsWizardFragment.java:695)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.openshift.internal.restclient.http.NotFoundException: {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "imageStreamTag \"django-example:latest\" not found",
> "reason": "NotFound",
> "details": {
> "name": "django-example:latest",
> "kind": "imageStreamTag"
> },
> "code": 404
> }
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:230)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:165)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:141)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:103)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:302)
> ... 36 more
> Caused by: java.io.FileNotFoundException: https://console.engint.openshift.com/oapi/v1/namespaces/image/imagestream...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1836)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:161)
> ... 39 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21731) Server Adapter: Error shown when image is not created/pushed yet, sould be more user friendly
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21731?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21731:
------------------------------------------
[~scabanovich] I guess that preloading services and projects as we do now already takes quite some time. Given that we should try to create ProjectImageStreamTags upfront but defer #createImageStreamMaps or just the deploymentMapper#refresh() to the actual selecting in the UI. Loading the services can also easily be deferred but this would make the UI less handy, since the user would have to unfold the projects to discover the services.
Loading upon selection changes will slow down things but if we do this with a progress (WizardUtils#runInWizard(job) which displays the progress bar and disables all the widgets) and only when selecting for the 1st time (caching for latter reuse), this might be acceptable? I would guess so, WDYT?
> Server Adapter: Error shown when image is not created/pushed yet, sould be more user friendly
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21731
> URL: https://issues.jboss.org/browse/JBIDE-21731
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
> Attachments: cannot_get_image.png
>
>
> When I create a new OS3 application and then I want to create a new server adapter, an image for this application has to be built and pushed to OpenShift's local image registry. If build is still running, what is often happening on internal OSE instance (it takes minutes - pushing of images), then there is an error message that loading of image failed. User without solid overview of OS3 background would not be able to figure out why it is happening, because even Image stream is shown, but the image is not there yet.
> Full error log:
> {code}
> com.openshift.restclient.OpenShiftException: Could not get resource django-example:latest in namespace image: {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "imageStreamTag \"django-example:latest\" not found",
> "reason": "NotFound",
> "details": {
> "name": "django-example:latest",
> "kind": "imageStreamTag"
> },
> "code": 404
> }
> at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:481)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:306)
> at org.jboss.tools.openshift.core.connection.Connection.getResource(Connection.java:378)
> at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.lambda$5(DeploymentResourceMapper.java:106)
> at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1540)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.getImageStreamTagsFor(DeploymentResourceMapper.java:107)
> at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.lambda$2(DeploymentResourceMapper.java:87)
> at java.util.stream.Collectors.lambda$toMap$213(Collectors.java:1321)
> at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
> at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1540)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.getAllImageStreamTags(DeploymentResourceMapper.java:85)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel$ProjectImageStreamTags.createImageStreamsMap(ServerSettingsViewModel.java:334)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel$ProjectImageStreamTags.<init>(ServerSettingsViewModel.java:327)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.lambda$1(ServerSettingsViewModel.java:279)
> at java.util.stream.Collectors.lambda$toMap$213(Collectors.java:1321)
> at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
> at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.createImageStreamTagsMap(ServerSettingsViewModel.java:277)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.loadResources(ServerSettingsViewModel.java:261)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.loadResources(ServerSettingsViewModel.java:255)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardFragment$15.run(ServerSettingsWizardFragment.java:695)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.openshift.internal.restclient.http.NotFoundException: {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "imageStreamTag \"django-example:latest\" not found",
> "reason": "NotFound",
> "details": {
> "name": "django-example:latest",
> "kind": "imageStreamTag"
> },
> "code": 404
> }
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:230)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:165)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:141)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:103)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:302)
> ... 36 more
> Caused by: java.io.FileNotFoundException: https://console.engint.openshift.com/oapi/v1/namespaces/image/imagestream...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1836)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:161)
> ... 39 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-2812) Unable to Install JBoss Hybrid Mobile Tools + CordovaSim from Central
by Baskar Venkatesan (JIRA)
[ https://issues.jboss.org/browse/JBDS-2812?page=com.atlassian.jira.plugin.... ]
Baskar Venkatesan commented on JBDS-2812:
-----------------------------------------
Me too
Jboss 9.0
> Unable to Install JBoss Hybrid Mobile Tools + CordovaSim from Central
> ---------------------------------------------------------------------
>
> Key: JBDS-2812
> URL: https://issues.jboss.org/browse/JBDS-2812
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: aerogear-hybrid, central
> Affects Versions: 7.1.0.Beta1
> Environment: JBDS 7.1.0.Beta1 Beta1-v20131020-0229-B441
> -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/4.1.kepler/devstudio-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/4.1.kepler/
> Reporter: Vlado Pakan
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: respin-a
> Fix For: 7.1.0.Beta1
>
> Attachments: help-check-for-updates-and-it-works.png, installerror.png, vpe.browsersim-cannot-be-in-JBDS-product-feature-and-in-Central.png
>
>
> While installing getting this error:
> !installerror.png!
> Choosing No displays error:
> {noformat}
> Problems occurred while performing installation: The following connectors are not available: JBoss Hybrid Mobile Tools + CordovaSim (Experimental) (id=org.jboss.tools.aerogear.hybrid.feature.feature.group, org.jboss.tools.vpe.cordovasim.feature.feature.group, site=http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/4.1.kep...)
> The following connectors are not available: JBoss Hybrid Mobile Tools + CordovaSim (Experimental) (id=org.jboss.tools.aerogear.hybrid.feature.feature.group, org.jboss.tools.vpe.cordovasim.feature.feature.group, site=http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/4.1.kep...)
> {noformat}
> Choosing Yes only BrowserSim will be installed no Cordova features will be installed
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21776) Cannot deploy docker image to OpenShift with manually entered details
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21776?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21776 at 3/3/16 6:00 AM:
------------------------------------------------------------------
adding link to JBIDE-21626 since according to [~xcoulon] it's is required to be able to pull the docker image here: https://github.com/jbosstools/jbosstools-openshift/pull/993/files#diff-39...
was (Author: adietish):
adding link to JBIDE-21636 since according to [~xcoulon] it's is required to be able to pull the docker image here: https://github.com/jbosstools/jbosstools-openshift/pull/993/files#diff-39...
> Cannot deploy docker image to OpenShift with manually entered details
> ---------------------------------------------------------------------
>
> Key: JBIDE-21776
> URL: https://issues.jboss.org/browse/JBIDE-21776
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Priority: Critical
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: manually_filled.png, Screenshot 2016-03-03 11.14.38.png, selected_image.png
>
>
> When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one).
> There is no error in error log.
> Manually filled in details screenshot:
> !manually_filled.png!
> Automatically filled details via selecting a specific image screenshot:
> !selected_image.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21776) Cannot deploy docker image to OpenShift with manually entered details
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21776?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21776:
------------------------------------------
adding link to JBIDE-21636 since according to [~xcoulon] it's is required to be able to pull the docker image here: https://github.com/jbosstools/jbosstools-openshift/pull/993/files#diff-39...
> Cannot deploy docker image to OpenShift with manually entered details
> ---------------------------------------------------------------------
>
> Key: JBIDE-21776
> URL: https://issues.jboss.org/browse/JBIDE-21776
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Priority: Critical
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: manually_filled.png, Screenshot 2016-03-03 11.14.38.png, selected_image.png
>
>
> When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one).
> There is no error in error log.
> Manually filled in details screenshot:
> !manually_filled.png!
> Automatically filled details via selecting a specific image screenshot:
> !selected_image.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21776) Cannot deploy docker image to OpenShift with manually entered details
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21776?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21776:
------------------------------------------
[~xcoulon][~jcantrill][~fbricon] I'll review the code and let you test it. I have so many patches to review that I barely manage to advance on my own topics. Ok?
> Cannot deploy docker image to OpenShift with manually entered details
> ---------------------------------------------------------------------
>
> Key: JBIDE-21776
> URL: https://issues.jboss.org/browse/JBIDE-21776
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Priority: Critical
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: manually_filled.png, Screenshot 2016-03-03 11.14.38.png, selected_image.png
>
>
> When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one).
> There is no error in error log.
> Manually filled in details screenshot:
> !manually_filled.png!
> Automatically filled details via selecting a specific image screenshot:
> !selected_image.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21802) Content assist for image names in "Deploy Docker Image" wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21802?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21802:
-------------------------------------
Fix Version/s: 4.3.1.CR1
> Content assist for image names in "Deploy Docker Image" wizard
> ---------------------------------------------------------------
>
> Key: JBIDE-21802
> URL: https://issues.jboss.org/browse/JBIDE-21802
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.3.1.CR1
>
>
> The {{Image Name}} field could be enhanced with content assist based on the list of image names+tags retrieved from the selected Docker connection.
> If the user inputs a name that does not match the list, a warning on the page would inform him/her that a remote call to the registry would be performed upon page completion, ie, when clicking on the {{Next}} button.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21776) Cannot deploy docker image to OpenShift with manually entered details
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21776?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-21776:
----------------------------------
Attachment: Screenshot 2016-03-03 11.14.38.png
[~fbricon], [~jcantrill]: I just pushed an update of the PR which checks if the given image exists on the selected Docker daemon's cache or on Docker Hub *when the clicks on {{Next}}*, in order to keep the as-you-type validation as smooth as possible (the image name is only validated against a regex). The attached screenshot shows the confirmation message that appears if the user selected an image that needs to be pulled.
This PR does not go further than this, so we should synchronize with [~jcantrill]'s work to see how the OpenShift client can pull the image metadata before displaying the next page.
> Cannot deploy docker image to OpenShift with manually entered details
> ---------------------------------------------------------------------
>
> Key: JBIDE-21776
> URL: https://issues.jboss.org/browse/JBIDE-21776
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Priority: Critical
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: manually_filled.png, Screenshot 2016-03-03 11.14.38.png, selected_image.png
>
>
> When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one).
> There is no error in error log.
> Manually filled in details screenshot:
> !manually_filled.png!
> Automatically filled details via selecting a specific image screenshot:
> !selected_image.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21805) Delete of OpenShift application via server adapter is disabled
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21805?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21805:
------------------------------------------
@Viachesla any idea when this got broken? This used to work.
> Delete of OpenShift application via server adapter is disabled
> --------------------------------------------------------------
>
> Key: JBIDE-21805
> URL: https://issues.jboss.org/browse/JBIDE-21805
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v2
> Fix For: 4.4.0.Alpha1
>
> Attachments: video.ogg-1.ogv
>
>
> Earlier it was possible to delete an OpenShift application via context menu of a server adapter "OpenShift" - "Delete application(s)...". While fixing JBIDE-21563, binding was commented out and some changes were done. Currently the context menu item is disabled so it is not possible to delete application via context menu item.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21813) Delete of OpenShift application via server adapter is disabled
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-21813:
----------------------------------------
Summary: Delete of OpenShift application via server adapter is disabled
Key: JBIDE-21813
URL: https://issues.jboss.org/browse/JBIDE-21813
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Assignee: Viacheslav Kabanovich
Fix For: 4.4.0.Alpha1
Earlier it was possible to delete an OpenShift application via context menu of a server adapter "OpenShift" - "Delete application(s)...". While fixing JBIDE-21563, binding was commented out and some changes were done. Currently the context menu item is disabled so it is not possible to delete application via context menu item.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month