October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-1019) Fuse - Create a test for deploying a Fuse project on OpenShift

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1019?page=com.atlassian.jira.plugin... ] Tomáš Sedmík closed JBTIS-1019. ------------------------------- Resolution: Done closing as duplicate issue > Fuse - Create a test for deploying a Fuse project on OpenShift > -------------------------------------------------------------- > > Key: JBTIS-1019 > URL: https://issues.jboss.org/browse/JBTIS-1019 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.0.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > > Try to deploy _Spring on OpenShift_ project to OpenShift -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1176) BPMN2 - some tests are freezing on Windows

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1176?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBTIS-1176: ------------------------------------------ [~dhanak] I tried various approaches but the job 'BPMN2 Property Page redraw' is still freezing. Note that if you use branch 'jbtis-4.5.x' (which uses RedDeer 1.x) it is working. So, please use this branch for the testing until we resolve the issue with RedDeer 2.x. > BPMN2 - some tests are freezing on Windows > ------------------------------------------ > > Key: JBTIS-1176 > URL: https://issues.jboss.org/browse/JBTIS-1176 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2, QE > Affects Versions: 4.5.1.Beta1 > Environment: Devstudio IS 11.1.0.Beta1 > Windows 10 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Priority: Blocker > Fix For: 4.5.1.Beta1 > > > Some BPMN2 tests are freezing on Windows. One of the tests is ComplexCompensationEventTest. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25273) Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25273?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-25273 at 10/20/17 10:07 AM: --------------------------------------------------------------------- The problem here is not a parsing issue. The tooling displays the correct value and units for the resource that's being edited. It's the resource that's being edited, that's differs: The user operation above edits the *replication controller*. The web-ui does exactly that, it is changing the replication controller. Our tooling is changing the *deployment config*. It only falls back to the replication controller if there's no deployment config. for the above to reflect the correct value/unit I would have to edit the deployment config. If I do that things are displayed correctly. [~jeffmaury] thoughts? Which one is correct/preferrable? Us or them? OC wont choose for you, you have to decide whether you update the rc or the dc by specifying the resource to change: {code} oc set resources dc nodejs-mongo-persistent --limits=memory=512Mi oc set resources rc nodejs-mongo-persistent-3 --limits=memory=512Mi {code} btw. there's another problem with the code: the resource loading is done in the handler whereas it should be done in a background job. was (Author: adietish): The problem here is not a parsing issue. The tooling displays the correct value and units for the resource that's being edited. It's the resource that's being edited, that's differs: The user operation above edits the *replication controller*. The web-ui does exactly that, it is changing the replication controller. Our tooling is changing the *deployment config*. It only falls back to the replication controller if there's no deployment config. for the above to reflect the correct value/unit I would have to edit the deployment config. If I do that things are displayed correctly. [~jeffmaury] thoughts? Which one is correct/preferrable? Us or them? btw. there's another problem with the code: the resource loading is done in the handler whereas it should be done in a background job. > Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes" > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-25273 > URL: https://issues.jboss.org/browse/JBIDE-25273 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Attachments: edit-resource-limits-memory-limit-units.png > > > steps: > # ASSERT: make sure that you have an application with a service and replication controller running in OpenShift (ex. create an app with the nodejs-mongo-persistent template) > # ASSERT: make sure that your memory request limit is in bytes: > # EXEC: in OpenShift explorer, select your project > # EXEC: in "Properties" view, select "Deployments" tab and select the last entry > # EXEC: pick "Edit" in the context menu to it > # ASSERT: replication controller is opened in the editor > # EXEC: search (Ctrl+F) "limits" and make sure it has an entry for memory limits that has no unit > {code} > "resources" : { > "limits" : {"memory" : "512"}, > }, > {code} > # EXEC: in OpenShift Explorer: select the service for your application and pick "Edit Resource Limits..." in the context menu > # ASSERT: Edit resource limits wizard shows up > Result: > Memory > Limits show *MiB* as unit > !edit-resource-limits-memory-limit-units.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-891) Fuse: Adapt smoke tests to determine missing new Fuse project wizard

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-891?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-891. ------------------------------ Resolution: Won't Do > Fuse: Adapt smoke tests to determine missing new Fuse project wizard > -------------------------------------------------------------------- > > Key: JBTIS-891 > URL: https://issues.jboss.org/browse/JBTIS-891 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.1.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.3.2.Final > > > see https://issues.jboss.org/browse/FUSETOOLS-2102 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-780) Fuse: Add test case for endpoint manipulation in JMX Navigator

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-780?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-780. ------------------------------ Resolution: Out of Date closing as out of date issue > Fuse: Add test case for endpoint manipulation in JMX Navigator > -------------------------------------------------------------- > > Key: JBTIS-780 > URL: https://issues.jboss.org/browse/JBTIS-780 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > > In JMX Navigator View can be created/deleted endpoints (in running Camel context) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25273) Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25273?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-25273 at 10/20/17 9:57 AM: -------------------------------------------------------------------- The problem here is not a parsing issue. The tooling displays the correct value and units for the resource that's being edited. It's the resource that's being edited, that's differs: The user operation above edits the *replication controller*. The web-ui does exactly that, it is changing the replication controller. Our tooling is changing the *deployment config*. It only falls back to the replication controller if there's no deployment config. for the above to reflect the correct value/unit I would have to edit the deployment config. If I do that things are displayed correctly. [~jeffmaury] thoughts? Which one is correct? Us or them? btw. there's another problem with the code: the resource loading is done in the handler whereas it should be done in a background job. was (Author: adietish): The problem here is not a parsing issue. The tooling displays the correct value and units for the resource that's being edited. It's the resource that's being edited, that's differs: The user operation above edits the *replication controller*. The web-ui does exactly that, it is changing the replication controller. Our tooling is changing the *deployment config*. It only falls back to the replication controller if there's no deployment config. for the above to reflect the correct value/unit I would have to edit the deployment config. If I do that things are displayed correctly. [~jeffmaury] thoughts? btw. there's another problem with the code: the resource loading is done in the handler whereas it should be done in a background job. > Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes" > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-25273 > URL: https://issues.jboss.org/browse/JBIDE-25273 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Attachments: edit-resource-limits-memory-limit-units.png > > > steps: > # ASSERT: make sure that you have an application with a service and replication controller running in OpenShift (ex. create an app with the nodejs-mongo-persistent template) > # ASSERT: make sure that your memory request limit is in bytes: > # EXEC: in OpenShift explorer, select your project > # EXEC: in "Properties" view, select "Deployments" tab and select the last entry > # EXEC: pick "Edit" in the context menu to it > # ASSERT: replication controller is opened in the editor > # EXEC: search (Ctrl+F) "limits" and make sure it has an entry for memory limits that has no unit > {code} > "resources" : { > "limits" : {"memory" : "512"}, > }, > {code} > # EXEC: in OpenShift Explorer: select the service for your application and pick "Edit Resource Limits..." in the context menu > # ASSERT: Edit resource limits wizard shows up > Result: > Memory > Limits show *MiB* as unit > !edit-resource-limits-memory-limit-units.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25273) Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25273?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-25273 at 10/20/17 9:57 AM: -------------------------------------------------------------------- The problem here is not a parsing issue. The tooling displays the correct value and units for the resource that's being edited. It's the resource that's being edited, that's differs: The user operation above edits the *replication controller*. The web-ui does exactly that, it is changing the replication controller. Our tooling is changing the *deployment config*. It only falls back to the replication controller if there's no deployment config. for the above to reflect the correct value/unit I would have to edit the deployment config. If I do that things are displayed correctly. [~jeffmaury] thoughts? Which one is correct/preferrable? Us or them? btw. there's another problem with the code: the resource loading is done in the handler whereas it should be done in a background job. was (Author: adietish): The problem here is not a parsing issue. The tooling displays the correct value and units for the resource that's being edited. It's the resource that's being edited, that's differs: The user operation above edits the *replication controller*. The web-ui does exactly that, it is changing the replication controller. Our tooling is changing the *deployment config*. It only falls back to the replication controller if there's no deployment config. for the above to reflect the correct value/unit I would have to edit the deployment config. If I do that things are displayed correctly. [~jeffmaury] thoughts? Which one is correct? Us or them? btw. there's another problem with the code: the resource loading is done in the handler whereas it should be done in a background job. > Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes" > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-25273 > URL: https://issues.jboss.org/browse/JBIDE-25273 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Attachments: edit-resource-limits-memory-limit-units.png > > > steps: > # ASSERT: make sure that you have an application with a service and replication controller running in OpenShift (ex. create an app with the nodejs-mongo-persistent template) > # ASSERT: make sure that your memory request limit is in bytes: > # EXEC: in OpenShift explorer, select your project > # EXEC: in "Properties" view, select "Deployments" tab and select the last entry > # EXEC: pick "Edit" in the context menu to it > # ASSERT: replication controller is opened in the editor > # EXEC: search (Ctrl+F) "limits" and make sure it has an entry for memory limits that has no unit > {code} > "resources" : { > "limits" : {"memory" : "512"}, > }, > {code} > # EXEC: in OpenShift Explorer: select the service for your application and pick "Edit Resource Limits..." in the context menu > # ASSERT: Edit resource limits wizard shows up > Result: > Memory > Limits show *MiB* as unit > !edit-resource-limits-memory-limit-units.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-779) Fuse: Add test case for run configurations

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-779?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-779. ------------------------------ Resolution: Duplicate Issue closing as a duplicate issue > Fuse: Add test case for run configurations > ------------------------------------------ > > Key: JBTIS-779 > URL: https://issues.jboss.org/browse/JBTIS-779 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > > Local Camel Context > Maven Build -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-773) Fuse: Add test for JBoss Central

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-773?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-773. ------------------------------ Resolution: Out of Date this issue is out of date > Fuse: Add test for JBoss Central > -------------------------------- > > Key: JBTIS-773 > URL: https://issues.jboss.org/browse/JBTIS-773 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > > A Fuse Integration Project can be created from JBoss Central. In case of Fuse Tooling is not installed, it installs the tooling. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25273) Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25273?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-25273 at 10/20/17 9:43 AM: -------------------------------------------------------------------- The problem here is not a parsing issue. The tooling displays the correct value and units for the resource that's being edited. It's the resource that's being edited, that's differs: The user operation above edits the *replication controller*. The web-ui does exactly that, it is changing the replication controller. Our tooling is changing the *deployment config*. It only falls back to the replication controller if there's no deployment config. for the above to reflect the correct value/unit I would have to edit the deployment config. If I do that things are displayed correctly. [~jeffmaury] thoughts? btw. there's another problem with the code: the resource loading is done in the handler whereas it should be done in a background job. was (Author: adietish): The problem here is not a parsing issue. The tooling displays the correct value and units for the resource that's being edited. It's the resource that's being edited, that's differs: The user operation above edits the *replication controller*. The web-ui does exactly that, it is changing the replication controller. Our tooling is changing the *deployment config*. It only falls back to the replication controller if there's no deployment config. for the above to reflect the correct value/unit I would have to edit the deployment config. If I do that things are displayed correctly. [~jeffmaury] thoughts? > Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes" > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-25273 > URL: https://issues.jboss.org/browse/JBIDE-25273 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Attachments: edit-resource-limits-memory-limit-units.png > > > steps: > # ASSERT: make sure that you have an application with a service and replication controller running in OpenShift (ex. create an app with the nodejs-mongo-persistent template) > # ASSERT: make sure that your memory request limit is in bytes: > # EXEC: in OpenShift explorer, select your project > # EXEC: in "Properties" view, select "Deployments" tab and select the last entry > # EXEC: pick "Edit" in the context menu to it > # ASSERT: replication controller is opened in the editor > # EXEC: search (Ctrl+F) "limits" and make sure it has an entry for memory limits that has no unit > {code} > "resources" : { > "limits" : {"memory" : "512"}, > }, > {code} > # EXEC: in OpenShift Explorer: select the service for your application and pick "Edit Resource Limits..." in the context menu > # ASSERT: Edit resource limits wizard shows up > Result: > Memory > Limits show *MiB* as unit > !edit-resource-limits-memory-limit-units.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

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 October 2017