[JBoss JIRA] (JBIDE-23662) Scaling To/Up/Down: causes error message (from OpenShift API) reporting outdated objects
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23662?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23662:
-------------------------------------
Description:
Every Scale option I select in the OpenShift Explorer view show this error:
Unable to scale guestbook-service
Exception trying to PUT https://10.1.2.2:8443/api/v1/namespaces/sample-project/replicationcontrol... response code: 409 Operation cannot be fulfilled on replicationcontrollers "guestbook-service-2": the object has been modified; please apply your changes to the latest version and try again
However, the scale command is executed successfuly.
Steps to reproduce:
# ASSERT: make sure that you have a service with at least 1 pod running in OpenShift
# EXEC: in OpenShift Explorer: select your service and pick "Scale > To" in the context menu
# ASSERT: "Scale Deployment" dialog is shown, prefilled with the current number of replicas
# EXEC: change the replicas to a high number (ex. 6 is working well for me to cause the error)
# ASSERT: you get the error, if not process with next step
# EXEC: in OpenShift Explorer: select your service and pick "Scale > To" in the context menu and scale down to "1" replica
Result:
either you now get the error above or you need to scale back up etc.
was:
Every Scale option I select in the OpenShift Explorer view show this error:
Unable to scale guestbook-service
Exception trying to PUT https://10.1.2.2:8443/api/v1/namespaces/sample-project/replicationcontrol... response code: 409 Operation cannot be fulfilled on replicationcontrollers "guestbook-service-2": the object has been modified; please apply your changes to the latest version and try again
However, the scale command is executed successfuly.
> Scaling To/Up/Down: causes error message (from OpenShift API) reporting outdated objects
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-23662
> URL: https://issues.jboss.org/browse/JBIDE-23662
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Ricardo Martinelli Oliveira
> Assignee: Andre Dietisheim
> Labels: openshift_v3, scaling_pods_wizard
> Fix For: 4.4.3.AM2
>
>
> Every Scale option I select in the OpenShift Explorer view show this error:
> Unable to scale guestbook-service
> Exception trying to PUT https://10.1.2.2:8443/api/v1/namespaces/sample-project/replicationcontrol... response code: 409 Operation cannot be fulfilled on replicationcontrollers "guestbook-service-2": the object has been modified; please apply your changes to the latest version and try again
> However, the scale command is executed successfuly.
> Steps to reproduce:
> # ASSERT: make sure that you have a service with at least 1 pod running in OpenShift
> # EXEC: in OpenShift Explorer: select your service and pick "Scale > To" in the context menu
> # ASSERT: "Scale Deployment" dialog is shown, prefilled with the current number of replicas
> # EXEC: change the replicas to a high number (ex. 6 is working well for me to cause the error)
> # ASSERT: you get the error, if not process with next step
> # EXEC: in OpenShift Explorer: select your service and pick "Scale > To" in the context menu and scale down to "1" replica
> Result:
> either you now get the error above or you need to scale back up etc.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBTIS-1018) Adapt tests for RHDSIS 10
by Matej Kralik (JIRA)
Matej Kralik created JBTIS-1018:
-----------------------------------
Summary: Adapt tests for RHDSIS 10
Key: JBTIS-1018
URL: https://issues.jboss.org/browse/JBTIS-1018
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: QE, teiid
Affects Versions: 4.4.0.Final
Reporter: Matej Kralik
Assignee: Matej Kralik
Priority: Critical
Oracle CP is different.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ]
Rastislav Wagner edited comment on JBIDE-23733 at 1/18/17 5:23 AM:
-------------------------------------------------------------------
This was discussed on local QE meeting and the result is:
We will have nightly, weekly and smoke jobs.
Nightly jobs will run only on one machine (rhel7) - currently we run them on Linux/Windows/OSX. We will schedule them to run 3-8 AM, Brno time only if some change happened in component repo. Nightly jobs are running all integration tests.
Weekly jobs will run during the weekends, on Linux/Windows/OSX - same set of tests as Nightly jobs
Smoke jobs will run on demand and will run only critical tests.
[~nickboldt] WDYT ?
was (Author: rawagner):
This was discussed on local QE meeting and the result is:
We will have nightly, weekly and smoke jobs.
Nightly jobs will run only on one machine (rhel7) - currently we run them on Linux/Windows/OSX. We will schedule them to run 3-8 AM, Brno time only if some change happened in component repo. Nightly jobs are running all integration tests a.
Weekly jobs will run during the weekends, on Linux/Windows/OSX - same set of tests as Nightly jobs
Smoke jobs will run on demand and will run only critical tests.
[~nickboldt] WDYT ?
> Merge .smoke and .nightly integration jobs into a single job and run them weekly
> --------------------------------------------------------------------------------
>
> Key: JBIDE-23733
> URL: https://issues.jboss.org/browse/JBIDE-23733
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-tests
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rastislav Wagner
>
> Purpose:
> a) easier maintenance of jobs / tests
> b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests
> c) more frequent full integration runs (rather than once per sprint, once per week)
> Tests to merge are in this view:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-23733:
------------------------------------------
This was discussed on local QE meeting and the result is:
We will have nightly, weekly and smoke jobs.
Nightly jobs will run only on one machine (rhel7) - currently we run them on Linux/Windows/OSX. We will schedule them to run 3-8 AM, Brno time only if some change happened in component repo. Nightly jobs are running all integration tests a.
Weekly jobs will run during the weekends, on Linux/Windows/OSX - same set of tests as Nightly jobs
Smoke jobs will run on demand and will run only critical tests.
[~nickboldt] WDYT ?
> Merge .smoke and .nightly integration jobs into a single job and run them weekly
> --------------------------------------------------------------------------------
>
> Key: JBIDE-23733
> URL: https://issues.jboss.org/browse/JBIDE-23733
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-tests
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rastislav Wagner
>
> Purpose:
> a) easier maintenance of jobs / tests
> b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests
> c) more frequent full integration runs (rather than once per sprint, once per week)
> Tests to merge are in this view:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23722) Fedora 24 x86 on CentralCI
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23722?page=com.atlassian.jira.plugi... ]
Lukáš Valach commented on JBIDE-23722:
--------------------------------------
The Fedora 24 x86 image is prepared and ready to use for testing of JBDS installer. I prepared these image by hand, not using the scripts (1), because [~jkopriva] is already working on these scripts. is already working on these scripts.
(1) http://qeos.centralci.eng.rdu2.redhat.com/dashboard/project/images/
*Jenkins label:* fedora24-x86-jbds-installer
*Image prepared for testing:* fedora24-x86-jbds-installer
*Base image:* Fedora-Cloud-Base-24-i386-20161207.0-testing ([source|https://dl.fedoraproject.org/pub/alt/atomic/testing/20161207.0/Clo...])
Because of problem during installation the image is missing some stuff which are included in standard "jbds" label and which are not necessary for installer testing:
* Epel 5 repository (http://dl.fedoraproject.org/pub/epel/5/x86_64/epel-release-5-4.noarch.rpm) - fedora-release conflicts with epel-release-5-4.noarch
* Avocado (label/rhel/avocado.sh) - can't install from any repository
* java-1.7.0-openjdk-devel - not included in yum repository
* java-1.6.0-openjdk-devel - not included in yum repository
It is worth mentioning default version of authorized_keys prevented ssh connection and X11 forwarding, so I had to remove this line form /home/hudson/.ssh/authorized_keys
{code}
no-port-forwarding,no-agent-forwarding,no-X11-forwarding,command="echo 'Please login as the user \"fedora\" rather than the user \"root\".';echo;sleep 10"
{code}
> Fedora 24 x86 on CentralCI
> --------------------------
>
> Key: JBIDE-23722
> URL: https://issues.jboss.org/browse/JBIDE-23722
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 4.4.3.AM2
>
>
> Create Fedora 24 x86 image on CentralCI.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4251) Have to restart installer if I remove Virtualbox, installer wont properly re-check
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4251?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-4251:
-------------------------------------
I removed mac os from summary becuase the same problem exists under windows.
> Have to restart installer if I remove Virtualbox, installer wont properly re-check
> ----------------------------------------------------------------------------------
>
> Key: JBDS-4251
> URL: https://issues.jboss.org/browse/JBDS-4251
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.3.0.AM1
> Reporter: Andre Dietisheim
> Attachments: virtualbox-too-new.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have VirtualBox 5.1.X installed
> # EXEC: launch platform installer, log in, get to components selection page
> # ASSERT: installer complains that Virtualbox 5.1.x is newer than the required 5.0.x, you cant continue
> !virtualbox-too-new.png!
> # EXEC: dont close installer, uninstall Virtualbox in the background
> # ASSERT: installer wont notice the uninstall, which is kinda expected
> # EXEC: hit "Back" and get back to the component selection
> # ASSERT: Component checks are executed.
> Result:
> Checks are executed again, but the installer still complains that VirtualBox 5.1.x is installed and newer than the exepected 5.0.x version.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4251) Have to restart installer if I remove Virtualbox, installer wont properly re-check
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4251?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4251:
--------------------------------
Summary: Have to restart installer if I remove Virtualbox, installer wont properly re-check (was: Have to restart MacOS installer if I remove Virtualbox, installer wont properly re-check)
> Have to restart installer if I remove Virtualbox, installer wont properly re-check
> ----------------------------------------------------------------------------------
>
> Key: JBDS-4251
> URL: https://issues.jboss.org/browse/JBDS-4251
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.3.0.AM1
> Reporter: Andre Dietisheim
> Attachments: virtualbox-too-new.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have VirtualBox 5.1.X installed
> # EXEC: launch platform installer, log in, get to components selection page
> # ASSERT: installer complains that Virtualbox 5.1.x is newer than the required 5.0.x, you cant continue
> !virtualbox-too-new.png!
> # EXEC: dont close installer, uninstall Virtualbox in the background
> # ASSERT: installer wont notice the uninstall, which is kinda expected
> # EXEC: hit "Back" and get back to the component selection
> # ASSERT: Component checks are executed.
> Result:
> Checks are executed again, but the installer still complains that VirtualBox 5.1.x is installed and newer than the exepected 5.0.x version.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months