November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22239: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Allow a user to choose to permanently update their desired replicas for their deployment > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22239 > URL: https://issues.jboss.org/browse/JBIDE-22239 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Viacheslav Kabanovich > Labels: openshift_v3 > Fix For: 4.5.x > > > When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest: > * Adding a custom dialog in the "..to.." option > * Update to use a spinner > * Add a checkbox to 'make the change perminent' > * If checkbox=true, you should only need to update the dc if it has a configchange trigger. > * Optionally show checkbox if unable to determine the dc associated with the deployment. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23270) [Watcher] Deploy docker wizard: pushing image to OpenShift Docker registry refused because of self-signed certificate

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23270?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23270: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > [Watcher] Deploy docker wizard: pushing image to OpenShift Docker registry refused because of self-signed certificate > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23270 > URL: https://issues.jboss.org/browse/JBIDE-23270 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Labels: deploy_docker_wizard, upstream > Fix For: 4.5.0.AM1 > > Attachments: pushing-failed-self-signed-certificate.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22727) Openshift resources managed by explorer and watcher are declared in both place leading to inconsistency

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22727?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22727: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Openshift resources managed by explorer and watcher are declared in both place leading to inconsistency > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22727 > URL: https://issues.jboss.org/browse/JBIDE-22727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.5.0.AM1 > > > The kind of Openshift resources are declated in 2 different places: WatchManager and ConnectionWrapper. This increases the technical debt and may lead to resources displayed by the explorer but not refreshed by the watcher. > The task requires investigation about ResourceKind.IMAGE_STREAM_TAG, which is present in ConnectionWrapper, but there is no such element in WatchManager's array. See discussion [here|https://github.com/jbosstools/jbosstools-openshift/pull/1272#discuss...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4200) Problem installing switchyard

by Lukáš Valach (JIRA)

