[JBoss JIRA] (JBIDE-23764) Scaling To: wong number of current replicas shown at times
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23764?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23764:
-------------------------------------
Labels: scaling_pods_wizard (was: )
> Scaling To: wong number of current replicas shown at times
> ----------------------------------------------------------
>
> Key: JBIDE-23764
> URL: https://issues.jboss.org/browse/JBIDE-23764
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Labels: scaling_pods_wizard
> Fix For: 4.4.3.AM2
>
> Attachments: scale-to-dialog.png
>
>
> Even though I tried very hard I unfortunately cannot provide steps to replicate this erroneous behaviour. But it happened to me here and there.
> The tooling provides a way to have a specified number of pods for a service. This is available via the context menu of a service (and other items in the tree and in the properties).
> !scale-to-dialog.png!
> The dialog that allows you to scale the number of replicas to a specific number initially shows the current number of replicas. You can then provide a specific number of replicas that you want to have, enabling the "OK" button.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23764) Scaling To: wong number of current replicas shown at times
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23764?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-23764:
----------------------------------------
Assignee: Andre Dietisheim
> Scaling To: wong number of current replicas shown at times
> ----------------------------------------------------------
>
> Key: JBIDE-23764
> URL: https://issues.jboss.org/browse/JBIDE-23764
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: scaling_pods_wizard
> Fix For: 4.4.3.AM2
>
> Attachments: scale-to-dialog.png
>
>
> Even though I tried very hard I unfortunately cannot provide steps to replicate this erroneous behaviour. But it happened to me here and there.
> The tooling provides a way to have a specified number of pods for a service. This is available via the context menu of a service (and other items in the tree and in the properties).
> !scale-to-dialog.png!
> The dialog that allows you to scale the number of replicas to a specific number initially shows the current number of replicas. You can then provide a specific number of replicas that you want to have, enabling the "OK" button.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23764) Scaling To: wong number of current replicas shown at times
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23764?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23764:
-------------------------------------
Attachment: scale-to-dialog.png
> Scaling To: wong number of current replicas shown at times
> ----------------------------------------------------------
>
> Key: JBIDE-23764
> URL: https://issues.jboss.org/browse/JBIDE-23764
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Attachments: scale-to-dialog.png
>
>
> Even though I tried very hard I unfortunately cannot provide steps to replicate this erroneous behaviour. But it happened to me here and there.
> The tooling provides a way to have a specified number of pods for a service. This is available via the context menu of a service (and other items in the tree and in the properties).
> !scale-to-dialog.png!
> The dialog that allows you to scale the number of replicas to a specific number initially shows the current number of replicas. You can then provide a specific number of replicas that you want to have, enabling the "OK" button.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23764) Scaling To: wong number of current replicas shown at times
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23764?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23764:
-------------------------------------
Attachment: scale-to-dialog.png
> Scaling To: wong number of current replicas shown at times
> ----------------------------------------------------------
>
> Key: JBIDE-23764
> URL: https://issues.jboss.org/browse/JBIDE-23764
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
>
> Even though I tried very hard I unfortunately cannot provide steps to replicate this erroneous behaviour. But it happened to me here and there.
> The tooling provides a way to have a specified number of pods for a service. This is available via the context menu of a service (and other items in the tree and in the properties).
> !scale-to-dialog.png!
> The dialog that allows you to scale the number of replicas to a specific number initially shows the current number of replicas. You can then provide a specific number of replicas that you want to have, enabling the "OK" button.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23764) Scaling To: wong number of current replicas shown at times
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23764?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23764:
-------------------------------------
Attachment: (was: scale-to-dialog.png)
> Scaling To: wong number of current replicas shown at times
> ----------------------------------------------------------
>
> Key: JBIDE-23764
> URL: https://issues.jboss.org/browse/JBIDE-23764
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
>
> Even though I tried very hard I unfortunately cannot provide steps to replicate this erroneous behaviour. But it happened to me here and there.
> The tooling provides a way to have a specified number of pods for a service. This is available via the context menu of a service (and other items in the tree and in the properties).
> !scale-to-dialog.png!
> The dialog that allows you to scale the number of replicas to a specific number initially shows the current number of replicas. You can then provide a specific number of replicas that you want to have, enabling the "OK" button.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23764) Scaling To: wong number of current replicas shown at times
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-23764:
----------------------------------------
Summary: Scaling To: wong number of current replicas shown at times
Key: JBIDE-23764
URL: https://issues.jboss.org/browse/JBIDE-23764
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.4.3.AM1
Reporter: Andre Dietisheim
Even though I tried very hard I unfortunately cannot provide steps to replicate this erroneous behaviour. But it happened to me here and there.
The tooling provides a way to have a specified number of pods for a service. This is available via the context menu of a service (and other items in the tree and in the properties).
!scale-to-dialog.png!
The dialog that allows you to scale the number of replicas to a specific number initially shows the current number of replicas. You can then provide a specific number of replicas that you want to have, enabling the "OK" button.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23641) Jboss AS Eclipse plugin freezes STS on Mac OS Sierra
by Giovanni Lovato (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23641?page=com.atlassian.jira.plugi... ]
Giovanni Lovato commented on JBIDE-23641:
-----------------------------------------
This is happening also with JBoss Developer Studio 10.2.0.GA, clean install. And only when there are projects deployed (or deployed and then removed).
> Jboss AS Eclipse plugin freezes STS on Mac OS Sierra
> ----------------------------------------------------
>
> Key: JBIDE-23641
> URL: https://issues.jboss.org/browse/JBIDE-23641
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Reporter: fede pia
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.3.AM2
>
> Attachments: eclipse.log
>
>
> When installing Jboss Tool 4.4.2 (only Jboss AS plugin) in Spring Tool Suite in a Mac, the Eclipse hangs up and needs to be killed
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23641) Jboss AS Eclipse plugin freezes STS on Mac OS Sierra
by Giovanni Lovato (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23641?page=com.atlassian.jira.plugi... ]
Giovanni Lovato commented on JBIDE-23641:
-----------------------------------------
I'm experiencing exactly the same issue. Eclipse (Neon.2) hangs on startup loading JBoss Tools (4.4.2.Final) and it must be killed, purge workspace and import projects again: it will work until the next restart. Any idea about the cause of this and possibile solution/workaround?
> Jboss AS Eclipse plugin freezes STS on Mac OS Sierra
> ----------------------------------------------------
>
> Key: JBIDE-23641
> URL: https://issues.jboss.org/browse/JBIDE-23641
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Reporter: fede pia
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.3.AM2
>
> Attachments: eclipse.log
>
>
> When installing Jboss Tool 4.4.2 (only Jboss AS plugin) in Spring Tool Suite in a Mac, the Eclipse hangs up and needs to be killed
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4252) Installer waits for failed Virtualbox installation (MacOS)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-4252?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-4252:
-----------------------------------
Description:
steps to reproduce:
# ASSERT: make sure that you have VirtualBox 5.1.x running but the app is removed from the Applications folder
# EXEC: launch installer, log in and select VirtualBox etc.
Result:
Installer fails to install VirtualBox.
!waiting-for-virtualbox-install-that-failed.png!
In the logs you see the following:
{code}
0:233: execution error: installer: Error - The installer has detected running virtual machines. Please shut down all running VirtualBox machines and then restart the installation. (1)
{code}
The installer simply states "Failed". It would be nice if the installer could provide more details on why/what failed. Sparing me from having to inspect the logs.
It simply states "Failed" for VirtualBox, the "Red Hat Container Development Kit" process is waiting for VirtualBox to get installed even though that failed.
was:
steps to reproduce:
# ASSERT: make sure that you have VirtualBox 5.1.x running but the app is removed from the Applications folder
# EXEC: launch installer, log in and select VirtualBox etc.
Result:
Installer fails to install VirtualBox.
!waiting-for-virtualbox-that-failed-to-install.png!
In the logs you see the following:
{code}
0:233: execution error: installer: Error - The installer has detected running virtual machines. Please shut down all running VirtualBox machines and then restart the installation. (1)
{code}
The installer simply states "Failed". It would be nice if the installer could provide more details on why/what failed. Sparing me from having to inspect the logs.
It simply states "Failed" for VirtualBox, the "Red Hat Container Development Kit" process is waiting for VirtualBox to get installed even though that failed.
> Installer waits for failed Virtualbox installation (MacOS)
> ----------------------------------------------------------
>
> Key: JBDS-4252
> URL: https://issues.jboss.org/browse/JBDS-4252
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.3.0.AM1
> Reporter: Andre Dietisheim
> Attachments: waiting-for-virtualbox-install-that-failed.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have VirtualBox 5.1.x running but the app is removed from the Applications folder
> # EXEC: launch installer, log in and select VirtualBox etc.
> Result:
> Installer fails to install VirtualBox.
> !waiting-for-virtualbox-install-that-failed.png!
> In the logs you see the following:
> {code}
> 0:233: execution error: installer: Error - The installer has detected running virtual machines. Please shut down all running VirtualBox machines and then restart the installation. (1)
> {code}
> The installer simply states "Failed". It would be nice if the installer could provide more details on why/what failed. Sparing me from having to inspect the logs.
> It simply states "Failed" for VirtualBox, the "Red Hat Container Development Kit" process is waiting for VirtualBox to get installed even though that failed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4252) Installer waits for failed Virtualbox installation (MacOS)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-4252?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-4252:
-----------------------------------
Attachment: waiting-for-virtualbox-install-that-failed.png
> Installer waits for failed Virtualbox installation (MacOS)
> ----------------------------------------------------------
>
> Key: JBDS-4252
> URL: https://issues.jboss.org/browse/JBDS-4252
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.3.0.AM1
> Reporter: Andre Dietisheim
> Attachments: waiting-for-virtualbox-install-that-failed.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have VirtualBox 5.1.x running but the app is removed from the Applications folder
> # EXEC: launch installer, log in and select VirtualBox etc.
> Result:
> Installer fails to install VirtualBox.
> !waiting-for-virtualbox-that-failed-to-install.png!
> In the logs you see the following:
> {code}
> 0:233: execution error: installer: Error - The installer has detected running virtual machines. Please shut down all running VirtualBox machines and then restart the installation. (1)
> {code}
> The installer simply states "Failed". It would be nice if the installer could provide more details on why/what failed. Sparing me from having to inspect the logs.
> It simply states "Failed" for VirtualBox, the "Red Hat Container Development Kit" process is waiting for VirtualBox to get installed even though that failed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months