openshift-labs / learn-katacoda

The OpenShift learning portal, powered by Katacoda
https://learn.openshift.com
159 stars 267 forks source link

Messaging with OpenShift and Red Hat AMQ #1298

Closed ignatovich closed 2 years ago

ignatovich commented 2 years ago

In which scenario did this bug occur?

Name the katacoda you were using

At what step of the scenario did this happen?

If you can't remember the exact step, try to explain where in the scenario did the bug happen

Describe the bug

A clear and concise description of what the bug is

Logs or error messages

Paste in any error message you got

Screenshots

If applicable, add screenshots to help explain your problem

Additional context

Add any other context about the problem

ignatovich commented 2 years ago

In which scenario did this bug occur?

Messaging with OpenShift and Red Hat AMQ

At what step of the scenario did this happen?

step 3/4 section Deploy Build and deploy the project using the following command: npm run openshift Describe the bug

error messages on console in the command results

Logs or error messages

$ npm run openshift

amq-js-demo@1.0.0 openshift /root/projects/amq-examples/amq-js-demo nodeshift --strictSSL=false --dockerImage=registry.access.redhat.com/rhoar-nodejs/nodejs-8 --tryServiceAccount=false

2021-09-03T13:08:02.605Z INFO loading configuration 2021-09-03T13:08:02.643Z INFO using namespace messaging at https://openshift:6443 2021-09-03T13:08:02.644Z WARNING a file property was not found in your package.json, archiving the current directory. 2021-09-03T13:08:02.647Z INFO creating archive of amq-broker.yaml, app.js, package-lock.json, package.json 2021-09-03T13:08:02.726Z INFO creating build configuration amq-js-demo-s2i 2021-09-03T13:08:02.726Z INFO Using the Source Build Strategy 2021-09-03T13:08:02.727Z INFO Using s2i image registry.access.redhat.com/rhoar-nodejs/nodejs-8 with tag latest 2021-09-03T13:08:02.773Z INFO creating ImageStream amq-js-demo 2021-09-03T13:08:02.794Z INFO uploading binary archive /root/projects/amq-examples/amq-js-demo/tmp/nodeshift/build/archive.tar 2021-09-03T13:08:19.467Z ERROR {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Internal error occurred: unable to upgrade connection: Unauthorized","reason":"InternalError","details":{"causes":[{"message":"unable to upgrade connection: Unauthorized"}]},"code":500}

2021-09-03T13:08:19.467Z ERROR Status code 500 npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! amq-js-demo@1.0.0 openshift: nodeshift --strictSSL=false --dockerImage=registry.access.redhat.com/rhoar-nodejs/nodejs-8 --tryServiceAccount=false npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the amq-js-demo@1.0.0 openshift script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2021-09-03T13_08_19_496Z-debug.log $ Screenshots

If applicable, add screenshots to help explain your problem

Additional context

Add any other context about the problem