Prevent the nodejs applications restarting on every Chef run #5
Labels
No Label
service
accounts
service
discourse
service
drone-ci
service
email
service
garage
service
gitea
service
ipfs
service
mastodon
service
postgres
service
remotestorage
service
wiki
service
xmpp
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/chef#5
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It is the
application_npm_install
resources that are causing the nodejs services to be restarted on every Chef runI have reported the issue upstream: https://github.com/poise/poise-javascript/issues/9 but no response. We need to find a way to use this unreleased version that fixes it (it's distributed as a gem that's a dependency in the application_javascript cookbook)
It would seem that
poise-javascript
is dead now.All the application/poise projects are dead, the maintainer isn't working on them anymore. I'm currently taking a look at Chef's new app build/deployment/management system, Habitat, that looks very interesting: https://www.habitat.sh
I have started from the unreleased master branch of poise-javascript (
rake chef:build
). That includes a change that supports the new behavior ofnpm install
, writing "up to date" to stdout when no changes have been performed.However,
npm install
now runs security auditing by default, even with the--production
switch, so even the newer version of poise-javascript still causes the service to restartI have then added the
--no-audit
switch to prevent the service from restart at every run, caused by the output of thenpm install
command missing the "up to date" string, and pushed that to a new repo:d85078fe59
.I'm going to do a PR to use that repo in our Berksfile, that works great in a VM
This happened again just now. I changed an env var for hal8000, but botka still restarted.
It can be any of the resources inside of the application resource, I'm checking what's causing it
I can't reproduce the issue in a VM, but I can confirm it still happens on barnard. Subresources of the application resource aren't updating, but still the service restarts. Logs:
Not high priority, to investigate more later
This is not an issue anymore, confirmed after working on #104 and running Chef multiple times