[JBoss JIRA] (JBDS-4493) Virtualization detection never terminates on powershell version <= 2
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4493?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4493:
--------------------------------
Story Points: 3
Sprint: devex #135 July 2017
> Virtualization detection never terminates on powershell version <= 2
> ---------------------------------------------------------------------
>
> Key: JBDS-4493
> URL: https://issues.jboss.org/browse/JBDS-4493
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 11.0.0.AM2
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 11.0.0.GA
>
>
> Follow up on the mail thread about detection not finishing on win 7.
> Namely methods from the Platform class that call powershell commands:
> - isVirtualizationEnabled
> - getHypervisorVersion
> - isHypervisorEnabled
> For some reason when called instead of erroring (since these commands dont work on older powershell) they don't terminate and block the detection.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4493) Virtualization detection never terminates on powershell version <= 2
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4493?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4493:
--------------------------------
Fix Version/s: 11.0.0.GA
> Virtualization detection never terminates on powershell version <= 2
> ---------------------------------------------------------------------
>
> Key: JBDS-4493
> URL: https://issues.jboss.org/browse/JBDS-4493
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 11.0.0.AM2
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 11.0.0.GA
>
>
> Follow up on the mail thread about detection not finishing on win 7.
> Namely methods from the Platform class that call powershell commands:
> - isVirtualizationEnabled
> - getHypervisorVersion
> - isHypervisorEnabled
> For some reason when called instead of erroring (since these commands dont work on older powershell) they don't terminate and block the detection.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4493) Virtualization detection never terminates on powershell version <= 2
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4493?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4493:
--------------------------------
Priority: Critical (was: Major)
> Virtualization detection never terminates on powershell version <= 2
> ---------------------------------------------------------------------
>
> Key: JBDS-4493
> URL: https://issues.jboss.org/browse/JBDS-4493
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 11.0.0.AM2
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 11.0.0.GA
>
>
> Follow up on the mail thread about detection not finishing on win 7.
> Namely methods from the Platform class that call powershell commands:
> - isVirtualizationEnabled
> - getHypervisorVersion
> - isHypervisorEnabled
> For some reason when called instead of erroring (since these commands dont work on older powershell) they don't terminate and block the detection.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24796) Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24796?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-24796:
----------------------------------
Attachment: cdk3_sa-manual_correct-mhome.png
> Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24796
> URL: https://issues.jboss.org/browse/JBIDE-24796
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.Final
> Environment: Fedora
> Reporter: Ondrej Dockal
> Priority: Critical
> Attachments: cdk3_sa-manual_correct-mhome.png, cdk3_sa-manual_wrong-mhome2.png
>
>
> In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See
> !cdk3_sa-manual_wrong-mhome2.png|thumbnail!
> In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder.
> Cc: [~adietish] [~rob.stryker].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24796) Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24796?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-24796:
----------------------------------
Description:
In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See
!cdk3_sa-manual_wrong-mhome2.png|thumbnail!
In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder. See
!cdk3_sa-manual_correct-mhome.png|thumbnail!
Cc: [~adietish] [~rob.stryker].
was:
In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See
!cdk3_sa-manual_wrong-mhome2.png|thumbnail!
In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder.
Cc: [~adietish] [~rob.stryker].
> Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24796
> URL: https://issues.jboss.org/browse/JBIDE-24796
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.Final
> Environment: Fedora
> Reporter: Ondrej Dockal
> Priority: Critical
> Attachments: cdk3_sa-manual_correct-mhome.png, cdk3_sa-manual_wrong-mhome2.png
>
>
> In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See
> !cdk3_sa-manual_wrong-mhome2.png|thumbnail!
> In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder. See
> !cdk3_sa-manual_correct-mhome.png|thumbnail!
> Cc: [~adietish] [~rob.stryker].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24796) Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24796?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-24796:
----------------------------------
Description:
In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See
!cdk3_sa-manual_wrong-mhome2.png|thumbnail!
In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder.
Cc: [~adietish] [~rob.stryker].
was:
In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See
!cdk3_sa-manual_wrong-mhome2.png|thumbnail!
In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses. If it is possible( from the side of binary)
Cc: [~adietish] [~rob.stryker].
> Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24796
> URL: https://issues.jboss.org/browse/JBIDE-24796
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.Final
> Environment: Fedora
> Reporter: Ondrej Dockal
> Priority: Critical
> Attachments: cdk3_sa-manual_wrong-mhome2.png
>
>
> In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See
> !cdk3_sa-manual_wrong-mhome2.png|thumbnail!
> In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder.
> Cc: [~adietish] [~rob.stryker].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24795) Add Minishift Home field to New server dialog for cdk 3
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24795?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24795:
---------------------------------------
The new related JIRA is JBIDE-24796 - the bug is that the Minishift Home field in server config is not taken into account at all.
> Add Minishift Home field to New server dialog for cdk 3
> -------------------------------------------------------
>
> Key: JBIDE-24795
> URL: https://issues.jboss.org/browse/JBIDE-24795
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.5.0.AM2
> Reporter: Martin Malina
>
> Somewhat related to JBIDE-24447 which is about allowing different minishift home set via MINISHIFT_HOME.
> When you create your cdk runtime manually, you should have a way of setting a custom Minishift home. Currently the dialog only contains the Minishift Binary field.
> So if you're using a directory other than ~/.minishift, you will have to create the cdk server first and then change this in the server editor. It would be desirable to have this field present in the New Server dialog.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months