Actions
Bug #10986
closedwebapp can't start after upgrade to 4.2
Bug #10986:
webapp can't start after upgrade to 4.2
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
13
Name check:
Fix check:
Regression:
Description
This is a template, please edit and remove what is not relevant.
I found this bug in Rudder version 4.2, on xenial
This bug happens:
- During upgrade of Rudder server
Description:
[2017-06-22 09:15:06] INFO bootchecks - Resume policy update if it was running before shutdown
[2017-06-22 09:15:06] INFO bootchecks - Flag file '/opt/rudder/etc/policy-update-running' does not exist, No need to start a new policy update
[2017-06-22 09:15:06] INFO bootchecks - Check that system group / directive / rules for Rudder 4.2 are agent-specific
[2017-06-22 09:15:06] ERROR bootchecks - Missing required system entry in bootstrap data (likely a bug, please report): 'nodeGroupId=all-nodes-with-cfengine-agent,groupCategoryId=SystemGroup
s,groupCategoryId=GroupRoot,ou=Rudder,cn=rudder-configuration'
[2017-06-22 09:15:06] ERROR application - Fatal error during boot, Rudder will stop now
javax.servlet.UnavailableException: Missing required system entry in bootstrap data (likely a bug, please report): 'nodeGroupId=all-nodes-with-cfengine-agent,groupCategoryId=SystemGroups,gro
upCategoryId=GroupRoot,ou=Rudder,cn=rudder-configuration'
at bootstrap.liftweb.checks.CheckCfengineSystemRuleTargets.FAIL(CheckCfengineSystemRuleTargets.scala:112)
at bootstrap.liftweb.checks.CheckCfengineSystemRuleTargets.failMissingEntryMsg$1(CheckCfengineSystemRuleTargets.scala:130)
at bootstrap.liftweb.checks.CheckCfengineSystemRuleTargets.$anonfun$checks$3(CheckCfengineSystemRuleTargets.scala:135)
Actions