[JBoss JIRA] (JBIDE-23817) Scaling is not working with OpenShift 3.4 (CDK 2.4)
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-23817:
----------------------------------
Summary: Scaling is not working with OpenShift 3.4 (CDK 2.4)
Key: JBIDE-23817
URL: https://issues.jboss.org/browse/JBIDE-23817
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.3.AM2
Environment: CDK 2.4
Devstudio 10.3.0.AM2
Reporter: Radim Hopp
Priority: Critical
Scaling pods is broken when using Openshift 3.4 from CDK 2.4. I was not able to try it with another Openshift 3.4 installation (https://open.paas.redhat.com/ is not working properly from Devstudio either - ticket INC0496390 with service-now).
When I select scale to -> and select "4" to scale to 4 pods, the pods get started but they are immediately terminated and the scaling is "1" again.
This is not happening when I used https://console.engint.openshift.com/ (OpenShift v3.3.1.4).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (JBIDE-23662) Scaling To/Up/Down: causes error message (from OpenShift API) reporting outdated objects
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23662?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-23662.
------------------------------
Verified in Devstudio 10.3.0.AM2. Closing
> 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
>
> Attachments: scale-error-object-modified.png
>
>
> 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.
> !scale-error-object-modified.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (JBIDE-23814) Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error
by Siamak Sadeghianfar (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23814?page=com.atlassian.jira.plugi... ]
Siamak Sadeghianfar commented on JBIDE-23814:
---------------------------------------------
I downgraded my oc client to 3.3. Then I would get a different error using the same environment and pods.
!jbds-error.png|thumbnail!
> Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error
> -----------------------------------------------------------------
>
> Key: JBIDE-23814
> URL: https://issues.jboss.org/browse/JBIDE-23814
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: Red Hat JBoss Developer Studio
> Version: 10.2.0.GA
> Build id: GA-v20161125-1418-B55
> Build date: 20161125-1418
> JBoss Openshift UI Plugin
> Version: 3.3.1.v20161125-0956
> OpenShift
> openshift v3.3.1.3
> Reporter: Siamak Sadeghianfar
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.3.Final
>
> Attachments: jboss-eap70-openshift.png
>
>
> When adding a Server Adapter for an JBoss EAP 7 based deployments on OpenShift, operation fails with this error:
> {{Could not sync /private/tmp/workspace-demo/.metadata/.plugins/org.jboss.ide.eclipse.as.core/inventory-dev-ssadeghi@inventory/deploy to all pods running the service inventory
> OpenShiftBinaryCapability process exited: error: auth info "ssadeghi-redhat.com" does not exist}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (JBIDE-23814) Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error
by Siamak Sadeghianfar (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23814?page=com.atlassian.jira.plugi... ]
Siamak Sadeghianfar updated JBIDE-23814:
----------------------------------------
Attachment: jbds-error.png
> Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error
> -----------------------------------------------------------------
>
> Key: JBIDE-23814
> URL: https://issues.jboss.org/browse/JBIDE-23814
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: Red Hat JBoss Developer Studio
> Version: 10.2.0.GA
> Build id: GA-v20161125-1418-B55
> Build date: 20161125-1418
> JBoss Openshift UI Plugin
> Version: 3.3.1.v20161125-0956
> OpenShift
> openshift v3.3.1.3
> Reporter: Siamak Sadeghianfar
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.3.Final
>
> Attachments: jbds-error.png, jboss-eap70-openshift.png
>
>
> When adding a Server Adapter for an JBoss EAP 7 based deployments on OpenShift, operation fails with this error:
> {{Could not sync /private/tmp/workspace-demo/.metadata/.plugins/org.jboss.ide.eclipse.as.core/inventory-dev-ssadeghi@inventory/deploy to all pods running the service inventory
> OpenShiftBinaryCapability process exited: error: auth info "ssadeghi-redhat.com" does not exist}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months