[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23136:
-------------------------------------
Fix Version/s: 4.4.4.AM2
(was: 4.4.4.AM1)
> 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.4.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
[JBoss JIRA] (JBIDE-23780) Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23780?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23780:
-------------------------------------
Fix Version/s: 4.4.4.AM2
(was: 4.4.4.AM1)
> Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23780
> URL: https://issues.jboss.org/browse/JBIDE-23780
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Labels: import_wizard, openshift_v3
> Fix For: 4.4.4.AM2
>
> Attachments: clone-destination-already-exists.png, error-even-though-clone-destination-doesnt-exist.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have a folder "jboss-eap-quickstarts" in your default Eclipse git clone destination (if you didnt change your preferences, it will point to ~/git/. If you dont have it yet git clone it from https://github.com/jboss-developer/jboss-eap-quickstarts.git)
> # EXEC: create a new application using the "eap64-basic-s2i" template
> # ASSERT: the OpenShift resources for your application are created, the import wizard pops up with the following error that complains about the directory already existing:
> !clone-destination-already-exists.png!
> # EXEC: manually remove the directory (ex. in cmd-line)
> # EXEC: uncheck "Use default clone destination:"
> Result:
> The error wont go away, the wizard is still complaining even though the folder isnt in the way any more.
> !error-even-though-clone-destination-doesnt-exist.png!
> Hitting "Browse" and pointing to the same folder, that doesnt containt the folder anymore, wont help. The error persists. There'
> s no way to work around this, you have to cancel the import and start over again.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23869:
------------------------------------------
[~jeffmaury] can you please reference the upstream issue here so that we can track it via this openshift jira?
> ClassCastException with Jolokia connection
> ------------------------------------------
>
> Key: JBIDE-23869
> URL: https://issues.jboss.org/browse/JBIDE-23869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: jmx, jolokia, openshift
> Fix For: 4.4.4.AM2
>
> Attachments: image-2017-02-06-13-54-27-708.png
>
>
> !image-2017-02-06-13-54-27-708.png|thumbnail!
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23869:
-------------------------------------
Fix Version/s: 4.4.4.AM2
(was: 4.4.4.AM1)
> ClassCastException with Jolokia connection
> ------------------------------------------
>
> Key: JBIDE-23869
> URL: https://issues.jboss.org/browse/JBIDE-23869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: jmx, jolokia, openshift
> Fix For: 4.4.4.AM2
>
> Attachments: image-2017-02-06-13-54-27-708.png
>
>
> !image-2017-02-06-13-54-27-708.png|thumbnail!
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23403) As a user I need to be able to inspect the state of my EAP deployments
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23403?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23403:
------------------------------------------
[~kconner] [~rcernich] are you aware of how I'd be able to inspect my deployments (which I could when we still had the admin console in our eap images) via jmx?
> As a user I need to be able to inspect the state of my EAP deployments
> ----------------------------------------------------------------------
>
> Key: JBIDE-23403
> URL: https://issues.jboss.org/browse/JBIDE-23403
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Labels: openshift_v3, server, web_console
> Fix For: 4.4.4.AM2
>
>
> The web console for eap was disabled in the eap image that we have in OpenShift. It's therefore not possible for users to inspect the state of their deployment.
> The only there is to do such thing is to inspect jolokia informations. There is no such tooling in Eclipse yet. Furthermore the url to access those is non-obvious as one can see [here|http://developers.redhat.com/blog/2016/03/30/jolokia-jvm-monitoring-...]. I therefore suggest that we should provide help/tooling that allows users to easily access and manipulate those informations.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years