[JBoss JIRA] (JBIDE-24373) Can't push an image to the CDK3 Docker registry
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24373?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-24373:
----------------------------------
Assignee: Jeff MAURY
> Can't push an image to the CDK3 Docker registry
> -----------------------------------------------
>
> Key: JBIDE-24373
> URL: https://issues.jboss.org/browse/JBIDE-24373
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Labels: openshift, openshift_v3
> Fix For: 4.4.4.Final
>
>
> Pushing an image to the CDK3 Docker registry is not possible. When the image is tagged, the registry port is not used thus Docker will try to contact the CDK Docker registry in port 80 causing a timeout to occur at the UI level.
> Steps to reproduce:
> # Create a Docker and OpenShift connection to CDK3 (using the server adapter or manually)
> # Edit the OpenShift connection and add http://172.30.1.1:5000 as the registry address
> # Build your own Docker image on the CDK3 Docker connection
> # Deploy that image and select Push to registry: a timeout will occur after 30s
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24373) Can't push an image to the CDK3 Docker registry
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24373:
----------------------------------
Summary: Can't push an image to the CDK3 Docker registry
Key: JBIDE-24373
URL: https://issues.jboss.org/browse/JBIDE-24373
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.4.AM3
Reporter: Jeff MAURY
Fix For: 4.4.4.Final
Pushing an image to the CDK3 Docker registry is not possible. When the image is tagged, the registry port is not used thus Docker will try to contact the CDK Docker registry in port 80 causing a timeout to occur at the UI level.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24372) Create test of devstudio installation using p2director
by Lukáš Valach (JIRA)
Lukáš Valach created JBIDE-24372:
------------------------------------
Summary: Create test of devstudio installation using p2director
Key: JBIDE-24372
URL: https://issues.jboss.org/browse/JBIDE-24372
Project: Tools (JBoss Tools)
Issue Type: Task
Components: integration-tests, qa
Affects Versions: 4.4.4.Final
Reporter: Lukáš Valach
Assignee: Lukáš Valach
Fix For: 4.4.4.Final
Create test that will install devstudio using p2director to catch problem like JBDS-4377
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23869:
-------------------------------------
https://github.com/openshift/origin/issues/13929 Opened upstream origin issue for their bad json response
> 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.Final
>
> 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)
8 years, 11 months
[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23869:
-------------------------------------
> Because that's how you get ants.
Would be funnier if we were using ANT to build the project. But we're not. So it's not funny. :|
> 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.Final
>
> 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)
8 years, 11 months
[JBoss JIRA] (JBDS-4362) Consider eliminating the devstudio EAP installer bundle?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4362?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4362:
----------------------------------
As a reminder, there's another way to install EAP 7.x from within devstudio itself, using SSO authentication to ensure the user has access to EAP 7.x:
0. Launch devstudio 10.x.
1. From the Servers view, click the link to open the 'New Server' dialog
!devstudio-install-add-servers-01.png|thumbnail!
2. Select EAP 7.x, click Next.
!devstudio-install-add-servers-02.png|thumbnail!
3. Click the 'Download and install runtime...'
!devstudio-install-add-servers-03.png|thumbnail!
4. Add your jboss.org or access.redhat.com credentials. Or sign up if you don't have credentials.
!devstudio-install-add-servers-04.png|thumbnail!
5. Once authenticated, your download will proceed.
!devstudio-install-add-servers-05.png|thumbnail!
> Consider eliminating the devstudio EAP installer bundle?
> --------------------------------------------------------
>
> Key: JBDS-4362
> URL: https://issues.jboss.org/browse/JBDS-4362
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer, integration-platform
> Affects Versions: 10.4.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.0.0.AM1
>
> Attachments: devstudio-install-add-servers-01.png, devstudio-install-add-servers-02.png, devstudio-install-add-servers-03.png, devstudio-install-add-servers-04.png, devstudio-install-add-servers-05.png
>
>
> For devstudio 11, we might want to eliminate the devstudio EAP installer.
> If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free.
> This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server.
> Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely?
> That way only the devSUITE installer would include EAP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months