[JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25050:
----------------------------------
Fix Version/s: 4.9.0.AM1
(was: 4.9.x)
> Prepare windows image with hyperv
> ---------------------------------
>
> Key: JBIDE-25050
> URL: https://issues.jboss.org/browse/JBIDE-25050
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.5.1.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Labels: jenkins
> Fix For: 4.9.0.AM1
>
> Attachments: error.log
>
>
> Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label.
> * Provision win10-x64-jbds (as some changes were made to jbds script)
> * Install manually HyperV in fresh windows image
> * Add new virtual switch
> * Set env. variable HYPERV_VIRTUAL_SWITCH
> * Add user into Hyper-V Administrators group
> * Test whether cdk can be run on the slave
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26159) Server adapter: debugging is not stopped if you delete the pod
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26159?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-26159:
-------------------------------------
Story Points: 4
> Server adapter: debugging is not stopped if you delete the pod
> --------------------------------------------------------------
>
> Key: JBIDE-26159
> URL: https://issues.jboss.org/browse/JBIDE-26159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Priority: Minor
> Labels: port_forwarding, server_adapter
> Fix For: 4.9.0.AM1
>
>
> steps:
> Screencast: https://youtu.be/XMA--S9zj6s
> # EXEC: create an application (via ex. nodejs-mongo-persistent template)
> # ASSERT: pod for service is running
> # EXEC: select pod and pick "Port Forwarding..." and start the forwarding
> # ASSERT: forwarding is running
> # EXEC: verify on the cmd-line that the forwarding is running
> {code}
> $ ps ax | grep oc
> 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
> {code}
> # EXEC: in Explorer: select the pod for your service and pick "Delete"
> # ASSERT: pod gets deleted and recreated
> # EXEC: verify on the cmd-line that the forwarding is running
> {code}
> $ ps ax | grep oc
> 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
> {code}
> Result:
> The port forwarding is still running.
> In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed).
> PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-26160:
-------------------------------------
Story Points: 4
> Server Adapter: erroneously stays in [Debugging] when you kill the pod
> ----------------------------------------------------------------------
>
> Key: JBIDE-26160
> URL: https://issues.jboss.org/browse/JBIDE-26160
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: server_adapter
> Fix For: 4.9.0.AM1
>
>
> steps:
> # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it
> # ASSERT: server adapter is created
> # EXEC: start the server adapter in Debugging
> # ASSERT: sever adapter is in *[Debugging, Synchronized]* state
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started
> # EXEC: in Explorer: select the pod for your service and pick "Delete"
> # ASSERT: pod gets deleted and recreated
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped
> Result:
> The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. The new pod is not running in debug (dev-) mode any more. To have it running again you need to restart the server adapter into debug, which will re-create a new pod in debug-mode.
> Expected result:
> Server adapter should get out of debugging and back into normal run mode *[Started, Synchronized]*.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26036) Update bundled minishift.yaml and write unit tests for both version of CDK stack yaml files
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26036?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-26036:
----------------------------------
Fix Version/s: 4.9.0.AM1
(was: 4.6.0.Final)
> Update bundled minishift.yaml and write unit tests for both version of CDK stack yaml files
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-26036
> URL: https://issues.jboss.org/browse/JBIDE-26036
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk
> Affects Versions: 4.6.0.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.9.0.AM1
>
>
> * Edit minishift.yaml file that resides in jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/resources to have corresponding content as jboss-stack/minishift.yaml file. We want to have the same content available when something fails to read stack's yaml file.
> * Add new openshift.cdk.server unit tests for stack file (minishift.yaml online and bundled one)
> * Update jboss-stack minishift.yaml (added 1.19 and 1.20)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26175) Cannot create server adapter for eap71-basic-s2i template from CDK
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26175?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-26175:
-------------------------------------
Story Points: 8
> 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
[JBoss JIRA] (JBIDE-26098) Repair org.jboss.tools.stacks test failures in jbosstools_base-master job
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26098?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-26098:
----------------------------------
Fix Version/s: 4.9.0.AM1
(was: 4.6.0.Final)
> Repair org.jboss.tools.stacks test failures in jbosstools_base-master job
> -------------------------------------------------------------------------
>
> Key: JBIDE-26098
> URL: https://issues.jboss.org/browse/JBIDE-26098
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: qa
> Affects Versions: 4.6.0.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.9.0.AM1
>
>
> 1. Have stacks tests to be run on jenkins jbt-base master and pull request job and have them green (not just omitting stacks tests results).
> 2. Update versions of maven plugins used as libraries in org.jboss.tools.stacks plugin:
> * org.jboss.jdf.stacks-client; 1.0.3.Final -> no change
> * org.yaml.snakeyaml; 1.10 -> 1.18
> * org.apache.httpcomponents.httpclient; 4.0.1 -> 4.5.5
> * org.apache.httpcomponents.httpcore; 4.0.1 -> 4.4.9
> * org.jboss.logging.jboss-logging; 3.1.2.GA -> 3.3.2.Final
> 3. Run all stacks.tests available (only one test class was run)
> 4. Check on dependencies and usages in org.jboss.jdf.stacks-client and org.jboss.tools.stacks (what needs to be update, does it broke something, what else is using it)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26175) Cannot create server adapter for eap71-basic-s2i template from CDK
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26175?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov reassigned JBIDE-26175:
----------------------------------------
Assignee: Dmitrii Bocharov (was: Andre Dietisheim)
> 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
[JBoss JIRA] (JBIDE-26175) Cannot create server adapter for eap71-basic-s2i template from CDK
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26175?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-26175:
-------------------------------------
Sprint: devex #152 July 2018
> 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