July 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26221) Server adapter wizard: reconfiguring oc will cause warning, where it should error

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-26221: ---------------------------------------- Summary: Server adapter wizard: reconfiguring oc will cause warning, where it should error Key: JBIDE-26221 URL: https://issues.jboss.org/browse/JBIDE-26221 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.9.0.AM1 Reporter: Andre Dietisheim Attachments: image-2018-07-18-17-15-31-065.png, image-2018-07-18-17-21-42-843.png # ASSERT: have a project with a service running on OpenShift # ASSERT: have the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] applied to your code # ASSERT: in OpenShift Preferences: have oc not configured (or alternatively have it pointed to a location with a " " - ex. ~/oc binaries/oc) -> in both cases preferences will display a warning # EXEC: launch server adapter wizard for your service # ASSERT: server adapter wizard shows an error with a link to "configure" the oc binary !image-2018-07-18-17-15-31-065.png! # EXEC: hit "configure" and then in preferences configure a fake oc file (ex. a dummy file that you created with "touch ~/oc && chmod +x oc"). # ASSERT: after closing preferences you're back in the server adapter wizard Result: Server adapter wizard now shows a warning, while it should show an error !image-2018-07-18-17-21-42-843.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26221) Server adapter wizard: reconfiguring oc will cause warning, where it should error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26221?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26221: ------------------------------------- Fix Version/s: 4.9.0.AM1 > Server adapter wizard: reconfiguring oc will cause warning, where it should error > --------------------------------------------------------------------------------- > > Key: JBIDE-26221 > URL: https://issues.jboss.org/browse/JBIDE-26221 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM1 > Reporter: Andre Dietisheim > Fix For: 4.9.0.AM1 > > Attachments: image-2018-07-18-17-15-31-065.png, image-2018-07-18-17-21-42-843.png > > > # ASSERT: have a project with a service running on OpenShift > # ASSERT: have the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] applied to your code > # ASSERT: in OpenShift Preferences: have oc not configured (or alternatively have it pointed to a location with a " " - ex. ~/oc binaries/oc) -> in both cases preferences will display a warning > # EXEC: launch server adapter wizard for your service > # ASSERT: server adapter wizard shows an error with a link to "configure" the oc binary > !image-2018-07-18-17-15-31-065.png! > # EXEC: hit "configure" and then in preferences configure a fake oc file (ex. a dummy file that you created with "touch ~/oc && chmod +x oc"). > # ASSERT: after closing preferences you're back in the server adapter wizard > Result: > Server adapter wizard now shows a warning, while it should show an error > !image-2018-07-18-17-21-42-843.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26117) Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26117?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26117: ---------------------------------- Assignee: Andre Dietisheim > Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui) > ----------------------------------------------------------------------------------- > > Key: JBIDE-26117 > URL: https://issues.jboss.org/browse/JBIDE-26117 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.9.x > > > The OpenShift web-ui provides a menu entry that creates the oc login command in your local clipboard: https://stackoverflow.com/questions/49548380/cannot-find-openshift-3-logi... > Currently, Eclipse users would have to paste it to some notepad and use the info in it to manually create a connection. The tooling could facilitate this by parsing the clipboard and creating a connection: > The Eclipse > There could be a button for parsing login command in clipboard. > Steps: > 1. User logins in web browser in OpenShift Console. > 2. User clicks on "Copy Login Command" > 3. In OpenShift tooling there could be button for parse login command from clipboard. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26204) Pod Log: empty console shows up when you use an oc whose path contains " "

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26204?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26204: ------------------------------------- Description: steps: # ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 # ASSERT: make sure you have an app with a pod running in OpenShift # EXEC: open OpenShift preferences and point it to an oc in a folder that contains spaces (ex. "~/oc binaries/3.41/oc") # EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." Result: The "Console" view shows up but nothing happens, there's no output. was: steps: # ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 # ASSERT: make sure you have an app with a pod running in OpenShift # EXEC: open OpenShift preferences and point it to a file that exist but is either not executable or simply not an oc binary # EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." Result: The "Console" view shows up but nothing happens, there's no output. > Pod Log: empty console shows up when you use an oc whose path contains " " > -------------------------------------------------------------------------- > > Key: JBIDE-26204 > URL: https://issues.jboss.org/browse/JBIDE-26204 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.9.0.AM1 > > > steps: > # ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 > # ASSERT: make sure you have an app with a pod running in OpenShift > # EXEC: open OpenShift preferences and point it to an oc in a folder that contains spaces (ex. "~/oc binaries/3.41/oc") > # EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." > Result: > The "Console" view shows up but nothing happens, there's no output. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25923) Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25923?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-25923: --------------------------------------- I would open new jira for this issue concerning wildfly server adapters. > Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over > ------------------------------------------------------------------------------------ > > Key: JBIDE-25923 > URL: https://issues.jboss.org/browse/JBIDE-25923 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.3.Final > Environment: Fedora, JBoss EAP 7.1, WildFly 11, 12 > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.6.0.AM1 > > Attachments: ServerAdapterEAP.gif, ServerAdapterEAPRepaired.gif > > > When there is specific maven project imported in Project explorer (jbosstools-openshift), Started EAP 7.1 server adapter is printing output where deployment scanner replaces deployment and redeploy over and over again, see part of log: > {code} > 15:35:15,824 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v1.xml" (runtime-name : "standalone.v1.xml") > 15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml") > 15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.v2.xml" (runtime-name: "standalone.v2.xml") > 15:35:20,856 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml") > 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.last.xml" (runtime-name : "standalone.last.xml") > 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v2.xml" (runtime-name : "standalone.v2.xml") > 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.xml" (runtime-name : "standalone.xml") > 15:35:25,951 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 20ms > 15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "standalone.v3.xml" (runtime-name: "standalone.v3.xml") > 15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml") > 15:35:25,957 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 2ms > 15:35:25,964 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml") > 15:35:26,037 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml" > 15:35:26,038 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v3.xml" (runtime-name : "standalone.v3.xml") > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26204) Pod Log: empty console shows up when you use an oc whose path contains " "

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26204?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26204: ------------------------------------- Summary: Pod Log: empty console shows up when you use an oc whose path contains " " (was: Pod Log: does not warn if you have a bogus (non executable, invalid) oc ) > Pod Log: empty console shows up when you use an oc whose path contains " " > -------------------------------------------------------------------------- > > Key: JBIDE-26204 > URL: https://issues.jboss.org/browse/JBIDE-26204 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.9.0.AM1 > > > steps: > # ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 > # ASSERT: make sure you have an app with a pod running in OpenShift > # EXEC: open OpenShift preferences and point it to a file that exist but is either not executable or simply not an oc binary > # EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." > Result: > The "Console" view shows up but nothing happens, there's no output. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23585) Integration tests global refactoring: org.jboss.tools.jsf.ui.bot.test

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23585?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-23585: --------------------------------------- PR merged long time ago. Could it be resolved? > Integration tests global refactoring: org.jboss.tools.jsf.ui.bot.test > --------------------------------------------------------------------- > > Key: JBIDE-23585 > URL: https://issues.jboss.org/browse/JBIDE-23585 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: integration, integration_tests, jsf > Fix For: 4.9.x > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.jsf.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23583) Integration tests global refactoring: org.jboss.tools.freemarker.ui.bot.test

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23583?page=com.atlassian.jira.plugi... ] Ondrej Dockal resolved JBIDE-23583. ----------------------------------- Assignee: Ondrej Dockal (was: Denis Golovin) Resolution: Done Because of freemarker ui.bot.itests removal in JBIDE-25052, we can close this issue as out of date. > Integration tests global refactoring: org.jboss.tools.freemarker.ui.bot.test > ---------------------------------------------------------------------------- > > Key: JBIDE-23583 > URL: https://issues.jboss.org/browse/JBIDE-23583 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Ondrej Dockal > Labels: freemarker, integration, integration_tests > Fix For: 4.9.x > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.freemarker.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26175) Cannot create server adapter for eap71-basic-s2i template from CDK

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26175?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26175: ------------------------------------------ JBIDE-22138 is linked to this issue in the sense that the bug found in JBIDE-22138 would affect us once we correct the path controller to use the module name instead of the hard coded "ROOT".war > Cannot create server adapter for eap71-basic-s2i template from CDK > ------------------------------------------------------------------ > > Key: JBIDE-26175 > URL: https://issues.jboss.org/browse/JBIDE-26175 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.6.0.Final > Environment: CDK: CDK v3.5.0-1 > Red Hat Developer Studio > Version: 12.0.0.GA > Build id: GA-v20180706-1014-B2970 > OS: Linux, v.4.17.3-200.fc28.x86_64, x86_64 / gtk 3.22.30, WebKit 2.20.3 > Java version: 1.8.0_172 > Reporter: Josef Kopriva > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: regression, upstream > Fix For: 4.9.0.AM1 > > > I was not able to create server adapter for eap71-basic-s2i template application. > Pod error log: > {code:java} > --> Scaling eap-app-1 down to zero > --> Scaling eap-app-2 to 1 before performing acceptance check > error: update acceptor rejected eap-app-2: pods for rc 'myproject/eap-app-2' took longer than 600 seconds to become available > {code} > Error log from OpenShift console: > {code:java} > Readiness probe failed: { > "probe.eap.dmr.EapProbe": { > "probe.eap.dmr.ServerStatusTest": "running", > "probe.eap.dmr.DeploymentTest": "Exception executing test: unorderable types: Status() < Status()", > "probe.eap.dmr.BootErrorsTest": [ > { > "failed-operation": { > "operation": "deploy", > "address": [ > { > "deployment": "kitchensink.war" > } > ] > }, > "failure-description": "{\"WFLYCTL0080: Failed services\" => {\"jboss.deployment.unit.\\\"kitchensink.war\\\".FIRST_MODULE_USE\" => \"WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \\\"kitchensink.war\\\"\n Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS\n Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\\\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\\\".statistics is already registered\"}}", > "failed-services": { > "jboss.deployment.unit.\"kitchensink.war\".FIRST_MODULE_USE": "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"kitchensink.war\"\n Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS\n Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\".statistics is already registered" > } > } > ] > } > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26213) Forge New and Noteworthy for 4.9.0.AM1

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26213?page=com.atlassian.jira.plugi... ] George Gastaldi closed JBIDE-26213. ----------------------------------- Resolution: Rejected No changes planned in this Sprint > Forge New and Noteworthy for 4.9.0.AM1 > --------------------------------------------------- > > Key: JBIDE-26213 > URL: https://issues.jboss.org/browse/JBIDE-26213 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > Labels: task > Fix For: 4.9.0.AM1 > > > George Gastaldi, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Forge JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Forge, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Forge by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26206 #comment Create N&N for Forge 4.9.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Forge for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 July 2018