[JBoss JIRA] (JBIDE-22912) Deploy Docker Wizard: Inappropriate project combo size
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22912?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-22912:
---------------------------------------
[~bdshadow] If you have updated to FC24, you have to reinstall vagrant, virtualbox and libvirt in order OpenShift to work correctly.
> Deploy Docker Wizard: Inappropriate project combo size
> ------------------------------------------------------
>
> Key: JBIDE-22912
> URL: https://issues.jboss.org/browse/JBIDE-22912
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Environment: Fedora 24, GTK 3
> Reporter: Marián Labuda
> Assignee: Snjezana Peco
> Priority: Minor
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM1
>
> Attachments: deploy-to-docker-wizard-fc23.png, project_combo.png
>
>
> In Deploy Docker Image wizard opened from context menu of a docker image is project combo stretched to left size and it does not look good.
> !project_combo.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22916) Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22916?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22916:
------------------------------------------
we should create the jira for the case where metadata is not fetched when doing "Browse"
> Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-22916
> URL: https://issues.jboss.org/browse/JBIDE-22916
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.1.Final
>
>
> When I am trying to deploy a docker image from context menu of a project in OpenShift explorer view and I paste image name (e.g. docker.io/openshift/hello-openshift), image metadata are not fetched/processed and thus there are no environment variables in the wizard and routing (routing wizard page is empty and cannot finish dialog - requires manual entry). This force user to enter the details manually, otherwise he would get deployed not working pod. This is happening only in case when user provide an image without any tag and thus there is/supposed to be assumed tag "latest".
> You can observe that it works when using tag v1.2.1. Difference between images with tag v1.2.1 and latest is that v1.2.1 contains exposed ports also in container config, not just in general config of the image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22916) Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22916?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22916:
------------------------------------------
The patch fixes the given usecase, but we have a few more usecases that still wont work:
1. Select Image using "Browse"
2. Select Image via "Paste" if the image is in the local docker daemon
> Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-22916
> URL: https://issues.jboss.org/browse/JBIDE-22916
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.1.Final
>
>
> When I am trying to deploy a docker image from context menu of a project in OpenShift explorer view and I paste image name (e.g. docker.io/openshift/hello-openshift), image metadata are not fetched/processed and thus there are no environment variables in the wizard and routing (routing wizard page is empty and cannot finish dialog - requires manual entry). This force user to enter the details manually, otherwise he would get deployed not working pod. This is happening only in case when user provide an image without any tag and thus there is/supposed to be assumed tag "latest".
> You can observe that it works when using tag v1.2.1. Difference between images with tag v1.2.1 and latest is that v1.2.1 contains exposed ports also in container config, not just in general config of the image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22992) OpenShift tools use wrong rest client bits
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22992?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22992.
---------------------------------
> OpenShift tools use wrong rest client bits
> ------------------------------------------
>
> Key: JBIDE-22992
> URL: https://issues.jboss.org/browse/JBIDE-22992
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, openshift
> Affects Versions: 4.4.1.AM3
> Environment: eclipse.buildId=10.1.0.AM3-v20160810-0441-B5735
> java.version=1.8.0_101
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product
> Reporter: Denis Golovin
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.4.1.Final
>
> Attachments: IU-unchanged-not-published.png, openshift-client-IU-new-timestamp.png, openshift-client-IU.png
>
>
> An internal error occurred during: "Loading service-manager to configure additional frameworks that CDK depends on.".{code}java.lang.NoSuchMethodError: com.openshift.restclient.ClientBuilder.withMaxRequests(I)Lcom/openshift/restclient/ClientBuilder;
> at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:53)
> at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:1)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKOpenshiftUtility.createOpenshiftConnection(CDKOpenshiftUtility.java:77)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKOpenshiftUtility.createOpenshiftConnection(CDKOpenshiftUtility.java:55)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureOpenshift(ConfigureDependentFrameworksListener.java:91)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:56)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:44)
> 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, 7 months
[JBoss JIRA] (JBIDE-22653) Scale Pod: should get warned when scaling to 0
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22653.
---------------------------------
Verified in DevStudio 10.1.0.GA build ID GA-v20160901-0833-B5918.
> Scale Pod: should get warned when scaling to 0
> ----------------------------------------------
>
> Key: JBIDE-22653
> URL: https://issues.jboss.org/browse/JBIDE-22653
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Labels: openshift_v3, scaling_pods_wizard
> Fix For: 4.4.1.Final
>
>
> The scale to... menu lets you scale to any number of replicas, but you can't go down to 0.
> The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment."
> My take is we should have the same behavior in eclipse
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBTIS-844) Update Target Platform: include m2e-wtp 1.2.2 in Mars TP
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-844?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-844:
-----------------------------
Priority: Blocker (was: Major)
> Update Target Platform: include m2e-wtp 1.2.2 in Mars TP
> --------------------------------------------------------
>
> Key: JBTIS-844
> URL: https://issues.jboss.org/browse/JBTIS-844
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.3.1.Final
> Reporter: Aurélien Pupier
> Assignee: Paul Leacu
> Priority: Blocker
>
> *Reason:* Have a fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=500197 which is blocking for [FUSETOOLS-1983] which is planned for Fuse Tooling 8.0.0
> *Project page/sources:* https://www.eclipse.org/m2e-wtp/
> *Version:* upgrade from 1.2.1 to 1.2.2
> *License and owner:* EPL, Eclipse
> *Original p2 repo:* http://download.eclipse.org/m2e-wtp/releases/mars/
> *JBoss mirror:* Leave empty
> *Include Sources:* included
> *Affected JBoss Tools components:* Fuse Tooling
> *Include in JBDS:* Yes
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> > org.eclipse.m2e.wtp.jpa.feature.feature.group [1.2.2.20160830-1241]
> > org.eclipse.m2e.wtp.feature.feature.group [1.2.2.20160830-1240]
> > org.jboss.tools.maven.jsf [1.2.2.20160830-1240]
> > org.eclipse.m2e.wtp.jsf.feature.feature.jar [1.2.2.20160830-1240]
> > org.eclipse.m2e.wtp.jpa [1.2.2.20160830-1241]
> > org.eclipse.m2e.wtp.jpa.feature.feature.jar [1.2.2.20160830-1241]
> > org.eclipse.m2e.wtp.feature.feature.jar [1.2.2.20160830-1240]
> > org.eclipse.m2e.wtp.jaxrs.feature.feature.jar [1.2.2.20160830-1240]
> > org.jboss.tools.maven.jpa [1.2.2.20160830-1241]
> > org.eclipse.m2e.wtp.overlay [1.2.2.20160830-1240]
> > org.eclipse.m2e.wtp [1.2.2.20160830-1240]
> > org.eclipse.m2e.wtp.jsf.feature.feature.group [1.2.2.20160830-1240]
> > org.eclipse.m2e.wtp.overlay.ui [1.2.2.20160830-1240]
> > org.maven.ide.eclipse.wtp [1.2.2.20160830-1240]
> > org.eclipse.m2e.wtp.jsf [1.2.2.20160830-1240]
> > org.eclipse.m2e.wtp.jaxrs [1.2.2.20160830-1240]
> > org.eclipse.m2e.wtp.jaxrs.feature.feature.group [1.2.2.20160830-1240]
> > org.jboss.tools.maven.jaxrs [1.2.2.20160830-1240]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 18 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months