March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24084) To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be start with admin rights

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24084?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24084: ---------------------------------- Description: One must run devstudio with admin rights to be able to start CDKv3 server adapter with hyperV vm-provider. Also, setup-cdk command must be run in cli before server adapter is started in IDE (admin rights are not required). I am not sure, if those issues are bugs or more features requests/enhancements, but we should definitely do something about it, at least document it properly. was: One must run devstudio with admin rights to be able to start CDKv3 server adapter with hyperV vm-provider. Also, setup-cdk command must be run in cli before server adapter is started in IDE (admin right are not required). I am not sure, if those issues are bugs or more features requests/enhancements, but we should definitely do something about it, at least document it properly. > To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be start with admin rights > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24084 > URL: https://issues.jboss.org/browse/JBIDE-24084 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM1 > Environment: Windows 10 Pro, x86_64 > HyperV allowed > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.4.4.AM2 > > > One must run devstudio with admin rights to be able to start CDKv3 server adapter with hyperV vm-provider. Also, setup-cdk command must be run in cli before server adapter is started in IDE (admin rights are not required). > I am not sure, if those issues are bugs or more features requests/enhancements, but we should definitely do something about it, at least document it properly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24084) To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be start with admin rights

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24084?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24084: ---------------------------------- Workaround Description: Run cli/IDE as administrator (and continue as is described in 5th step in steps to reproduce). > To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be start with admin rights > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24084 > URL: https://issues.jboss.org/browse/JBIDE-24084 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM1 > Environment: Windows 10 Pro, x86_64 > HyperV allowed > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.4.4.AM2 > > > One must run devstudio with admin rights to be able to start CDKv3 server adapter with hyperV vm-provider. Also, setup-cdk command must be run in cli before server adapter is started in IDE. > I am not sure, if those issues are bugs or more features requests/enhancements, but we should definitely do something about it, at least document it properly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24084) To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be start with admin rights

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24084?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24084: ---------------------------------- Description: One must run devstudio with admin rights to be able to start CDKv3 server adapter with hyperV vm-provider. Also, setup-cdk command must be run in cli before server adapter is started in IDE (admin right are not required). I am not sure, if those issues are bugs or more features requests/enhancements, but we should definitely do something about it, at least document it properly. was: One must run devstudio with admin rights to be able to start CDKv3 server adapter with hyperV vm-provider. Also, setup-cdk command must be run in cli before server adapter is started in IDE. I am not sure, if those issues are bugs or more features requests/enhancements, but we should definitely do something about it, at least document it properly. > To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be start with admin rights > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24084 > URL: https://issues.jboss.org/browse/JBIDE-24084 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM1 > Environment: Windows 10 Pro, x86_64 > HyperV allowed > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.4.4.AM2 > > > One must run devstudio with admin rights to be able to start CDKv3 server adapter with hyperV vm-provider. Also, setup-cdk command must be run in cli before server adapter is started in IDE (admin right are not required). > I am not sure, if those issues are bugs or more features requests/enhancements, but we should definitely do something about it, at least document it properly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23708: ------------------------------------- Labels: logs openshift_v3 properties (was: logs properties) > Pod Log: unable to get build log if build failed with error > ----------------------------------------------------------- > > Key: JBIDE-23708 > URL: https://issues.jboss.org/browse/JBIDE-23708 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Labels: logs, openshift_v3, properties > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > Attachments: cannot-get-logs-for-erroring-build.png, webconsole-logs-for-erroring-build.png > > > steps to reproduce: > # ASSERT: make sure that you have a build that failed (ex. launch a nodejs build and shut down your vpn. The build will fail because it cannot connect to the registry) > # EXEC: in Properties view: select "Builds" tab and choose your erroring build. Choose "Build Log..." in it's context menu > Result: > You're told that you cannot get the logs for an erroring build. You therefore cannot have insights on why your build failed: > !cannot-get-logs-for-erroring-build.png! > The webconsole allows you to inspect those logs: > !webconsole-logs-for-erroring-build.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24084) To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be start with admin rights

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24084?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24084: ---------------------------------- Description: One must run devstudio with admin rights to be able to start CDKv3 server adapter with hyperV vm-provider. Also, setup-cdk command must be run in cli before server adapter is started in IDE. I am not sure, if those issues are bugs or more features requests/enhancements, but we should definitely do something about it, at least document it properly. was: One must run devstudio with admin rights to be able to start CDKv3 server adapter with hyperV vm-provider. Also, setup-cdk command must be run in cli before server adapter is started in IDE. I am not sure, if those issues are bugs or more features requests/enhancements, but we should definitely do something about it, at least document it properly. Following steps to reproduce will lead to successfully started CDK3 server adapter in IDE. > To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be start with admin rights > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24084 > URL: https://issues.jboss.org/browse/JBIDE-24084 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM1 > Environment: Windows 10 Pro, x86_64 > HyperV allowed > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.4.4.AM2 > > > One must run devstudio with admin rights to be able to start CDKv3 server adapter with hyperV vm-provider. Also, setup-cdk command must be run in cli before server adapter is started in IDE. > I am not sure, if those issues are bugs or more features requests/enhancements, but we should definitely do something about it, at least document it properly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23708: ------------------------------------------ merged into jbosstools-4.4.x and cherry-picked to master. > Pod Log: unable to get build log if build failed with error > ----------------------------------------------------------- > > Key: JBIDE-23708 > URL: https://issues.jboss.org/browse/JBIDE-23708 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Labels: logs, openshift_v3, properties > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > Attachments: cannot-get-logs-for-erroring-build.png, webconsole-logs-for-erroring-build.png > > > steps to reproduce: > # ASSERT: make sure that you have a build that failed (ex. launch a nodejs build and shut down your vpn. The build will fail because it cannot connect to the registry) > # EXEC: in Properties view: select "Builds" tab and choose your erroring build. Choose "Build Log..." in it's context menu > Result: > You're told that you cannot get the logs for an erroring build. You therefore cannot have insights on why your build failed: > !cannot-get-logs-for-erroring-build.png! > The webconsole allows you to inspect those logs: > !webconsole-logs-for-erroring-build.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23708: ------------------------------------- Fix Version/s: 4.5.0.AM2 > Pod Log: unable to get build log if build failed with error > ----------------------------------------------------------- > > Key: JBIDE-23708 > URL: https://issues.jboss.org/browse/JBIDE-23708 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Labels: logs, properties > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > Attachments: cannot-get-logs-for-erroring-build.png, webconsole-logs-for-erroring-build.png > > > steps to reproduce: > # ASSERT: make sure that you have a build that failed (ex. launch a nodejs build and shut down your vpn. The build will fail because it cannot connect to the registry) > # EXEC: in Properties view: select "Builds" tab and choose your erroring build. Choose "Build Log..." in it's context menu > Result: > You're told that you cannot get the logs for an erroring build. You therefore cannot have insights on why your build failed: > !cannot-get-logs-for-erroring-build.png! > The webconsole allows you to inspect those logs: > !webconsole-logs-for-erroring-build.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23708: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.5.0.AM2) > Pod Log: unable to get build log if build failed with error > ----------------------------------------------------------- > > Key: JBIDE-23708 > URL: https://issues.jboss.org/browse/JBIDE-23708 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Labels: logs, properties > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > Attachments: cannot-get-logs-for-erroring-build.png, webconsole-logs-for-erroring-build.png > > > steps to reproduce: > # ASSERT: make sure that you have a build that failed (ex. launch a nodejs build and shut down your vpn. The build will fail because it cannot connect to the registry) > # EXEC: in Properties view: select "Builds" tab and choose your erroring build. Choose "Build Log..." in it's context menu > Result: > You're told that you cannot get the logs for an erroring build. You therefore cannot have insights on why your build failed: > !cannot-get-logs-for-erroring-build.png! > The webconsole allows you to inspect those logs: > !webconsole-logs-for-erroring-build.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24084) To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be start with admin rights

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24084?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24084: ---------------------------------- Steps to Reproduce: 1. Install cygwin's ssh + put it in the path 2. Allow hyperV and restart workstation 3. Configure virtual switch in HyperV Manager (check network adapter setup) 4. Open cli and setup minishift cdk with "minishift setup-cdk" 5. Open IDE, add new CDKv3 server adapter and start it (or you can start minishift from cli, result is the same) was: 1. Install cygwin's ssh + put it in the path 2. Allow hyperV and restart workstation 3. Configure virtual switch in HyperV Manager (check network adapter setup) 4. Open cli as admin and setup minishift cdk with "minishift setup-cdk" 5. Open IDE as admin, add new CDKv3 server adapter and start it > To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be start with admin rights > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24084 > URL: https://issues.jboss.org/browse/JBIDE-24084 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM1 > Environment: Windows 10 Pro, x86_64 > HyperV allowed > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.4.4.AM2 > > > One must run devstudio with admin rights to be able to start CDKv3 server adapter with hyperV vm-provider. Also, setup-cdk command must be run in cli before server adapter is started in IDE. > I am not sure, if those issues are bugs or more features requests/enhancements, but we should definitely do something about it, at least document it properly. > Following steps to reproduce will lead to successfully started CDK3 server adapter in IDE. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4326) When hyper-v installed virtualization detection does not work

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4326?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4326: -------------------------------- Attachment: hyperv-virtualisation-is-not-detected.png > When hyper-v installed virtualization detection does not work > ------------------------------------------------------------- > > Key: JBDS-4326 > URL: https://issues.jboss.org/browse/JBDS-4326 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.AM2 > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.4.0.AM2 > > Attachments: hyperv-virtualisation-is-not-detected.png > > > When hyper-v installed, powershell script we use to detect virtualization is enabled in bios always returns false. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2017