Deployment to OpenShift broken after latest update?
See original GitHub issueIts possible that I’m missing something, but from what I can tell something has changed in the latest version that causes deployment to OpenShift to break.
remote: npm WARN package.json slackin@0.8.1 No repository field.
remote: npm WARN package.json slackin@0.8.1 No license field.
remote: npm WARN deprecated lodash@1.0.2: lodash@<2.0.0 is no longer maintained. Upgrade to lodash@^3.0.0 ```
and
```remote: make: *** [Release/obj.target/validation/src/validation.o] Error 1
remote: gyp ERR! build error
remote: gyp ERR! stack Error: `make` failed with exit code: 2
remote: gyp ERR! stack at ChildProcess.onExit (/var/lib/openshift/569583602d5271d51f000088/app-root/data/.iojs/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
remote: gyp ERR! stack at emitTwo (events.js:87:13)
remote: gyp ERR! stack at ChildProcess.emit (events.js:172:7)
remote: gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
remote: gyp ERR! System Linux 2.6.32-573.12.1.el6.x86_64
remote: gyp ERR! command "/var/lib/openshift/569583602d5271d51f000088/app-root/data/.iojs/bin/iojs" "/var/lib/openshift/569583602d5271d51f000088/app-root/data/.iojs/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
remote: gyp ERR! cwd /var/lib/openshift/569583602d5271d51f000088/app-root/runtime/repo/node_modules/utf-8-validate
remote: gyp ERR! node -v v3.3.1
remote: gyp ERR! node-gyp -v v3.2.1
remote: gyp ERR! not ok
remote: npm WARN install:utf-8-validate@1.2.1 utf-8-validate@1.2.1 install: `node-gyp rebuild`
remote: npm WARN install:utf-8-validate@1.2.1 Exit status 1
remote:
remote: > slackin@0.8.1 postinstall /var/lib/openshift/569583602d5271d51f000088/app-root/runtime/repo
remote: > gulp
remote:
remote: [18:05:21] Requiring external module babel-core/register
remote: [18:05:22] Using gulpfile /var/lib/openshift/569583602d5271d51f000088/app-root/runtime/repo/gulpfile.babel.js
remote: fs.js:549
remote: return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
remote: ^
remote:
remote: Error: EACCES: permission denied, open '/var/lib/openshift/569583602d5271d51f000088/.babel.json'
remote: at Error (native)
remote: at Object.fs.openSync (fs.js:549:18)
remote: at Object.fs.writeFileSync (fs.js:1155:15)
remote: at save (/var/lib/openshift/569583602d5271d51f000088/app-root/runtime/repo/node_modules/babel-register/lib/cache.js:45:19)
remote: at doNTCallback0 (node.js:407:9)
remote: at process._tickCallback (node.js:336:13)
remote:
remote: npm WARN slackin@0.8.1 No repository field.
remote: npm WARN slackin@0.8.1 No license field.
remote: npm ERR! Linux 2.6.32-573.12.1.el6.x86_64
remote: npm ERR! argv "/var/lib/openshift/569583602d5271d51f000088/app-root/data/.iojs/bin/iojs" "/var/lib/openshift/569583602d5271d51f000088/app-root/data/.iojs/bin/npm" "i"
remote: npm ERR! node v3.3.1
remote: npm ERR! npm v3.5.3
remote: npm ERR! code ELIFECYCLE
remote: npm ERR! slackin@0.8.1 postinstall: 'gulp`
remote: npm ERR! Exit status 1
remote: npm ERR!
remote: npm ERR! Failed at the slackin@0.8.1 postinstall script 'gulp'.
remote: npm ERR! Make sure you have the latest version of node.js and npm installed.
remote: npm ERR! If you do, this is most likely a problem with the slackin package,
remote: npm ERR! not with npm itself.
remote: npm ERR! Tell the author that this fails on your system:
remote: npm ERR! gulp
remote: npm ERR! You can get information on how to open an issue for this project with:
remote: npm ERR! npm bugs slackin
remote: npm ERR! Or if that isn't available, you can get their info via:
remote: npm ERR! npm owner ls slackin
remote: npm ERR! There is likely additional logging output above.
remote:
remote: npm ERR! Please include the following file with any support request:
remote: npm ERR! /var/lib/openshift/569583602d5271d51f000088/app-root/runtime/repo/npm-debug.log
remote: CLIENT_RESULT: io.js modules installed.
remote: Preparing build for deployment
remote: Deployment id is fe4008e2
remote: Activating deployment
remote: CLIENT_MESSAGE: Starting io.js application...
remote: CLIENT_RESULT: Warning! Could not start io.js application!
remote: -------------------------
remote: Git Post-Receive Result: failure
remote: Activation status: failure
remote: Activation failed for the following gears:
remote: 569583602d5271d51f000088 (Error activating gear: CLIENT_ERROR: Failed to execute: 'control start' for /var/lib/openshift/569583602d5271d51f000088/iojs
remote: #<IO:0x000000025ee2d0>
remote: #<IO:0x000000025ee258>
remote: )
remote: Deployment completed with status: failure
remote: postreceive failed
To ssh://569583602d5271d51f000088@slackin-test.rhcloud.com/~/git/slackin.git/
+ 0bcc963...fcaae54 master -> master (forced update)
There is nothing in the /var/lib/openshift/569583602d5271d51f000088/app-root/runtime/repo/npm-debug.log
file, nor is there even a /var/lib/openshift
directory
Issue Analytics
- State:
- Created 8 years ago
- Comments:10
Top Results From Across the Web
1768260 – Could not update deployment "openshift-console ...
Cause: Failure to roll-out deployment during updates was logged only in CVO logs ... Fix: The CVO now exposes underlying error to roll-out...
Read more >Troubleshooting installations | OpenShift Container Platform 4.9
When troubleshooting OpenShift Container Platform installation issues, you can monitor installation logs to determine at which stage issues occur. Then, ...
Read more >Troubleshooting Guide for OpenShift Container Platform
Pod related issues. Router/Registry Not deploying to correct node · Issues with Nodes. Nodes being reported as ready, but builds failing · Registry...
Read more >Plugin update on fresh Jenkins deployment on Openshift ...
Reported issue Restarting a fresh Jenkins instance on Openshift Online after a plugin update results in a broken installation.
Read more >Managing rolling deployments to update your apps - IBM Cloud
You can create the new version: green deployment, wait until it is ready, and then delete the version: blue deployment. Or you can...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This can be fixed with the following command:
rhc env-set -a slackin BABEL_CACHE_PATH=“/var/lib/openshift/{instance}/app-root/repo/.cache/.babel.json”
Might be a more elegant way to do it to grab the path in an automated way, but that should fix that error.
@nsvrana reverting back to 0.7.3 fixed it for me as well.