[JBoss JIRA] (JBIDE-23094) Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata when image is in the Docker daemon
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23094?page=com.atlassian.jira.plugi... ]
Marián Labuda resolved JBIDE-23094.
-----------------------------------
Resolution: Cannot Reproduce Bug
This was supposed to be follow up on JBIDE-22916, but there was only one use case when the issue occurred and thus there is no need to have follow up on non-existing issue. Marking as cannot reproduce
> Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata when image is in the Docker daemon
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23094
> URL: https://issues.jboss.org/browse/JBIDE-23094
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Jeff MAURY
> Fix For: 4.4.2.AM1
>
>
> ASSERT: Have an OpenShift 3 connection with a project.
> ASSERT: Have a docker connection in docker explorer.
> EXEC: Select a context menu item Deploy Docker Image in context menu of a project.
> EXEC: Paste docker image name e.g. docker.io/openshift/hello-openshift (the image must be available in the Docker daemon).
> EXEC: Proceed to next wizard page(s).
> RESULT: There are no prefetched and processed metadata of the image.
> EXPECTED RESULT: Metadata are correctly processed and shown.
> Description
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23094) Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata when image is in the Docker daemon
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23094?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-23094:
----------------------------------
Description:
ASSERT: Have an OpenShift 3 connection with a project.
ASSERT: Have a docker connection in docker explorer.
EXEC: Select a context menu item Deploy Docker Image in context menu of a project.
EXEC: Browse docker image name e.g. docker.io/openshift/hello-openshift (the image must be available in the Docker daemon).
EXEC: Proceed to next wizard page(s).
RESULT: There are no prefetched and processed metadata of the image.
EXPECTED RESULT: Metadata are correctly processed and shown.
Description
was:
ASSERT: Have an OpenShift 3 connection with a project.
ASSERT: Have a docker connection in docker explorer.
EXEC: Select a context menu item Deploy Docker Image in context menu of a project.
EXEC: Paste docker image name e.g. docker.io/openshift/hello-openshift (the image must be available in the Docker daemon).
EXEC: Proceed to next wizard page(s).
RESULT: There are no prefetched and processed metadata of the image.
EXPECTED RESULT: Metadata are correctly processed and shown.
Description
> Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata when image is in the Docker daemon
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23094
> URL: https://issues.jboss.org/browse/JBIDE-23094
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Jeff MAURY
> Fix For: 4.4.2.AM1
>
>
> ASSERT: Have an OpenShift 3 connection with a project.
> ASSERT: Have a docker connection in docker explorer.
> EXEC: Select a context menu item Deploy Docker Image in context menu of a project.
> EXEC: Browse docker image name e.g. docker.io/openshift/hello-openshift (the image must be available in the Docker daemon).
> EXEC: Proceed to next wizard page(s).
> RESULT: There are no prefetched and processed metadata of the image.
> EXPECTED RESULT: Metadata are correctly processed and shown.
> Description
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22916) Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22916?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22916:
---------------------------------------
Selection of an image by browsing images in a docker connection works. Also selection of a searched image works. Also autocompleted image in the text widget works. Only pasted image name does not work.
> Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-22916
> URL: https://issues.jboss.org/browse/JBIDE-22916
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.1.Final
>
>
> When I am trying to deploy a docker image from context menu of a project in OpenShift explorer view and I paste image name (e.g. docker.io/openshift/hello-openshift), image metadata are not fetched/processed and thus there are no environment variables in the wizard and routing (routing wizard page is empty and cannot finish dialog - requires manual entry). This force user to enter the details manually, otherwise he would get deployed not working pod. This is happening only in case when user provide an image without any tag and thus there is/supposed to be assumed tag "latest".
> You can observe that it works when using tag v1.2.1. Difference between images with tag v1.2.1 and latest is that v1.2.1 contains exposed ports also in container config, not just in general config of the image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23041) Restore Defaults preferences causes exception
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23041?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-23041.
------------------------------------
verified in Devstudio 10.1.0.GA-v20160901-1218-B5920
> Restore Defaults preferences causes exception
> ---------------------------------------------
>
> Key: JBIDE-23041
> URL: https://issues.jboss.org/browse/JBIDE-23041
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.4.1.AM3
> Reporter: Rastislav Wagner
> Assignee: Ilya Buziuk
> Fix For: 4.4.1.Final
>
>
> {code}
> java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Boolean
> at org.jboss.tools.vpe.preview.editor.VpvEditor$5.propertyChange(VpvEditor.java:328)
> at org.eclipse.ui.preferences.ScopedPreferenceStore$3.run(ScopedPreferenceStore.java:350)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.preferences.ScopedPreferenceStore.firePropertyChangeEvent(ScopedPreferenceStore.java:346)
> at org.eclipse.ui.preferences.ScopedPreferenceStore.setToDefault(ScopedPreferenceStore.java:543)
> at org.eclipse.jface.preference.FieldEditor.store(FieldEditor.java:674)
> at org.eclipse.jface.preference.FieldEditorPreferencePage.performOk(FieldEditorPreferencePage.java:344)
> at org.jboss.tools.vpe.editor.preferences.VpePreferencesPage.performOk(VpePreferencesPage.java:215)
> at org.jboss.tools.common.model.ui.preferences.TabbedPreferencesPage.performOk(TabbedPreferencesPage.java:161)
> at org.eclipse.jface.preference.PreferenceDialog$8.run(PreferenceDialog.java:905)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:889)
> at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:409)
> at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.okPressed(WorkbenchPreferenceDialog.java:168)
> at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:230)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211)
> at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:63)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22963) NPE when creating a html5 project
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22963?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-22963.
------------------------------------
verified in Devstudio 10.1.0.GA-v20160901-1218-B5920
> NPE when creating a html5 project
> ---------------------------------
>
> Key: JBIDE-22963
> URL: https://issues.jboss.org/browse/JBIDE-22963
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.4.1.Final
>
>
> I get this NPE when I create the HTML5 project from Central:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.lookupHibernateVersion(JPAPostInstallFasetListener.java:222)
> at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.buildConsoleConfiguration(JPAPostInstallFasetListener.java:182)
> at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.handleEvent(JPAPostInstallFasetListener.java:79)
> at org.eclipse.wst.common.project.facet.core.events.internal.DelayedClassLoadingListener.handleEvent(DelayedClassLoadingListener.java:62)
> at org.eclipse.wst.common.project.facet.core.events.internal.ProjectListenerRegistry.notifyListeners(ProjectListenerRegistry.java:76)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1327)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:454)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configureFacets(JpaProjectConfigurator.java:152)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:108)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:501)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:494)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:281)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:168)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:136)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects0(ProjectConfigurationManager.java:830)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:760)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects(ProjectConfigurationManager.java:758)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4$1.call(ArchetypeExamplesWizardPage.java:382)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4$1.call(ArchetypeExamplesWizardPage.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4.run(ArchetypeExamplesWizardPage.java:377)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$5.run(ArchetypeExamplesWizardPage.java:419)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> {code}
> I was using devstudio-10.1.0.AM3-v20160808-1833-B5724-installer-standalone.jar
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22909) JavaModelException below FileSet.checkType (thrown in JavaElement.newNotPresentException)
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22909?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22909.
---------------------------------
> JavaModelException below FileSet.checkType (thrown in JavaElement.newNotPresentException)
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22909
> URL: https://issues.jboss.org/browse/JBIDE-22909
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.1.AM3
>
>
> The following problem was reported via the automated error reporting:
> Message: IntermediateMessageHandler [in WsRemoteEndpointImplBase$IntermediateMessageHandler.class [in org.apache.tomcat.websocket [in D:\sts-bundle\apache-tomcat-8.0.30\lib\tomcat-websocket.jar]]] does not exist
> {noformat}
> org.eclipse.jdt.core.JavaModelException: IntermediateMessageHandler [in WsRemoteEndpointImplBase$IntermediateMessageHandler.class [in org.apache.tomcat.websocket [in D:\sts-bundle\apache-tomcat-8.0.30\lib\tomcat-websocket.jar]]] does not exist
> at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:556)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:590)
> at org.eclipse.jdt.internal.core.BinaryType.getElementInfo(BinaryType.java:287)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
> at org.eclipse.jdt.internal.core.BinaryType.isAnnotation(BinaryType.java:738)
> at org.jboss.tools.jsf.jsf2.bean.scanner.FileSet.checkType(FileSet.java:80)
> at org.jboss.tools.jsf.jsf2.bean.scanner.FileSet.add(FileSet.java:50)
> at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.buildJars(JSF2ProjectBuilder.java:242)
> at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.build(JSF2ProjectBuilder.java:143)
> at org.jboss.tools.jst.web.kb.internal.KbBuilder.buildExtensionModels(KbBuilder.java:216)
> at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:134)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160503-1608 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 |
> | org.eclipse.jdt.core | 3.11.0.xx-201604081629-e45 | 3.12.0.v20160516-2131 |
> | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 |
> | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.11.0.v20160505-1301 |
> | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.500.v201605120129 |
> | org.jboss.tools.common.el.core | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.common.model | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.jsf | 3.7.1.Final-v20160330-2256-B84 | 3.8.1.v20160607-2131 |
> | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.8.1.v20160607-2115 |
> Operating Systems:
> | Linux | 3.2.0 | 4.6.4.fc23 |
> | MacOSX | 10.10.5 | 10.11.6 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/56fa9212e4b08ccb7b...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23094) Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata when image is in the Docker daemon
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23094?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23094:
-------------------------------
Description:
ASSERT: Have an OpenShift 3 connection with a project.
ASSERT: Have a docker connection in docker explorer.
EXEC: Select a context menu item Deploy Docker Image in context menu of a project.
EXEC: Paste docker image name e.g. docker.io/openshift/hello-openshift (the image must be available in the Docker daemon).
EXEC: Proceed to next wizard page(s).
RESULT: There are no prefetched and processed metadata of the image.
EXPECTED RESULT: Metadata are correctly processed and shown.
Description
> Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata when image is in the Docker daemon
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23094
> URL: https://issues.jboss.org/browse/JBIDE-23094
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Jeff MAURY
> Fix For: 4.4.2.AM1
>
>
> ASSERT: Have an OpenShift 3 connection with a project.
> ASSERT: Have a docker connection in docker explorer.
> EXEC: Select a context menu item Deploy Docker Image in context menu of a project.
> EXEC: Paste docker image name e.g. docker.io/openshift/hello-openshift (the image must be available in the Docker daemon).
> EXEC: Proceed to next wizard page(s).
> RESULT: There are no prefetched and processed metadata of the image.
> EXPECTED RESULT: Metadata are correctly processed and shown.
> Description
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months