[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:
-------------------------------------
Sprint: devex #123 November 2016, devex #140 November 2017 (was: devex #123 November 2016)
> 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
>
>
> 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)
6 years, 8 months
[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:
------------------------------------------
[~adietish] agree
> 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
>
>
> 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)
6 years, 8 months
[JBoss JIRA] (JBIDE-25172) CDK 3.2+ adapter started successfully but there is no project under OS 3 Connection
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25172?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-25172.
---------------------------------
Verified on devstudio 11.1.0.GA-v20171026-1022-B1486.
Because of changes in underlying product - CDK, steps must be adjusted. Now, one cannot have set named profile only (must call setup-cdk first, then it is possible to call setup-cdk --profile Name). After those changes, Everything works as expected. Closing.
> CDK 3.2+ adapter started successfully but there is no project under OS 3 Connection
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-25172
> URL: https://issues.jboss.org/browse/JBIDE-25172
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.1.AM3
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Fix For: 4.5.1.Final
>
> Attachments: CDK3_2WrongOS3.png
>
>
> CDK 3.2+ server adapter is started sucessfully, one can log in to openshift via browser, but in IDE, OS 3 connection got wrong name (openshift-dev) and no project is attached.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (JBIDE-25291) Read Jolokia port from image configuration instead of hardcoded to default value
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25291?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-25291:
-----------------------------------------
{quote}Are these flags standard to all images?{quote}
it is standard to all images based on fabric8
{quote}I'm very concerned that the openshift server adapter design is going to be flooded with a huge number of use-case-specific crap that isn't applicable to other situations. This stuff as a whole really needs to be spec'd out. A list of all things an openshift server should be able to do, and a set of different behavior for each task need to be outlined. Then implementations can be made.
Right now it seems everything is 100% ad-hoc and it's giving me a very dirty feeling.{quote}
it is the same than for all work done with OpenShift server adapters. The Node;js and EAP images used by Red Hat are trying to define some conventions. These conventions for Jolokia seems to be coherent, the implementor ([~rhuss]) of Jolokia has worked to create the fabric8 images using Jolokia. So I think that we can take it as convention.
> Read Jolokia port from image configuration instead of hardcoded to default value
> --------------------------------------------------------------------------------
>
> Key: JBIDE-25291
> URL: https://issues.jboss.org/browse/JBIDE-25291
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jmx, openshift
> Affects Versions: 4.5.0.Final, 4.5.1.AM3
> Reporter: Aurélien Pupier
>
> see https://hub.docker.com/r/fabric8/s2i-java/ for classical use case:
> {noformat}
> AB_JOLOKIA_PORT : Port to use (Default: 8778)
> {noformat}
> might worth to also take care of all other parameters?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (JBIDE-25171) Changing value of 'Minishift profile' in CDK 3.2.+ server adapter should be reflected in Launch Configuration
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25171?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-25171.
---------------------------------
Verified on devstudio 11.1.0.-v20171026-1022-B1486.
> Changing value of 'Minishift profile' in CDK 3.2.+ server adapter should be reflected in Launch Configuration
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25171
> URL: https://issues.jboss.org/browse/JBIDE-25171
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk
> Affects Versions: 4.5.1.AM3
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.5.1.Final
>
>
> Changing value of 'Minishift profile' field should get propagated into Launch configuration of CDK 3.2+ server adapter.
> Also, if user leaves Minishift Profile field empty during filling up the wizard, and then he sets up the profile value in CDK 3.2 server adapter editor, it should be reflected in launch configuration (simply add "--profile someValue") arguments after save.
> [~rob.stryker], could you, please, take a look here? Thanks!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (JBIDE-25258) Integration Tests: Server adapter wizard and editor dont allow invalid devmode-/debug-port-key nor debug port value
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25258?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25258:
-------------------------------------
Affects Version/s: 4.5.1.AM2
(was: 4.5.0.Final)
> Integration Tests: Server adapter wizard and editor dont allow invalid devmode-/debug-port-key nor debug port value
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25258
> URL: https://issues.jboss.org/browse/JBIDE-25258
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_editor, server_adapter_wizard
> Fix For: 4.5.2.AM1
>
> Attachments: server-adapter-wizard.png, server-adater-editor.png
>
>
> In JBIDE-25108 the server adapter wizard and -editor were changed so that they would only allow valid values for
> * devmode key
> * debug port key
> * debug port value
> The editor should not allow saving if there are invalid values, the wizard would not allow one to finish it.
> !server-adater-editor.png|thumbnail!
> !server-adapter-wizard.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months
[JBoss JIRA] (JBIDE-25258) Integration Tests: Server adapter wizard and editor dont allow invalid devmode-/debug-port-key nor debug port value
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25258?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25258:
-------------------------------------
Sprint: devex #140 November 2017
> Integration Tests: Server adapter wizard and editor dont allow invalid devmode-/debug-port-key nor debug port value
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25258
> URL: https://issues.jboss.org/browse/JBIDE-25258
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_editor, server_adapter_wizard
> Fix For: 4.5.2.AM1
>
> Attachments: server-adapter-wizard.png, server-adater-editor.png
>
>
> In JBIDE-25108 the server adapter wizard and -editor were changed so that they would only allow valid values for
> * devmode key
> * debug port key
> * debug port value
> The editor should not allow saving if there are invalid values, the wizard would not allow one to finish it.
> !server-adater-editor.png|thumbnail!
> !server-adapter-wizard.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 8 months