Debug vagrant provisioning failure #15
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The script was writing "${DISTRO}" as-is in
/etc/apt/sources.list.d/nodesource.list, which prevented the system from
installing node.
The installation failed when installing Django 1.9 because six was not
automatically upgraded:
django-rest-swagger==0.3.6 : pkg_resources.VersionConflict: (six
1.5.2 (/usr/lib/python3/dist-packages),
Requirement.parse('six>=1.10.0'))
Fix this by upgrading six by hand.
Moreover Django wants debug_toolbar.middleware.DebugToolbarMiddleware
into its MIDDLEWARE apps, as
ProjetSigma/backend@37fc065
did in some branch of the backend. Otherwise Django was complaining:
==> default: + python3 manage.py migrate
==> default: SystemCheckError: System check identified some issues:
==> default:
==> default: ERRORS:
==> default: ?: debug_toolbar.middleware.DebugToolbarMiddleware is
missing from MIDDLEWARE_CLASSES.
==> default: HINT: Add
debug_toolbar.middleware.DebugToolbarMiddleware to
MIDDLEWARE_CLASSES.
The Node package from Ubuntu 14.04 is too old so install Node 5 when running "apt-get install -yqq nodejs". Moreover do not install npm as it is provided by nodejs package.
In order to make it easier to find bugs/failures, stop the provisionning as soon as an error happens.
|
Oui, vagrant marche pas bien. Les gens ont abandonné. Mais un bon virtualenv fait l'affaire. J'ai quitté le projet, mais je peux toujours t'aider si tu le souhaites ;)
Et je peux t'ajouter au groupe slack, même si je ne sais pas s'il est toujours actif
Le 24 janv. 2017 00:01, Nicolas Iooss <[email protected]> a écrit :
Hello,
As I would like to see what ProjetSigma look like, I am looking forward to build a virtual machine with it. Currently the provided Vagrant configuration file fails in several places and this Pull Request fixes some of them. With it, there is one last failure I do not understand, when running npm install --loglevel=info as user vagrant in /vagrant/frontend:
[22:54:48] Requiring external module ts-node/register TSError: ⨯ Unable to compile TypeScript src/shared/services/api-service.ts (7,23): Cannot find module '../../config'. (2307) src/shared/services/auth-service.ts (3,23): Cannot find module '../../config'. (2307) at getOutput (/vagrant/frontend/node_modules/ts-node/src/ts-node.ts:210:13) at Object.loader (/vagrant/frontend/node_modules/ts-node/src/ts-node.ts:225:23) at Module.load (module.js:357:32) at Function.Module._load (module.js:314:12) at Module.require (module.js:367:17) at require (internal/module.js:20:19) at Liftoff.handleArguments (/vagrant/frontend/node_modules/gulp/bin/gulp.js:116:3) at Liftoff.<anonymous> (/vagrant/frontend/node_modules/liftoff/index.js:198:16) at module.exports (/vagrant/frontend/node_modules/flagged-respawn/index.js:17:3) at Liftoff.<anonymous> (/vagrant/frontend/node_modules/liftoff/index.js:190:9) npm info lifecycle [email protected]~postinstall: Failed to exec postinstall script npm WARN optional Skipping failed optional dependency /chokidar/fsevents: npm WARN notsup Not compatible with your operating system or architecture: [email protected] npm ERR! Linux 3.13.0-107-generic npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "--loglevel=info" npm ERR! node v5.12.0 npm ERR! npm v3.8.6 npm ERR! code ELIFECYCLE npm ERR! [email protected] postinstall: `typings install && gulp check.versions && npm prune` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] postinstall script 'typings install && gulp check.versions && npm prune'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the sigma package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! typings install && gulp check.versions && npm prune npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs sigma npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls sigma npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /vagrant/frontend/npm-debug.log
I do not understand this error so any hint about what would have gone wrong would be appreciated :)
Cheers!
…_____________________________________________
You can view, comment on, or merge this pull request online at:
#15
Commit Summary
Use double quote to fill /etc/apt/sources.list.d/nodesource.listFix Django installationapt-get update before installing Node 5Add set -x -e to provisionning script
File Changes
M vagrant_bootstrap.sh (18)
Patch Links:
https://github.com/ProjetSigma/provisioning/pull/15.patchhttps://github.com/ProjetSigma/provisioning/pull/15.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
As I would like to see what ProjetSigma look like, I am looking forward to build a virtual machine with it. Currently the provided Vagrant configuration file fails in several places and this Pull Request fixes some of them. With it, there is one last failure I do not understand, when running
npm install --loglevel=infoas uservagrantin/vagrant/frontend:I do not understand this error so any hint about what would have gone wrong would be appreciated :)
Cheers!