Lukáš Valach created JBDS-4200: ---------------------------------- Summary: Problem installing switchyard Key: JBDS-4200 URL: https://issues.jboss.org/browse/JBDS-4200 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: rpm Affects Versions: 10.2.0.GA Environment: RHEL7 Reporter: Lukáš Valach Attachments: rh-eclipse46-devstudio10.2.log.switchyard_plugin_test.txt I tried to install switchyard and this error appeared in the log after restart: {code} !ENTRY org.switchyard.tools.core 4 0 2016-11-23 09:45:11.118 !MESSAGE FrameworkEvent ERROR !STACK 0 org.osgi.framework.BundleException: Could not resolve module: org.switchyard.tools.core [1390] Bundle was not resolved because of a uses contraint violation. org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.switchyard.tools.core [osgi.identity; osgi.identity="org.switchyard.tools.core"; type="osgi.bundle"; version:Version="2.2.0.Final-v20161110-1803-B65"] because it is exposed to package 'org.slf4j' from resources org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"] and slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.4"; osgi.identity="slf4j.api"] via two dependency chains. {code} See whole log here [^rh-eclipse46-devstudio10.2.log.switchyard_plugin_test.txt]. Tested in 10.2-0.20161123.1426. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23402) [WATCHER] Explorer: can "Deploy Latest" even if the build failed

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23402: ------------------------------------- TODO: File upstream issue at origin, then link, then mark this issue as 'LATER' or fixed if upstream fixes it. > [WATCHER] Explorer: can "Deploy Latest" even if the build failed > ---------------------------------------------------------------- > > Key: JBIDE-23402 > URL: https://issues.jboss.org/browse/JBIDE-23402 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Fix For: 4.5.0.AM1 > > Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png > > > When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete. > In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23389) OpenShift 3.4 support

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23389?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23389: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.2.Final) > OpenShift 3.4 support > --------------------- > > Key: JBIDE-23389 > URL: https://issues.jboss.org/browse/JBIDE-23389 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Alexey Kazakov > Assignee: Jeff MAURY > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.5.0.AM1 > > > OpenShift 3.4 is currently in progress but we need to start testing it now to see if we need adjust anything in our tools to support it. > cc: [~adietish] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23402) [WATCHER] Explorer: can "Deploy Latest" even if the build failed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23402: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > [WATCHER] Explorer: can "Deploy Latest" even if the build failed > ---------------------------------------------------------------- > > Key: JBIDE-23402 > URL: https://issues.jboss.org/browse/JBIDE-23402 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Fix For: 4.5.0.AM1 > > Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png > > > When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete. > In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4125) Provide environment variable to override developers.redhat.com in download manager URLs

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBDS-4125?page=com.atlassian.jira.plugin.... ] Ondrej Dockal edited comment on JBDS-4125 at 11/23/16 10:49 AM: ---------------------------------------------------------------- * UPDATE: I learn what jdf is, no need to answer following part anymore. Maybe I found a problematic part in issue I described above. When I check url of CDK on stage server, it is https://developers.stage.redhat.com/download-manager/file/cdk-2.3.0.RC1.zip and if I set DM_STAGE_HOST var. then it is trying to download https://developers.stage.redhat.com/download-manager/jdf/file/cdk-2.3.0.R..., the difference is in /jdf/ part of url, and this results in different checksums of downloaded file (it just downloads some content of unavailable url) and expected from requirement-*.json file. Also, devstudio url in requirement files is probably missing timestamp and build number. It is: https://developers.redhat.com/download-manager/jdf/file/devstudio-10.2.0.... but should be something like: devstudio-10.2.0.AM3-v20161104-1659-B6372-installer-standalone.jar It is just my guess. was (Author: odockal): Maybe I found a problematic part in issue I described above. When I check url of CDK on stage server, it is https://developers.stage.redhat.com/download-manager/file/cdk-2.3.0.RC1.zip and if I set DM_STAGE_HOST var. then it is trying to download https://developers.stage.redhat.com/download-manager/jdf/file/cdk-2.3.0.R..., the difference is in /jdf/ part of url, and this results in different checksums of downloaded file (it just downloads some content of unavailable url) and expected from requirement-*.json file. Also, devstudio url is probably missing timestamp and build number. It is: https://developers.redhat.com/download-manager/jdf/file/devstudio-10.2.0.... but should be something like: devstudio-10.2.0.AM3-v20161104-1659-B6372-installer-standalone.jar It is just my guess. Thanks for any advice. > Provide environment variable to override developers.redhat.com in download manager URLs > --------------------------------------------------------------------------------------- > > Key: JBDS-4125 > URL: https://issues.jboss.org/browse/JBDS-4125 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.2.0.GA > > Attachments: install.log > > > This is required to support testing online installer with staged download manager -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23402) [WATCHER] Explorer: can "Deploy Latest" even if the build failed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23402 at 11/23/16 10:48 AM: --------------------------------------------------------------------- [~rob.stryker] dare to file an issue against origin since you have the most infos? was (Author: adietish): [~rob.stryker] dare to file an issue again origin since you have the most infos? > [WATCHER] Explorer: can "Deploy Latest" even if the build failed > ---------------------------------------------------------------- > > Key: JBIDE-23402 > URL: https://issues.jboss.org/browse/JBIDE-23402 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Fix For: 4.4.x > > Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png > > > When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete. > In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23066) Generating hbm.xml files always happens using the 3.5 runtime

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23066?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23066: ------------------------------------- [~koen.aers] Can you please re-target this issue for 4.5.0 or close it if it is no longer relevant? > Generating hbm.xml files always happens using the 3.5 runtime > ------------------------------------------------------------- > > Key: JBIDE-23066 > URL: https://issues.jboss.org/browse/JBIDE-23066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.x > > > This issue is related to JBIDE-22997 and JBIDE-23059. After implementing JBIDE-23059 the phenomenon described in JBIDE-22997 disappeared but the hbm.xml files are now always generated using the 3.5 runtime, even when the project is a hibernate project with a console configuration using another version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 November 2016