Bug #7336
closed
Node stuck in "Applying" status
Added by Jonathan CLARKE over 8 years ago.
Updated almost 8 years ago.
Category:
Web - Compliance & node report
Description
I changed a couple of Directives earlier today, and they have been successfully applied to all concerned nodes, except for one.
That particular node is in 100% Applying status:
However, I discovered ("thanks" to this problem) that the agent is not running on that particular node, so it has neither sent an inventory nor any reports for 3 days (see #7335 for why it's not running - unrelated).
Even after clicking on "Clear caches", the problem persists, and it has now been several hours since the Directive change.
Files
|
1.png (9.93 KB)
1.png |
|
Jonathan CLARKE, 2015-10-30 15:18
|
|
|
2.png (4.48 KB)
2.png |
|
Jonathan CLARKE, 2015-10-30 15:49
|
|
|
3.png (3.92 KB)
3.png |
|
Jonathan CLARKE, 2015-10-30 15:49
|
|
Update: When I restarted the agent on that node, the compliance came back to something closer to "normal":
Note that some of those reports are "Missing reports".
However, and this may be related, I also have 2 nodes that are receiving reports, and using the latest "config id" (same on disk in /var/rudder/share/<node id> as on the node in /var/rudder/cfengine-*/inputs), but display compliance as 100% "No report":
This server is running 3.1.4-wheezy0 by the way.
- Target version changed from 3.1.5 to 3.0.12
Most of that code didn't change since 3.0, so retargeting to that version.
- Status changed from New to In progress
- Status changed from In progress to New
This is not in progress at all - I'm stuck on that one.
- Target version changed from 3.0.12 to 3.0.13
- Related to Bug #7743: Compliance take into account expired run added
- Target version changed from 3.0.13 to 3.0.14
- Target version changed from 3.0.14 to 3.0.15
- Related to Bug #8051: Compliance is not correctly computed if we receive run agent right after generation added
- Target version changed from 3.0.15 to 3.0.16
It is mostly related to #8051. At least, it's typically the kind of behavior that can be produced by a case where the code that should update the compliance information for a node is stuck in the middle of nowhere forever.
I propose to mark it as a duplicate of #8051, and reopened it in case we find it again in the future.
- Related to deleted (Bug #8051: Compliance is not correctly computed if we receive run agent right after generation)
François ARMAND wrote:
It is mostly related to #8051. At least, it's typically the kind of behavior that can be produced by a case where the code that should update the compliance information for a node is stuck in the middle of nowhere forever.
I propose to mark it as a duplicate of #8051, and reopened it in case we find it again in the future.
Agreed.
- Status changed from New to Rejected
- Related to Question #8176: All nodes compliance report unexpected/missing except root server. added
- Related to Bug #8141: On rules creation, we may get a never stopping spining wheel on rules list added
- Related to Bug #8030: When a node doesn't have expected reports, we have a spinning wheel in place of compliance added
- Related to Bug #8288: Many WARN messages after upgrade about JSON deserialisation error added
- Related to deleted (Bug #8288: Many WARN messages after upgrade about JSON deserialisation error)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by