[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:
------------------------------------------
According to https://docs.openshift.com/container-platform/3.3/dev_guide/managing_imag...: an Image Stream is created by manually pushing an image to the internal registry.
I debugged the workflow from the description of this JIRA. Right after pushing image to registry phase and before deploying image job, i found that the only resource created in Openshift is an Image Stream:
!FedoraImageStream.png|thumbnail!
And you can see there the address of the fedora image in internal registry:
{quote}dockerImageRepository: '172.30.115.181:5000/sample-project/fedora'{quote}
By this moment "docker images -a" still doesn't have this additional image.
Then starts [Deploy Image job and creation of resources|https://github.com/jbosstools/jbosstools-openshift/blob/57ef9c0...]. And right after creation of Deployment Config, "docker images -a" starts displaying this additional image.
About the tag: it doesn't have tag, but it displays the digest: !ImagesWithDigest.png|thumbnail!
So in my opinion this is an intended behavior, though i'm no really acquainted with this stuff. So [~jcantrill] [~xcoulon] [~adietish], please comment, what do you think about it
> 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.4.3.AM2
>
> 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.2.3#72005)
9 years, 2 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 updated JBIDE-23136:
-------------------------------------
Attachment: ImagesWithDigest.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.4.3.AM2
>
> 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.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-22999) Red Hat Central Rebranding
by Todd Mancini (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22999?page=com.atlassian.jira.plugi... ]
Todd Mancini commented on JBIDE-22999:
--------------------------------------
If not technical issues with turning on now, I'd vote to turn it on. Other than design, content is the same, right?
> Red Hat Central Rebranding
> --------------------------
>
> Key: JBIDE-22999
> URL: https://issues.jboss.org/browse/JBIDE-22999
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: James Cobb
> Fix For: 4.4.x
>
> Attachments: central-rhd-icon.png, fullIDE.png, jbosstools-central-webpage-2.0.0-revised.zip, tools_rebrand.png, tools_rebrand_r1v2.png, tools_rebrand_r1v3.png, tools_rebrand_r2v1.png
>
>
> Quoting [~james.cobb], from JBIDE-22382
> {quote}
> I've pulled in the branding fro RHD into this IDE panel.
> 1. I've opted to use colors verses an grey monotones
> 2. I've used Red Hat icons from the icon set
> Thoughts?
> {quote}
> !tools_rebrand.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 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 updated JBIDE-23136:
-------------------------------------
Attachment: FedoraImageStream.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.4.3.AM2
>
> Attachments: FedoraImageStream.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.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-22999) Red Hat Central Rebranding
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22999?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22999:
-------------------------------------
Thanks [~james.cobb]. [~tmancini], [~jeffmaury]: do you guys want to switch the new page on right away or do you prefer to wait for the next JBDS release?
> Red Hat Central Rebranding
> --------------------------
>
> Key: JBIDE-22999
> URL: https://issues.jboss.org/browse/JBIDE-22999
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: James Cobb
> Fix For: 4.4.x
>
> Attachments: central-rhd-icon.png, fullIDE.png, jbosstools-central-webpage-2.0.0-revised.zip, tools_rebrand.png, tools_rebrand_r1v2.png, tools_rebrand_r1v3.png, tools_rebrand_r2v1.png
>
>
> Quoting [~james.cobb], from JBIDE-22382
> {quote}
> I've pulled in the branding fro RHD into this IDE panel.
> 1. I've opted to use colors verses an grey monotones
> 2. I've used Red Hat icons from the icon set
> Thoughts?
> {quote}
> !tools_rebrand.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23735) Refactor CDK smoke test for integration of devstudio and CDK
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23735?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-23735:
----------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.x)
> Refactor CDK smoke test for integration of devstudio and CDK
> ------------------------------------------------------------
>
> Key: JBIDE-23735
> URL: https://issues.jboss.org/browse/JBIDE-23735
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: qa
> Affects Versions: 4.4.1.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Labels: cdk, integration_tests
> Fix For: 4.4.3.AM2
>
>
> In case that CDK server adapter is not started properly or is having some underlay issue that prevents CDK from starting, it takes too long to finish all test suites. It is desirable that test suite, even failing one, give results much faster. This could also improve CDK test pipeline.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months