[JBoss JIRA] (JBIDE-23626) Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23626:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23626
> URL: https://issues.jboss.org/browse/JBIDE-23626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Labels: oc_binary, preferences
> Fix For: 4.4.3.AM1
>
>
> oc 1.4, which is available from github is not compatible with the lastest CDK 2.3 (it's only compatible oc 1.3). Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use.
> Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use compatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23638) Scaling: Sometimes incorrect version of RC leads to error when scaling
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23638?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23638:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> Scaling: Sometimes incorrect version of RC leads to error when scaling
> ----------------------------------------------------------------------
>
> Key: JBIDE-23638
> URL: https://issues.jboss.org/browse/JBIDE-23638
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.Final
> Reporter: Marián Labuda
> Labels: openshift_v3
> Fix For: 4.4.3.AM1
>
>
> Sometimes when scaling an OpenShift 3 application several times, there is an error about failed PUT call. No jobs are running when triggering a scaling. Even though pods are shown correctly (right amount is shown) this error is shown:
> {code}
> com.openshift.restclient.OpenShiftException: Exception trying to PUT https://10.1.2.2:8443/api/v1/namespaces/test-project/replicationcontrolle... response code: 409 Operation cannot be fulfilled on replicationcontrollers "nodejs-example-1": the object has been modified; please apply your changes to the latest version and try again
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65)
> at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
> at okhttp3.RealCall.execute(RealCall.java:57)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:217)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:194)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:183)
> at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:275)
> at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler$2.run(ScaleDeploymentHandler.java:155)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22816:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> Create application from image (or builder) may lead to update being detected
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22816
> URL: https://issues.jboss.org/browse/JBIDE-22816
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.3.AM1
>
>
> When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-18848) setup tests for ide-config.properties
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18848?page=com.atlassian.jira.plugi... ]
Lukáš Valach closed JBIDE-18848.
--------------------------------
Verified, I can confirm that:
* The ide-config.properties is wraped as maven artifact
* ide-config.properties generator (ide-config.properties.py)
** checks for duplicate keys
** checks that there are exactly 8 keys for each prod/version
** checks for presence of ".GA" and ".Final" during stable build
> setup tests for ide-config.properties
> -------------------------------------
>
> Key: JBIDE-18848
> URL: https://issues.jboss.org/browse/JBIDE-18848
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, common
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Labels: releasework
> Fix For: 4.4.2.Final
>
>
> JBIDE-18837 and other jiras showed that ide-config.properties risk having errors introduced into it.
> we should have a test that runs every day to check if it is still consistent.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months