[JBoss JIRA] (JBIDE-23368) Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-23368:
---------------------------------------
[~mlabuda]This was originally added because even though an image metadata does not indicate an image will be listening on a port, it still could be. For example, a debug port is open but I did not explicitly declare it in the dockerfile. Adding still allows you to configure a service that will expose the port. However, [~adietish] and I had a long discussion about this issue and I believe we agreed on doing one of the following:
* Remove the functionality all together to be consistent with the web ui
* Modify button desc, add text to explain the ramifications, update the table to make it obvious these ports are not exposed
I'm not certain what the right direction is other then we should probably follow the web and console as examples. You could always make the argument that a user can manually edit a service if an image does not explicitly expose ports. This seems reasonable to me.
> Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23368
> URL: https://issues.jboss.org/browse/JBIDE-23368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM3
>
>
> When deploying a docker image via Deploy Docker Wizard to an OpenShift instance, there is a wizard page with mapping of pod ports to service ports. If I add a new port mapping there, it is propagated to a created Service. But created replication controller does not contain those new mappings (results into creating pods without those ports available)
> Either way this should be fixed, to also Replication Controller should contain mapped ports, because having a service which has mapped pod ports to service ports but pods itself does not have this port exposes is useless. Or having Add... button does not make sense there, or there is no known use case where it would be useful (existing mapping could be edited but a new one would be useless).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23368) Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23368:
------------------------------------------
[~mlabuda] yes, I agree and this was my initial impression, too. This seems to be confirmed by the fact that the web-ui wont allow you to add/remove ports. Web-UI only allows you to chose the routing port.
On the ohter hand, offering this ability is giving power to the users and works as long as the users take care to expose those ports on the pod/container.
[~jeffmaury] can you reiterate the reasons that made you think that we should allow users to add/remove ports?
> Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23368
> URL: https://issues.jboss.org/browse/JBIDE-23368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM3
>
>
> When deploying a docker image via Deploy Docker Wizard to an OpenShift instance, there is a wizard page with mapping of pod ports to service ports. If I add a new port mapping there, it is propagated to a created Service. But created replication controller does not contain those new mappings (results into creating pods without those ports available)
> Either way this should be fixed, to also Replication Controller should contain mapped ports, because having a service which has mapped pod ports to service ports but pods itself does not have this port exposes is useless. Or having Add... button does not make sense there, or there is no known use case where it would be useful (existing mapping could be edited but a new one would be useless).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23465) Cannot install JBoss Tools Abridged into Eclipse Neon 1 JEE (remediation required)
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23465?page=com.atlassian.jira.plugi... ]
Lukáš Valach commented on JBIDE-23465:
--------------------------------------
Installation from [nightly update site|http://download.jboss.org/jbosstools/neon/snapshots/updates/] works fine.
http://download.jboss.org/jbosstools/neon/snapshots/updates/
> Cannot install JBoss Tools Abridged into Eclipse Neon 1 JEE (remediation required)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-23465
> URL: https://issues.jboss.org/browse/JBIDE-23465
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform, updatesite
> Affects Versions: 4.4.2.AM2
> Environment: Fedora 24
> Reporter: Lukáš Valach
> Attachments: RemediationPage.png, RemediationPageUpdate.png
>
>
> When I try to install JBoss Tools Abridged from [1| into eclipse-jee-neon-1a-linux-gtk-x86_64.tar.gz , I am shown a remediation screen.
> !RemediationPage.png|thumbnail!
> !RemediationPageUpdate.png|thumbnail!
> This is the original error message:
> {code:java}
> Your original request has been modified.
> "JavaScript Development Tools" will be ignored because a newer version is already installed.
> "Eclipse JSON Editors and Tools" will be ignored because a newer version is already installed.
> "WST JSON Core" will be ignored because a newer version is already installed.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
> Software currently installed: Code Recommenders for Java Developers 2.4.3.v20160913-0645 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160913-0645)
> Only one of the following can be installed at once:
> Code Recommenders Dependency Identification UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.coordinates.rcp 2.4.0.v20160607-1609)
> Code Recommenders Dependency Identification UI 2.4.3.v20160913-0645 (org.eclipse.recommenders.coordinates.rcp 2.4.3.v20160913-0645)
> Cannot satisfy dependency:
> From: Code Recommenders for Java Developers 2.4.3.v20160913-0645 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160913-0645)
> To: org.eclipse.recommenders.coordinates.rcp [2.4.3.v20160913-0645]
> Cannot satisfy dependency:
> From: Code Recommenders Snipmatch UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp 2.4.0.v20160607-1609)
> To: bundle org.eclipse.recommenders.coordinates.rcp [2.4.0,2.4.1)
> Cannot satisfy dependency:
> From: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
> To: org.eclipse.recommenders.snipmatch.rcp [2.4.0.v20160607-1609]
> {code}
> [1] http://download.jboss.org/jbosstools/neon/staging/updates/
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23324) Properties: should set selection to child context
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23324?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23324:
-------------------------------------
Fix Version/s: 4.4.x
(was: 4.4.2.AM3)
> Properties: should set selection to child context
> -------------------------------------------------
>
> Key: JBIDE-23324
> URL: https://issues.jboss.org/browse/JBIDE-23324
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Dmitry Bocharov
> Assignee: Dmitrii Bocharov
> Labels: openshift_v3, properties
> Fix For: 4.4.x
>
>
> (copied from https://issues.jboss.org/browse/JBIDE-23182?focusedCommentId=13306362&pag...):
> We need to update EvaluationContext in OpenShiftResourcePropertySection class for example like this:
> {code}
> table.addSelectionChangedListener(new ISelectionChangedListener() {
>
> @Override
> public void selectionChanged(SelectionChangedEvent event) {
> IHandlerService service = (IHandlerService) page.getSite().getService(IHandlerService.class);
> service.getCurrentState().addVariable(ISources.ACTIVE_CURRENT_SELECTION_NAME, table.getSelection());
>
> }
> });
> {code}
> But this made no sense, because in the example above i'm trying to update the global evaluation context from getter. Nothing just happens. So the way to solve it is to define a child evaluation context, which will be used then in Handlers too.
> I think it's a much bigger refactoring, than the one that Slava made. I think we should merge it.
> However, i might have missed some possibilities and maybe someone has more experience with updating the evaluation context. That is the thing that should be done for Properties view similarly to what i offered above, because it's a "peculiar" view.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23324) Properties: should set selection to child context
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23324?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23324:
-------------------------------------
Sprint: (was: devex #122 October 2016)
> Properties: should set selection to child context
> -------------------------------------------------
>
> Key: JBIDE-23324
> URL: https://issues.jboss.org/browse/JBIDE-23324
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Dmitry Bocharov
> Assignee: Dmitrii Bocharov
> Labels: openshift_v3, properties
> Fix For: 4.4.x
>
>
> (copied from https://issues.jboss.org/browse/JBIDE-23182?focusedCommentId=13306362&pag...):
> We need to update EvaluationContext in OpenShiftResourcePropertySection class for example like this:
> {code}
> table.addSelectionChangedListener(new ISelectionChangedListener() {
>
> @Override
> public void selectionChanged(SelectionChangedEvent event) {
> IHandlerService service = (IHandlerService) page.getSite().getService(IHandlerService.class);
> service.getCurrentState().addVariable(ISources.ACTIVE_CURRENT_SELECTION_NAME, table.getSelection());
>
> }
> });
> {code}
> But this made no sense, because in the example above i'm trying to update the global evaluation context from getter. Nothing just happens. So the way to solve it is to define a child evaluation context, which will be used then in Handlers too.
> I think it's a much bigger refactoring, than the one that Slava made. I think we should merge it.
> However, i might have missed some possibilities and maybe someone has more experience with updating the evaluation context. That is the thing that should be done for Properties view similarly to what i offered above, because it's a "peculiar" view.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-22543) Different errors when closing Central right after it was opened
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22543?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22543:
-------------------------------------
Fix Version/s: 4.4.2.Final
(was: 4.4.2.AM3)
> Different errors when closing Central right after it was opened
> ---------------------------------------------------------------
>
> Key: JBIDE-22543
> URL: https://issues.jboss.org/browse/JBIDE-22543
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.0.Final
> Environment: Devstudio 10.0.0.GA-v20160603-1025-B5510
> Reporter: Radim Hopp
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.4.2.Final
>
>
> Opening and closing central gives me two different errors:
> {noformat}
> java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86)
> at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157)
> at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor92.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84)
> ... 8 more
> Caused by: org.eclipse.core.runtime.OperationCanceledException
> at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:360)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156)
> ... 12 more
> {noformat}
> and
> {noformat:title=Failed to get connectors from RemoteProxyWizardDiscoveryStrategy}
> org.eclipse.core.runtime.CoreException: IO failure: cannot load discovery directory
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:111)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:68)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:47)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.io.IOException: Cancelled by user
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader$1.checkException(FileReader.java:337)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader$1.close(FileReader.java:287)
> at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.readResource(WebUtil.java:101)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:91)
> ... 6 more
> Caused by: org.eclipse.core.runtime.OperationCanceledException: Cancelled by user
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader$1.checkException(FileReader.java:334)
> ... 9 more
> Caused by: org.eclipse.ecf.filetransfer.UserCancelledException: Cancelled by user
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.newUserCancelledException(AbstractRetrieveFileTransfer.java:442)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.setDoneCanceled(AbstractRetrieveFileTransfer.java:472)
> at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer.cancel(HttpClientRetrieveFileTransfer.java:228)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.handleTransferEvent(FileReader.java:213)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.fireTransferReceiveDataEvent(AbstractRetrieveFileTransfer.java:390)
> at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer.fireTransferReceiveDataEvent(HttpClientRetrieveFileTransfer.java:1116)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.handleReceivedData(AbstractRetrieveFileTransfer.java:294)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:179)
> at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:74)
> ... 1 more
> {noformat}
> They do not appear every time, but pretty often.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months