November 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-24977) central.it.weekly and smoke tests fail on most OS combos

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24977?page=com.atlassian.jira.plugi... ] Vojtech Prusa commented on JBIDE-24977: --------------------------------------- Working on it, i've had broken local env. I need update resoruces/settings.xml for latest repositories, also https://github.com/vprusa/jbosstools-integration-tests/tree/JBIDE-25063_2 > central.it.weekly and smoke tests fail on most OS combos > -------------------------------------------------------- > > Key: JBIDE-24977 > URL: https://issues.jboss.org/browse/JBIDE-24977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, integration-tests > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Assignee: Vojtech Prusa > Attachments: central.it.smoke.png, central.it.weekly.png > > > central.it.weekly and smoke tests are failing pretty much everywhere. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > !central.it.weekly.png|thumbnail! > !central.it.smoke.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25271) Prevents server adapter editor to switch connections

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25271?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25271: ------------------------------- Summary: Prevents server adapter editor to switch connections (was: Server adapter editor: cannot use new connection) > Prevents server adapter editor to switch connections > ---------------------------------------------------- > > Key: JBIDE-25271 > URL: https://issues.jboss.org/browse/JBIDE-25271 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Priority: Minor > Labels: openshift_v3, server_adapter_editor > Fix For: 4.5.x > > Attachments: eclipse-project-not-filled-out.png, image-2017-10-19-09-43-38-950.png > > > steps: > # ASSERT: make sure that you have a connection to an OpenShift instance > # ASSERT: make sure that you have an application running (ex. nodejs) > # ASSERT: make sure that you have a server adapter for it > # EXEC: delete the connection > # EXEC: restart Eclipse > # ASSERT: the editor has an empty Connection combo (no Connection selected). > !image-2017-10-19-09-43-38-950.png! > # EXEC: if you have 2 connections (ex. connection to OpenShift online at https://console.starter-us-east-2.openshift.com/): > try to select the other connection in the connection combo: > Here's the 1nd flaw: the connection combo is not selectable. You *CANNOT* choose the *OTHER* connection. > Then there's a 2nd flaw: the project is *NOT* filled out > !eclipse-project-not-filled-out.png! > # EXEC: hit "New" on the right of the "Connection:"-combo > # EXEC. create a new connection > Result: > The new connection shows up in the OpenShift Explorer but is *NOT* set in the adapter editor, the connection combo stays empty -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25306) Remove OpenShift2 plugins and features

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25306?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25306: ---------------------------------- Assignee: Nick Boldt > Remove OpenShift2 plugins and features > -------------------------------------- > > Key: JBIDE-25306 > URL: https://issues.jboss.org/browse/JBIDE-25306 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.5.2.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov resolved JBIDE-23136. -------------------------------------- Resolution: Done > Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-23136 > URL: https://issues.jboss.org/browse/JBIDE-23136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: FedoraImageStream.png, ImagesWithDigest.png, docker-tools-push-image-options.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png, pulling-by-digest.png > > > I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see: > 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB > Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411 > Steps to reproduce: > - have a project with a file named {{Dockerfile}} with the following content (1 line): > {code} > FROM fedora:latest > {code} > - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}}) > - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}. > - In the wizard, select the option to push the image to the registry (add a dummy port if needed) > - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-23136: ------------------------------------------ I'm resolving this Jira as it is not a bug. h4. Explanation When we deploy image to Openshift with pushing it to the registry, first of all an Image stream is created. See the example of the part of image stream yaml: {code:yaml} dockerImageRepository: '172.30.1.1:5000/myproject/fedora' tags: - items: - created: '2017-11-08T11:44:23Z' dockerImageReference: >- 172.30.1.1:5000/myproject/fedora@sha256:d17b578fcd97f98a849d81783cd82674e229ebcb209c04b772dc5181dbc8a0a1 generation: 1 image: >- sha256:d17b578fcd97f98a849d81783cd82674e229ebcb209c04b772dc5181dbc8a0a1 tag: my-tag-2 {code} Although tag is specified, _dockerImageReference_ field will be used to pull image during the deployment. Look at the screenshot of the events: !pulling-by-digest.png|thumbnail! When you do pull by the digest, the tag is not specified. See docker documentation here: https://docs.docker.com/engine/reference/commandline/images/ (List image digests) and here https://docs.docker.com/engine/reference/commandline/pull/#pull-an-image-.... There is nothing wrong with it. Actually, it can be "fixed" by removing _removeTag_ in the _PushImageToRegistryJob_ class: {code:java} try { this.dockerConnection.removeTag(tmpImageName); } catch (DockerException | InterruptedException e) { return new Status(IStatus.WARNING, OpenShiftCoreActivator.PLUGIN_ID, "Pushed the selected Docker image into OpenShift registry but failed to untag it afterwards", e); } {code} This "untagging" is the equivalent to choosing the following 2 option in Eclipse Docker Tooling in push image wizard: !docker-tools-push-image-options.png|thumbnail! See [the comment|https://issues.jboss.org/browse/JBIDE-23136?focusedCommentId=1332...] of [~xcoulon] above for more details. However, i don't think it's necessary to remove the "untagging" because everything works correctly, there is nothing wrong with the <none> tag for image pulled by digest and because i agree to Xavier's comment, that we need to restore the initial state. So i'm resolving this jira by now. However if you have any more questions or have different opinion of how it must work, feel free to reopen and comment. > Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-23136 > URL: https://issues.jboss.org/browse/JBIDE-23136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: FedoraImageStream.png, ImagesWithDigest.png, docker-tools-push-image-options.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png, pulling-by-digest.png > > > I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see: > 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB > Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411 > Steps to reproduce: > - have a project with a file named {{Dockerfile}} with the following content (1 line): > {code} > FROM fedora:latest > {code} > - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}}) > - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}. > - In the wizard, select the option to push the image to the registry (add a dummy port if needed) > - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23136: ------------------------------------- Attachment: docker-tools-push-image-options.png > Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-23136 > URL: https://issues.jboss.org/browse/JBIDE-23136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: FedoraImageStream.png, ImagesWithDigest.png, docker-tools-push-image-options.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png, pulling-by-digest.png > > > I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see: > 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB > Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411 > Steps to reproduce: > - have a project with a file named {{Dockerfile}} with the following content (1 line): > {code} > FROM fedora:latest > {code} > - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}}) > - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}. > - In the wizard, select the option to push the image to the registry (add a dummy port if needed) > - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23136: ------------------------------------- Attachment: pulling-by-digest.png > Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-23136 > URL: https://issues.jboss.org/browse/JBIDE-23136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png, pulling-by-digest.png > > > I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see: > 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB > Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411 > Steps to reproduce: > - have a project with a file named {{Dockerfile}} with the following content (1 line): > {code} > FROM fedora:latest > {code} > - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}}) > - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}. > - In the wizard, select the option to push the image to the registry (add a dummy port if needed) > - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25303: ------------------------------- Attachment: spring-boot-demo.zip > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM1 > > Attachments: spring-boot-demo.zip > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25387) Missing coretests bundles on stable update site

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBIDE-25387: ----------------------------------------- Summary: Missing coretests bundles on stable update site Key: JBIDE-25387 URL: https://issues.jboss.org/browse/JBIDE-25387 Project: Tools (JBoss Tools) Issue Type: Bug Components: updatesite Affects Versions: 4.5.1.Final Reporter: Andrej Podhradsky Priority: Critical Attachments: coretests.png The following update site http://download.jboss.org/jbosstools/oxygen/stable/updates/coretests/ is missing all coretests bundles. Note that the composite files define folder '4.5.1.Final' but no such folder exists. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25387) Missing coretests bundles on stable update site

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25387?page=com.atlassian.jira.plugi... ] Andrej Podhradsky updated JBIDE-25387: -------------------------------------- Fix Version/s: 4.5.1.Final > Missing coretests bundles on stable update site > ----------------------------------------------- > > Key: JBIDE-25387 > URL: https://issues.jboss.org/browse/JBIDE-25387 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.5.1.Final > Reporter: Andrej Podhradsky > Priority: Critical > Fix For: 4.5.1.Final > > Attachments: coretests.png > > > The following update site > http://download.jboss.org/jbosstools/oxygen/stable/updates/coretests/ > is missing all coretests bundles. Note that the composite files define folder '4.5.1.Final' but no such folder exists. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2017