[JBoss JIRA] (JBIDE-25830) After starting CDK server adapter OpenShift Connection does not work when oc is not on path
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25830?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25830:
-------------------------------------
Sprint: devex #155 September 2018
> After starting CDK server adapter OpenShift Connection does not work when oc is not on path
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-25830
> URL: https://issues.jboss.org/browse/JBIDE-25830
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk, openshift
> Affects Versions: 4.5.3.AM3
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Labels: cdk_server_adapter, connection
> Fix For: 4.9.0.Final
>
> Attachments: edit-connection-advanced.png
>
>
> OpenShift connection should be working, when user starts CDK server adapter, even if you do not have oc on path. In my opinion OpenShift connection should be working "out of box" when user starts CDK server adapter.
> steps:
> # ASSERT: oc is not on path
> # EXEC: Start CDK server adapter
> # ASSERT: OpenShift connection is created, but does not fully work (all oc related operations wont)
> Error: oc is not set for OpenShift connection to CDK and OpenShift connection does not work.
> Expected: OpenShift connection should be working without user touch.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 10 months
[JBoss JIRA] (JBIDE-25830) After starting CDK server adapter OpenShift Connection does not work when oc is not on path
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25830?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-25830:
----------------------------------------
Assignee: Andre Dietisheim (was: Rob Stryker)
> After starting CDK server adapter OpenShift Connection does not work when oc is not on path
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-25830
> URL: https://issues.jboss.org/browse/JBIDE-25830
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk, openshift
> Affects Versions: 4.5.3.AM3
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Labels: cdk_server_adapter, connection
> Fix For: 4.9.0.Final
>
> Attachments: edit-connection-advanced.png
>
>
> OpenShift connection should be working, when user starts CDK server adapter, even if you do not have oc on path. In my opinion OpenShift connection should be working "out of box" when user starts CDK server adapter.
> steps:
> # ASSERT: oc is not on path
> # EXEC: Start CDK server adapter
> # ASSERT: OpenShift connection is created, but does not fully work (all oc related operations wont)
> Error: oc is not set for OpenShift connection to CDK and OpenShift connection does not work.
> Expected: OpenShift connection should be working without user touch.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 10 months
[JBoss JIRA] (JBIDE-26334) Launcher wizard: improve user experience
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26334?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26334:
-------------------------------------
Story Points: 8
> Launcher wizard: improve user experience
> ----------------------------------------
>
> Key: JBIDE-26334
> URL: https://issues.jboss.org/browse/JBIDE-26334
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: launcher_wizard
> Fix For: 4.9.0.Final
>
> Attachments: error-markers-for-missing-info.png, maven-artifact-elements.png, mission-infos.png
>
>
> The launcher wizard that we implemented in 4.9.AM3 works but it lacks explanations that would help a novice user.
> Suggested improvements:
> * A novice user has no idea what a mission is all about. We should maybe add an explanatory label that tells the user what he's picking with a mission. And then we should explain what the mission that he has chose will provide.
> !mission-infos.png!
> * A novice user has no idea what the maven artifact elements are for.
> !maven-artifact-elements.png!
> * Generally speaking it is preferable to decorate missing input fields with a "*" than to mark them as errors (as one can see in most web forms). OpenShift tooling does this as a rule of thumb.
> !error-markers-for-missing-info.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 10 months
[JBoss JIRA] (JBIDE-26306) Server adapter: deleting server adapter after project causes NPE
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26306?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-26306:
------------------------------------
[~adietish] isn't it a duplicate of JBIDE-26327
> Server adapter: deleting server adapter after project causes NPE
> -----------------------------------------------------------------
>
> Key: JBIDE-26306
> URL: https://issues.jboss.org/browse/JBIDE-26306
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM1
> Reporter: Andre Dietisheim
> Labels: server_adapter
> Fix For: 4.9.x
>
> Attachments: image-2018-08-14-11-57-17-905.png
>
>
> steps:
> # ASSERT: have an application running in OpenShift that you created via the eap70-basic-s2i template
> # ASSERT: have the project imported into workspace, have the server adapter created for it
> # EXEC: delete the project in workspace
> # EXEC: delete the server (have it stopped before being deleted - the checkbox checked for this sake)
> Result:
> Error dialog reports an NPE
> !image-2018-08-14-11-57-17-905.png!
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftShutdownController.updateProject(OpenShiftShutdownController.java:71)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftShutdownController.stop(OpenShiftShutdownController.java:58)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.stop(ControllableServerBehavior.java:255)
> at org.eclipse.wst.server.core.internal.Server.stopImpl2(Server.java:3698)
> at org.eclipse.wst.server.core.internal.Server.stopImpl(Server.java:3655)
> at org.eclipse.wst.server.core.internal.Server$StopJob.run(Server.java:413)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 10 months
[JBoss JIRA] (JBIDE-26098) Update dependencies in org.jboss.tools.stacks and repair 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:
----------------------------------
Sprint: devex #151 June 2018, devex #154 September 2018, devex #155 September 2018 (was: devex #151 June 2018, devex #154 September 2018)
> Update dependencies in org.jboss.tools.stacks and repair 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.x
>
>
> 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)
5 years, 10 months
[JBoss JIRA] (JBIDE-26355) Fuse on openshift project does not work on CDK CDK v3.6.0-alpha.2-1
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26355?page=com.atlassian.jira.plugi... ]
Josef Kopriva edited comment on JBIDE-26355 at 9/12/18 7:22 AM:
----------------------------------------------------------------
[~jeffmaury] thx for pointing out - moving to CDK
was (Author: jkopriva):
[~jeffmaury] thx for pointing out - moving to FUSETOOLS
> Fuse on openshift project does not work on CDK CDK v3.6.0-alpha.2-1
> -------------------------------------------------------------------
>
> Key: JBIDE-26355
> URL: https://issues.jboss.org/browse/JBIDE-26355
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Environment: F28
> CDK v3.6.0-alpha.2-1
> Red Hat Developer Studio
> Version: 12.9.0.AM3
> Build id: AM3-v20180906-1322-B3331
> Build date: 20180906-1322
> Reporter: Josef Kopriva
>
> I have tried to reproduce JIRA https://issues.jboss.org/browse/JBIDE-25303 , but during deploy to OpenShift on CDK I get an error.
> Full log of build:
> {code:java}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model for org.mycompany:camel-ose-springboot-xml:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.springframework.boot:spring-boot-maven-plugin @ line 172, column 15
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
> [WARNING]
> [INFO]
> [INFO] ---------------< org.mycompany:camel-ose-springboot-xml >---------------
> [INFO] Building Fabric8 :: Quickstarts :: Spring-Boot :: Camel XML 1.0.0-SNAPSHOT
> [INFO] --------------------------------[ jar ]---------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ camel-ose-springboot-xml ---
> [INFO] Deleting /home/jkopriva/fuse-on-openshift/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ camel-ose-springboot-xml ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- fabric8-maven-plugin:3.1.80.redhat-000019:resource (default) @ camel-ose-springboot-xml ---
> [INFO] F8: Running in OpenShift mode
> [INFO] F8: Using docker image name of namespace: myproject
> [INFO] F8: spring-boot: Using fat jar packaging as the spring boot plugin is using `repackage` goal execution
> [INFO] F8: Running generator spring-boot
> [INFO] F8: spring-boot: Using Docker image fabric8/s2i-java as base / builder
> [INFO] F8: Using resource templates from /home/jkopriva/fuse-on-openshift/src/main/fabric8
> 2018-09-10 14:36:03 INFO Version:30 - HV000001: Hibernate Validator 5.2.4.Final
> [INFO] F8: fmp-service: Adding a default Service with ports [8080]
> [INFO] F8: spring-boot-health-check: Adding readiness probe on port 8081, path='/health', with initial delay 10 seconds
> [INFO] F8: spring-boot-health-check: Adding liveness probe on port 8081, path='/health', with initial delay 180 seconds
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [INFO]
> [INFO] --- maven-compiler-plugin:3.6.0:compile (default-compile) @ camel-ose-springboot-xml ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 2 source files to /home/jkopriva/fuse-on-openshift/target/classes
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ camel-ose-springboot-xml ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory /home/jkopriva/fuse-on-openshift/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.6.0:testCompile (default-testCompile) @ camel-ose-springboot-xml ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ camel-ose-springboot-xml ---
> [INFO] No tests to run.
> [INFO]
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ camel-ose-springboot-xml ---
> [INFO] Building jar: /home/jkopriva/fuse-on-openshift/target/camel-ose-springboot-xml-1.0.0-SNAPSHOT.jar
> [INFO]
> [INFO] --- spring-boot-maven-plugin:1.4.1.RELEASE:repackage (default) @ camel-ose-springboot-xml ---
> [INFO]
> [INFO] >>> fabric8-maven-plugin:3.1.80.redhat-000019:build (default) > initialize @ camel-ose-springboot-xml >>>
> [INFO]
> [INFO] <<< fabric8-maven-plugin:3.1.80.redhat-000019:build (default) < initialize @ camel-ose-springboot-xml <<<
> [INFO]
> [INFO]
> [INFO] --- fabric8-maven-plugin:3.1.80.redhat-000019:build (default) @ camel-ose-springboot-xml ---
> [INFO] F8: Using OpenShift build with strategy S2I
> [INFO] F8: spring-boot: Using fat jar packaging as the spring boot plugin is using `repackage` goal execution
> [INFO] F8: Running generator spring-boot
> [INFO] F8: spring-boot: Using Docker image fabric8/s2i-java as base / builder
> [INFO] Copying files to /home/jkopriva/fuse-on-openshift/target/docker/camel-ose-springboot-xml/latest/build/maven
> [INFO] Building tar: /home/jkopriva/fuse-on-openshift/target/docker/camel-ose-springboot-xml/latest/tmp/docker-build.tar
> [INFO] F8: [camel-ose-springboot-xml:latest] "spring-boot": Created docker source tar /home/jkopriva/fuse-on-openshift/target/docker/camel-ose-springboot-xml/latest/tmp/docker-build.tar
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 18.250 s
> [INFO] Finished at: 2018-09-10T14:36:19+02:00
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal io.fabric8:fabric8-maven-plugin:3.1.80.redhat-000019:build (default) on project camel-ose-springboot-xml: Execution default of goal io.fabric8:fabric8-maven-plugin:3.1.80.redhat-000019:build failed: An error has occurred. timeout: Socket closed -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> {code}
> I have also tried this project with oc cluster up(version 3.9.0) and it went without errors.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 10 months