openshift-roadshow / nationalparks Goto Github PK

• we should add the following annotation to the pipeline template to make it display better in the UI:

pipeline.alpha.openshift.io/uses: '[{"name": "nationalparks", "namespace": "", "kind": "DeploymentConfig"},{"name": "nationalparks-live", "namespace": "", "kind": "DeploymentConfig"}]'

When ever I setup to application, I get no issues from OpenShift. However, when I go to route to bring up the webpage I get the following error. I have tried this on multiple machines with the same result.

Whitelabel Error Page
This application has no explicit mapping for /error, so you are seeing this as a fallback.

Thu Jun 18 17:59:56 UTC 2020
There was an unexpected error (type=Not Found, status=404).
No message available

Tekton Task on IBM ROKS with this error:

Writing manifest to image destination
Storing signatures
STEP 2: LABEL "io.openshift.s2i.build.image"="registry.access.redhat.com/openjdk/openjdk-11-rhel7" "io.openshift.s2i.build.source-location"="."
error building at STEP "LABEL "io.openshift.s2i.build.image" "registry.access.redhat.com/openjdk/openjdk-11-rhel7" "io.openshift.s2i.build.source-location" "."": error ensuring container path "/home/jboss": lstat /var/lib/containers/storage/overlay/a4ada3ad6f4db47580a5d5d08981f8f9472fad319dd53037dcd0eb8ecb354444/merged/home: invalid argument
STEP-PUSH

This is due a bug in buildah on OpenShift RHEL 7 kernels (worker nodes) when a PVC is used.

Other References:
containers/buildah#2198
openshift/pipelines-tutorial#66

workaround is to add --storage-driver=vfs to buildah steps inside s2i-java-11-binary Task

I got a build error once I followed below commands in OCP3.3
oc new-project roadshow
oc policy add-role-to-user view system:serviceaccount:roadshow:default
oc create -f ./ose3/application-template.json
oc new-app nationalparks

error: build error: unable to get jorgemoralespou/s2i-java@sha256:bd7903c84ea2bd05a01b7d0515f8262dfac9dd26ad36d870f0154edb06ed2f70

Is that a known issue or something I missed?

Friendly notification: see https://github.com/openshift/jenkins-plugin#openshift-v3-plugin-for-jenkins

The plugin will not be supported in releases after 3.11, and will be removed from the openshift jenkins image during the 4.0 development cycle.

This repo has usage of the DSL from that plugin.

Switch to the DSL from the jenkins client plugin at https://github.com/openshift/jenkins-client-plugin

Pipelines Operator comes along with Tekton Triggers: v0.8.1 and use a new format to map parameters

$(tt.params.<name>)

We need to update TriggerTemplate accordingly.

Thanks to Alejandro Quirós Pascual for reporting it!

It looks like Google's Maven image used in the Java pipeline is shipping JDK 8 in latest tag.

One solution is to use explicitly the new tag 3.9.1

https://github.com/rhpds/agnosticv/issues/9434

The shell script is just a curl to the all endpoint, but never involves loading the data into the database. If someone does labs out of order or never loads the data, this test will always fail.

It's also a little odd that the dev and "live" apps are both using the same database, but that's not as big of a concern.

One option would be to modify the test script to hit the load before hitting all.

@siamaksade

Do I need to update the Docker image?

Giri Venkataraman discovered this issue when using Tekton ClusterTask Maven:

*[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:2.6:jar (default-jar) on project
nationalparks: Execution default-jar of goal
org.apache.maven.plugins:maven-jar- plugin:2.6:jar failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-jar-plugin:2.6:jar:
java.lang.ExceptionInInitializerError: null*

Proposed fix is to use Maven JAR plugin

it would be nice if the app didn't crash if the database isn't available.

This way the map name will populate into web-parksmap, but just no data points.

Pipeline is annotated with both Dev and Live deploymentconfigs and therefore it is displayed twice in the console:

pipeline.alpha.openshift.io/uses: '[{"name": "nationalparks-dev", "namespace": "", "kind": "DeploymentConfig"},{"name": "nationalparks-live", "namespace": "", "kind": "DeploymentConfig"}]'

Pipeline visualization in its current form attached to either of them does not make much sense. We should probably remove the annotations and just show the pipeline in Builds → Pipelines

redhat-scholars/openshift-starter-guides#1
redhat-scholars/openshift-starter-guides#4

Right now the REST endpoints don't work without a trailing / when invoking them:

http://localhost:8080/ws/healthz/
http://localhost:8080/ws/info/

We want to support the request also without that, because it is often source of errors:

http://localhost:8080/ws/healthz
http://localhost:8080/ws/info

Hello.

I am having trouble with building from the git repo and I get the errors:

[ERROR]     'dependencies.dependency.version' for org.springframework.cloud:spring-cloud-context:jar is missing. @ line 69, column 21
[ERROR] 
[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/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/ModelParseException
error: build error: error building at STEP "RUN /usr/local/s2i/assemble": error while running runtime: exit status 1

It seems like the build fails becuase of the step with RUN /usr/local/s2i/assemble failing.

Any thoughts on how to fix this?

Pipeline Operator 1.0.1 is fine with name:, we need to update it to ref for 1.1.2

[DEBUG] getAllParks
[DEBUG] MongoDBConnection.getAll()
2016-11-23 16:22:08.914  INFO 1 --- [nio-8080-exec-1] org.mongodb.driver.connection            : Opened connection [connectionId{localValue:2, serverValue:33}] to mongodb:27017
[INFO] load()
[DEBUG] MongoDBConnection.loadParks()
[DEBUG] MongoDBConnection.loadParks(InputStream)
[INFO] load()
[DEBUG] MongoDBConnection.loadParks()
[DEBUG] MongoDBConnection.loadParks(InputStream)
[DEBUG] MongoDBConnection.init(...)
[DEBUG] MongoDBConnection.init(...)
2016-11-23 16:22:18.588  INFO 1 --- [nio-8080-exec-3] org.mongodb.driver.connection            : Opened connection [connectionId{localValue:3, serverValue:38}] to mongodb:27017
[INFO] load()
[DEBUG] MongoDBConnection.loadParks()
[DEBUG] MongoDBConnection.loadParks(InputStream)
[DEBUG] MongoDBConnection.init(...)
[DEBUG] getAllParks
[DEBUG] MongoDBConnection.getAll()

In the app:

Items inserted in database: 5480

The list comes from 2016, we need to update it with latest entries from ProtectedPlanet database. The filtering will be done following NPS official units to pick right categories under National Park nomenclature