[JBoss JIRA] (JBIDE-24438) Server adapter: JMX connection is not working for OpenShift instance
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24438?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24438:
-------------------------------------
Fix Version/s: 4.5.0.AM2
(was: 4.5.0.AM1)
> Server adapter: JMX connection is not working for OpenShift instance
> ---------------------------------------------------------------------
>
> Key: JBIDE-24438
> URL: https://issues.jboss.org/browse/JBIDE-24438
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Labels: jmx, jolokia, openshift_v3, server_adapter
> Fix For: 4.5.0.AM2
>
> Attachments: JMXForOpenSHiftWithoutPortNotWorking.mp4, ManualJMXConnectionWithoutPortWorking.mp4
>
>
> such as open.paas.redhat.com
> {noformat}
> java.io.IOException: org.jolokia.client.exception.J4pTimeoutException: Read timeout while request https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113)
> 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)
> Caused by: org.jolokia.client.exception.J4pTimeoutException: Read timeout while request https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out
> at org.jolokia.client.J4pClient.mapException(J4pClient.java:330)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:198)
> 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:311)
> ... 4 more
> Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:150)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:190)
> ... 7 more
> Caused by: java.net.SocketTimeoutException: connect timed out
> at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
> at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
> at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
> at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at sun.security.ssl.SSLSocketImpl.connect(Unknown Source)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337)
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141)
> ... 18 more
> {noformat}
> we can notice that the url used is https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...
> It should not contain the port 8443
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4442) Central page is not working
by Josef Kopriva (JIRA)
Josef Kopriva created JBDS-4442:
-----------------------------------
Summary: Central page is not working
Key: JBDS-4442
URL: https://issues.jboss.org/browse/JBDS-4442
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Enhancement
Components: central
Affects Versions: 11.0.0.AM1
Environment: Fedora 26 Alpha
Red Hat JBoss Developer Studio
Version: 11.0.0.AM1
Build id: AM1-v20170606-1759-B247
Build date: 20170606-1759
Reporter: Josef Kopriva
After fresh installation of F26 and Devstudio central shows error message
{code:java}
org.eclipse.swt.SWTException: An exception was raised in JavaScript
at org.eclipse.swt.browser.WebKit$Webkit2JavascriptEvaluator.evaluate(WebKit.java:1273)
at org.eclipse.swt.browser.WebKit.evaluate(WebKit.java:1324)
at org.eclipse.swt.browser.WebBrowser.evaluate(WebBrowser.java:409)
at org.eclipse.swt.browser.Browser.evaluate(Browser.java:663)
at org.eclipse.swt.browser.Browser.evaluate(Browser.java:610)
at org.jboss.tools.central.internal.browser.VersionedBrowser.<init>(VersionedBrowser.java:51)
at org.jboss.tools.central.editors.GettingStartedHtmlPage.createBrowserSection(GettingStartedHtmlPage.java:188)
at org.jboss.tools.central.editors.GettingStartedHtmlPage.createFormContent(GettingStartedHtmlPage.java:175)
at org.eclipse.ui.forms.editor.FormPage.lambda$0(FormPage.java:163)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:163)
at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:480)
at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1077)
at org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:614)
at org.eclipse.ui.forms.editor.SharedHeaderFormEditor.createPages(SharedHeaderFormEditor.java:106)
at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348)
at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:151)
at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:99)
at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:355)
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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:990)
at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:955)
at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:124)
at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:399)
at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:318)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:105)
at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:74)
at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:56)
at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:666)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:772)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:743)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:737)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:721)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$1.handleEvent(PartServiceImpl.java:104)
at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233)
at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:144)
at org.eclipse.swt.widgets.Display.syncExec(Display.java:5434)
at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212)
at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201)
at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:52)
at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60)
at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:173)
at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:620)
at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:584)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:768)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:401)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1187)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3261)
at org.eclipse.ui.internal.WorkbenchPage.access$25(WorkbenchPage.java:3176)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:3158)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3153)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3117)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3098)
at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:437)
at org.jboss.tools.central.JBossCentralActivator.getJBossCentralEditor(JBossCentralActivator.java:425)
at org.jboss.tools.central.ShowJBossCentral$2.run(ShowJBossCentral.java:110)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4492)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4105)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
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:653)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4430) EAP is not added to runtime locations
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4430?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-4430:
-----------------------------------
True, it's just sneaky and runs after EAP declares success and I did not see that.
But the mac part does hold, because the file is on a different path.
> EAP is not added to runtime locations
> -------------------------------------
>
> Key: JBDS-4430
> URL: https://issues.jboss.org/browse/JBDS-4430
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 11.0.0.AM1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 11.0.0.AM1
>
>
> The event handler responsible for adding EAP to devstudio runtime locations gets called immediately after the main installation, no matter what state devstudio is in. Hence, EAP is not usually added to runtime_locations.properties.
> On windows, runtime detection can still somehow get past this and finds EAP on its own. But on mac it doesn't. Plus the location of runtime_locations.properties file on mac is different to other platforms (needs update in the code).
> And btw. it could use some logging as well.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4430) EAP is not added to runtime locations
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4430?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-4430:
-------------------------------------
Cannot replicate, it does work for me on windows.
> EAP is not added to runtime locations
> -------------------------------------
>
> Key: JBDS-4430
> URL: https://issues.jboss.org/browse/JBDS-4430
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 11.0.0.AM1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 11.0.0.AM1
>
>
> The event handler responsible for adding EAP to devstudio runtime locations gets called immediately after the main installation, no matter what state devstudio is in. Hence, EAP is not usually added to runtime_locations.properties.
> On windows, runtime detection can still somehow get past this and finds EAP on its own. But on mac it doesn't. Plus the location of runtime_locations.properties file on mac is different to other platforms (needs update in the code).
> And btw. it could use some logging as well.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4229) If updating CDK installation error reported
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4229?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-4229:
-----------------------------------
Assignee: Denis Golovin
> If updating CDK installation error reported
> -------------------------------------------
>
> Key: JBDS-4229
> URL: https://issues.jboss.org/browse/JBDS-4229
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.2.0.GA
> Reporter: Jeff MAURY
> Assignee: Denis Golovin
> Labels: cdk, installer, ui
> Fix For: 11.0.0.AM1
>
> Attachments: nstall.log
>
>
> If you install DevSuite on a system where a previous version already exists, then an error is reported during the CDK installation but no explanation is given. User has to go to the install log and detect that the cdkv2 box is already there
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4229) If updating CDK installation error reported
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4229?page=com.atlassian.jira.plugin.... ]
Denis Golovin resolved JBDS-4229.
---------------------------------
Resolution: Out of Date
CDK 2 is discontinued, resolving as out of date.
> If updating CDK installation error reported
> -------------------------------------------
>
> Key: JBDS-4229
> URL: https://issues.jboss.org/browse/JBDS-4229
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.2.0.GA
> Reporter: Jeff MAURY
> Assignee: Denis Golovin
> Labels: cdk, installer, ui
> Fix For: 11.0.0.AM1
>
> Attachments: nstall.log
>
>
> If you install DevSuite on a system where a previous version already exists, then an error is reported during the CDK installation but no explanation is given. User has to go to the install log and detect that the cdkv2 box is already there
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4418) DevSuite 1.4 Mac fails installing CDK
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4418?page=com.atlassian.jira.plugin.... ]
Denis Golovin resolved JBDS-4418.
---------------------------------
Resolution: Duplicate Issue
[~rterzi] I linked specific issues for every item on the list.
Closing this as duplicate.
Thanks!
> DevSuite 1.4 Mac fails installing CDK
> -------------------------------------
>
> Key: JBDS-4418
> URL: https://issues.jboss.org/browse/JBDS-4418
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.4.0.GA
> Environment: Mac OS X 10.10.5, DevSuite 1.4.0 online installer.
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Fix For: 11.0.0.AM1
>
> Attachments: install.log
>
>
> The DevSuite 1.4 installer failed while installing CDK. There are two problems
> # [JBDS-3834] When an install fails and the installer can't make any progress, the flow stops. There is no prompt, no clues how to get help, find a log, etc. The user's only option is to give up and close the window.
> # [JBDS-4272] the CDK install failed. It's not clear why, attaching /Applications/DevelopmentSuite/install.log. But looking at the logs it looks like there may be permission errors. There were no prompts related to needing to run as root, or password requests, etc. If it is permissions, it just silently fails.
> # [JBDS-4441] Also, given that this is macOS, why is the installer trying to Windows admin commands (to add the user to "Hyper-V administrators")? (This should possibly be a separate bug.)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4418) DevSuite 1.4 Mac fails installing CDK
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4418?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4418:
--------------------------------
Description:
The DevSuite 1.4 installer failed while installing CDK. There are two problems
# [JBDS-3834] When an install fails and the installer can't make any progress, the flow stops. There is no prompt, no clues how to get help, find a log, etc. The user's only option is to give up and close the window.
# [JBDS-4272] the CDK install failed. It's not clear why, attaching /Applications/DevelopmentSuite/install.log. But looking at the logs it looks like there may be permission errors. There were no prompts related to needing to run as root, or password requests, etc. If it is permissions, it just silently fails.
# [JBDS-4441] Also, given that this is macOS, why is the installer trying to Windows admin commands (to add the user to "Hyper-V administrators")? (This should possibly be a separate bug.)
was:
The DevSuite 1.4 installer failed while installing CDK. There are two problems
# When an install fails and the installer can't make any progress, the flow stops. There is no prompt, no clues how to get help, find a log, etc. The user's only option is to give up and close the window.
# [JBDS-4272] the CDK install failed. It's not clear why, attaching /Applications/DevelopmentSuite/install.log. But looking at the logs it looks like there may be permission errors. There were no prompts related to needing to run as root, or password requests, etc. If it is permissions, it just silently fails.
# [JBDS-4441] Also, given that this is macOS, why is the installer trying to Windows admin commands (to add the user to "Hyper-V administrators")? (This should possibly be a separate bug.)
> DevSuite 1.4 Mac fails installing CDK
> -------------------------------------
>
> Key: JBDS-4418
> URL: https://issues.jboss.org/browse/JBDS-4418
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.4.0.GA
> Environment: Mac OS X 10.10.5, DevSuite 1.4.0 online installer.
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Fix For: 11.0.0.AM1
>
> Attachments: install.log
>
>
> The DevSuite 1.4 installer failed while installing CDK. There are two problems
> # [JBDS-3834] When an install fails and the installer can't make any progress, the flow stops. There is no prompt, no clues how to get help, find a log, etc. The user's only option is to give up and close the window.
> # [JBDS-4272] the CDK install failed. It's not clear why, attaching /Applications/DevelopmentSuite/install.log. But looking at the logs it looks like there may be permission errors. There were no prompts related to needing to run as root, or password requests, etc. If it is permissions, it just silently fails.
> # [JBDS-4441] Also, given that this is macOS, why is the installer trying to Windows admin commands (to add the user to "Hyper-V administrators")? (This should possibly be a separate bug.)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months