Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rhoar-nodejs/nodejs-10 nodejs component is failing silently on openshift 3.11 cluster #2361

Closed
girishramnani opened this issue Nov 5, 2019 · 7 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@girishramnani
Copy link
Contributor

rhoar-nodejs/nodejs-10 based nodejs component is failing silently on 3.11 cluster with logs

2019/11/05 09:46:43 [go-init] No pre-start command defined, skip
2019/11/05 09:46:43 [go-init] Main command launched : /opt/odo/bin/supervisord -c /opt/odo/conf/supervisor.conf
time="2019-11-05T09:46:43Z" level=info msg="create process:run" 
time="2019-11-05T09:46:43Z" level=info msg="try to start program" program=run 
+ set -eo pipefail
+ echo 'Setting up'
+ /opt/odo/bin/s2i-setup
time="2019-11-05T09:46:43Z" level=info msg="success to start program" program=run 
Setting up
+ set -eo pipefail
+ mkdir -p /tmp
+ touch /tmp/.dummy
+ mkdir -p /tmp/src/
+ touch /tmp/src/.dummy
+ [[ /tmp != *\/\s\r\c* ]]
+ mkdir -p /tmp/src
+ touch /tmp/src/.dummy
+ mkdir -p /opt/app-root/src
+ echo Running
+ /opt/odo/bin/run
Running
+ set -eo pipefail
+ export ODO_UTILS_DIR=/opt/odo
+ ODO_UTILS_DIR=/opt/odo
+ export ODO_IMAGE_MAPPINGS_FILE=/opt/odo/language-scripts/image-mappings.json
+ ODO_IMAGE_MAPPINGS_FILE=/opt/odo/language-scripts/image-mappings.json
++ /opt/odo/bin/getlanguage
+ IMAGE_LANG=nodejs
+ '[' -f /tmp/.s2i/bin/run ']'
+ '[' '!' -z nodejs ']'
+ exec /opt/odo/language-scripts/nodejs/dev-run
+ DEBUG_MODE=true
+ '[' true == true ']'
+ export DEV_MODE=true
+ DEV_MODE=true
+ '[' -z '' ']'
+ '[' true == true ']'
+ export NODE_ENV=development
+ NODE_ENV=development
+ '[' development == production ']'
+ export DEV_MODE=true
+ DEV_MODE=true
++ id -u
+ USER_ID=1013360000
++ id -g
+ GROUP_ID=0
+ '[' x1013360000 '!=' x0 -a x1013360000 '!=' x1001 ']'
+ NSS_WRAPPER_PASSWD=/opt/app-root/etc/passwd
+ NSS_WRAPPER_GROUP=/etc/group
+ cat /etc/passwd
+ sed -e 's/^default:/builder:/'
+ echo 'default:x:1013360000:0:Default Application User:/opt/app-root/src:/sbin/nologin'
+ export NSS_WRAPPER_PASSWD
+ export NSS_WRAPPER_GROUP
+ LD_PRELOAD=libnss_wrapper.so
+ export LD_PRELOAD
+ '[' development == production ']'
+ export DEV_MODE=true
+ DEV_MODE=true
+ set -x
+ export GIT_COMMITTER_NAME=unknown
+ GIT_COMMITTER_NAME=unknown
+ export and GIT_COMMITTER_EMAIL=unknown@localhost.com
+ GIT_COMMITTER_EMAIL=unknown@localhost.com
+ git --version
git version 2.9.3
+ '[' '' == --debug ']'
+ run_node
++ node --version
+ echo -e 'Using Node.js version: v10.12.0'
Using Node.js version: v10.12.0
Environment: 
	DEV_MODE=true
	NODE_ENV=development
	DEBUG_PORT=5858
+ echo -e 'Environment: \n\tDEV_MODE=true\n\tNODE_ENV=development\n\tDEBUG_PORT=5858'
++ id
Running as user uid=1013360000(default) gid=0(root) groups=0(root),1013360000
Launching via nodemon...
+ echo -e 'Running as user uid=1013360000(default) gid=0(root) groups=0(root),1013360000'
+ '[' true == true ']'
+ echo 'Launching via nodemon...'
+ exec npx nodemon --inspect=5858
time="2019-11-05T09:46:44Z" level=debug msg="wait program exit" program=run 
  Usage: nodemon [nodemon options] [script.js] [args]

  See "nodemon --help" for more.

time="2019-11-05T09:46:57Z" level=info msg="program stopped with status:exit status 0" program=run 
time="2019-11-05T09:46:57Z" level=info msg="Don't start the stopped program because its autorestart flag is false" program=run 

The important line here is

+ exec npx nodemon --inspect=5858
time="2019-11-05T09:46:44Z" level=debug msg="wait program exit" program=run 
  Usage: nodemon [nodemon options] [script.js] [args]

seems like nodemon cannot understand --inspect flag anymore

@amitkrout
Copy link
Contributor

amitkrout commented Nov 5, 2019

@girishramnani Can you please point out which test scenario is failing or if you found it while doing a manual run please provide the execution steps

@kadel kadel added the kind/bug Categorizes issue or PR as related to a bug. label Dec 3, 2019
@girishramnani
Copy link
Contributor Author

This hasn't been reproducible recently hence closing.

@kadel
Copy link
Member

kadel commented Feb 13, 2020

/kind s2i

@girishramnani girishramnani reopened this on Jan 13

@girishramnani why was this reopened? Is this still an issue?

@openshift-ci-robot
Copy link
Collaborator

@kadel: The label(s) kind/s2i cannot be applied, because the repository doesn't have them

In response to this:

/kind s2i

@girishramnani girishramnani reopened this on Jan 13

@girishramnani why was this reopened? Is this still an issue?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kadel
Copy link
Member

kadel commented Feb 13, 2020

/area s2i

@girishramnani
Copy link
Contributor Author

Yes, let me find the logs. It was reported by an external user

@girishramnani
Copy link
Contributor Author

girishramnani commented Apr 2, 2020

I dont see this happening now, so closing this issue. if it fails then it can be reopened

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

4 participants