October 2017 - jbosstools-issues - Jboss List Archives

[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 closed JBIDE-25273. ------------------------------------ Resolution: Rejected > 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: dc-rcs.png, 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 commented on JBIDE-25273: ------------------------------------------ what I see in your screenshots are the replication controllers. Nevertheless after some wait in Eclipse I see an update had happened in the dc which then made a new rc appear. So it looks like I was mislead when not waiting, thinking that web-ui had changed the rc. In this case we both (Eclipse tooling and the web-ui) use the same strategy: changing the dc which then creates a new rc. > 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: dc-rcs.png, 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-1178) Discovery update site refers to non-existing update site

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1178?page=com.atlassian.jira.plugin... ] Paul Leacu resolved JBTIS-1178. ------------------------------- Resolution: Done Corrected in the staging devstudio-directory.xml file. > Discovery update site refers to non-existing update site > -------------------------------------------------------- > > Key: JBTIS-1178 > URL: https://issues.jboss.org/browse/JBTIS-1178 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 11.1.0.Beta1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 11.1.0.Beta1 > > > Composite files at > https://devstudio.redhat.com/11/staging/updates/integration-stack/discove... > refer to > https://devstudio.redhat.com/targetplatforms/devstudioistarget/11.1.0.Bet... > which doesn't exist. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1177) Unknown category when specifying discovery url for Integration Stack EA

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1177?page=com.atlassian.jira.plugin... ] Paul Leacu resolved JBTIS-1177. ------------------------------- Resolution: Done This is corrected within the same beta release. No plugin changes required - Nick changed the name of the certification id. > Unknown category when specifying discovery url for Integration Stack EA > ----------------------------------------------------------------------- > > Key: JBTIS-1177 > URL: https://issues.jboss.org/browse/JBTIS-1177 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 11.1.0.Beta1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 11.1.0.Beta1 > > > {code} > Unknown category 'com.jboss.jbds.discovery.certification.supported.earlyaccess' referenced by connector 'jboss.integration-stack.ea.bundle.ds' declared in com.jboss.jbds.central.discovery.integration_stack.earlyaccess_11.1.0.Beta1_v20171012_1209_B62.jar_5518145992839178562.jar > {code} > I use Devstudio 11.1.0.GA-v20171017-1040-B1391 with the following lines in devstudio.ini > {code} > -Djboss.discovery.directory.url=https://devstudio.redhat.com/11/staging/updates/integration-stack/discovery/11.1.0.Beta1/devstudio-directory.xml > -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/11/staging/updates/integration-stack/discovery/11.1.0.Beta1 > -Djboss.discovery.earlyaccess.site.integration-stack.url=https://devstudio.redhat.com/11/staging/updates/integration-stack/discovery/11.1.0.Beta1/earlyaccess > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24897: ------------------------------------ Installing Fabric8 Analytics should now work from the nightly Central site [1] (see instructions here [2]) [1] https://devstudio.redhat.com/11/snapshots/updates/discovery.earlyaccess/m... [2] https://issues.jboss.org/browse/JBDS-4591?focusedCommentId=13480060&page=... ... but we should include the source feature too before we can mark this resolved. > add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector) > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24897 > URL: https://issues.jboss.org/browse/JBIDE-24897 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: fabric8 > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.Final > > > Once authentication (to access Fabric8 Analytics API) is fixed we can add this to JBoss Tools and devstudio. cc: [~gbatra] > Assuming we also want to create a Central connector to advertise this optional feature. > In future we could also consider adding a Marketplace connector (separate from JBT/devstudio), if that's desired. cc: [~maxandersen] [~adisakala] > Sources: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin > Affected: > * https://github.com/jbdevstudio/jbdevstudio-product (category.xml, feature.xml) > * https://github.com/jbosstools/jbosstools-build-sites (category.xml) > * https://github.com/jbosstools/jbosstools-discovery (plugin.xml x 2, plus new icon if applicable?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4591) Can't install com.redhat.fabric8analytics.lsp.eclipse from RH Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4591?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4591: ----------------------------- Attachment: fabric8-connector.png > Can't install com.redhat.fabric8analytics.lsp.eclipse from RH Central > --------------------------------------------------------------------- > > Key: JBDS-4591 > URL: https://issues.jboss.org/browse/JBDS-4591 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central, central-update > Affects Versions: 11.1.0.GA > Environment: * RHEL7 > * rh-eclipse47-devstudio-11.1-0.20171019.0637.el7.x86_64.rpm > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.1.0.GA > > Attachments: fabric8-connector.png > > > It is not possible to install "Fabric8 Analytics Language Server Integration" from RH Central. Feature group *com.redhat.fabric8analytics.lsp.eclipse.feature.feature.group* isn't in update site. > {code} > Problems occurred while performing installation: The following connectors are not available: Fabric8 Analytics Language Server Integration (id=com.redhat.fabric8analytics.lsp.eclipse.feature.feature.group, site=https://devstudio.redhat.com/11/snapshots/updates/discovery.earlyacc...) > The following connectors are not available: Fabric8 Analytics Language Server Integration (id=com.redhat.fabric8analytics.lsp.eclipse.feature.feature.group, site=https://devstudio.redhat.com/11/snapshots/updates/discovery.earlyacc...) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4591) Can't install com.redhat.fabric8analytics.lsp.eclipse from RH Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4591?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4591: ---------------------------------- 0. Install Eclipse Oxygen.1a JEE bundle 1. Help > Install > https://devstudio.redhat.com/11/snapshots/updates/discovery.earlyaccess/m... > Central feature; restart when prompted 2. Launch Central. Enable Early Access. Browse or search for fabric8 analytics. !fabric8-connector.png|thumbnail! Feature can now be installed. > Can't install com.redhat.fabric8analytics.lsp.eclipse from RH Central > --------------------------------------------------------------------- > > Key: JBDS-4591 > URL: https://issues.jboss.org/browse/JBDS-4591 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central, central-update > Affects Versions: 11.1.0.GA > Environment: * RHEL7 > * rh-eclipse47-devstudio-11.1-0.20171019.0637.el7.x86_64.rpm > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.1.0.GA > > Attachments: fabric8-connector.png > > > It is not possible to install "Fabric8 Analytics Language Server Integration" from RH Central. Feature group *com.redhat.fabric8analytics.lsp.eclipse.feature.feature.group* isn't in update site. > {code} > Problems occurred while performing installation: The following connectors are not available: Fabric8 Analytics Language Server Integration (id=com.redhat.fabric8analytics.lsp.eclipse.feature.feature.group, site=https://devstudio.redhat.com/11/snapshots/updates/discovery.earlyacc...) > The following connectors are not available: Fabric8 Analytics Language Server Integration (id=com.redhat.fabric8analytics.lsp.eclipse.feature.feature.group, site=https://devstudio.redhat.com/11/snapshots/updates/discovery.earlyacc...) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4591) Can't install com.redhat.fabric8analytics.lsp.eclipse from RH Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4591?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-4591. ------------------------------ Resolution: Done > Can't install com.redhat.fabric8analytics.lsp.eclipse from RH Central > --------------------------------------------------------------------- > > Key: JBDS-4591 > URL: https://issues.jboss.org/browse/JBDS-4591 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central, central-update > Affects Versions: 11.1.0.GA > Environment: * RHEL7 > * rh-eclipse47-devstudio-11.1-0.20171019.0637.el7.x86_64.rpm > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.1.0.GA > > Attachments: fabric8-connector.png > > > It is not possible to install "Fabric8 Analytics Language Server Integration" from RH Central. Feature group *com.redhat.fabric8analytics.lsp.eclipse.feature.feature.group* isn't in update site. > {code} > Problems occurred while performing installation: The following connectors are not available: Fabric8 Analytics Language Server Integration (id=com.redhat.fabric8analytics.lsp.eclipse.feature.feature.group, site=https://devstudio.redhat.com/11/snapshots/updates/discovery.earlyacc...) > The following connectors are not available: Fabric8 Analytics Language Server Integration (id=com.redhat.fabric8analytics.lsp.eclipse.feature.feature.group, site=https://devstudio.redhat.com/11/snapshots/updates/discovery.earlyacc...) > {code} -- 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 Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25273?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-25273: ------------------------------------ I don't agree See my DC after updating the limlits: !dc-rcs.png|thumbnail! > 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: dc-rcs.png, 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 Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25273?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25273: ------------------------------- Attachment: dc-rcs.png > 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: dc-rcs.png, 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