Project

General

Profile

Actions

Bug #7689

closed

Error on promise generation after accepting a node

Added by Nicolas CHARLES over 5 years ago. Updated about 5 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

On Rudder 3.2~rc1-3, I accept a node, and no promise generation happen
So I click on update, and I have a failure:
⇨ cf-promise check fails for promises generated at '/var/rudder/share/479d8ed6-38a7-4562-aee2-c7570f0e68f5/rules.new/cfengine-community'
⇨ Command to check generated promises is: '/var/rudder/cfengine-community/bin/cf-promises -f /var/rudder/share/479d8ed6-38a7-4562-aee2-c7570f0e68f5/rules.new/cfengine-community/promises.cf'
⇨ error: Can't stat file '/var/rudder/share/479d8ed6-38a7-4562-aee2-c7570f0e68f5/rules.new/cfengine-community/promises.cf' for parsing. (stat: No such file or directory)

Indeed, the generated policies don't contain the "common" system technique (but inventory is there)
Clearing the cache don't solve the issue, but reloading the dynamic group does correct the policy generation


Related issues

Related to Rudder - Bug #7544: Accpeting several nodes *still* not accept them allReleasedVincent MEMBRÉ2015-12-04Actions
Related to Rudder - Bug #10446: Policy validation failsReleasedFrançois ARMANDActions
Actions #1

Updated by Nicolas CHARLES over 5 years ago

  • Target version changed from 3.2.0~rc2 to 3.0.13

Ha, benoit told me he saw this in 3.1 as well

Actions #2

Updated by Nicolas CHARLES over 5 years ago

When accepting a node, the logs say

[2015-12-24 09:55:48] DEBUG com.normation.rudder.services.servers.NewNodeManagerImpl - Pre accepted phase: accept_or_refuse_new_node:historize_inventory
[2015-12-24 09:55:48] DEBUG com.normation.rudder.services.servers.NewNodeManagerImpl - Pre accepted phase: accept_new_server:ou=node
[2015-12-24 09:55:48] DEBUG com.normation.rudder.services.servers.NewNodeManagerImpl - Pre accepted phase: accept_new_server:inventory
[2015-12-24 09:55:48] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [1120975579168] Start search for { returnType:'NodeReturnType' with 'Or' criteria [node.nodeHostname eq agent2.rudder.local] }
[2015-12-24 09:55:48] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [1120975579168] |- (final query) LDAPObjectType(ou=Nodes,ou=Accepted Inventories,ou=Inventories,cn=rudder-configuration,One,LDAPObjectTypeFilter((objectClass=*)),Some((|(nodeHostname=agent2.rudder.local))),DNJoin,Set())
[2015-12-24 09:55:48] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [1120975579168] |--- SearchRequest(baseDN='ou=Nodes,ou=Accepted Inventories,ou=Inventories,cn=rudder-configuration', scope=ONE, deref=NEVER, sizeLimit=0, timeLimit=0, filter='(&(objectClass=*)(|(nodeHostname=agent2.rudder.local)))', attrs={policyServerId, osFullName, localAdministratorAccountName, container, cn, osServicePack, createTimestamp, agentName, osName, ipHostNumber, publicKey, osVersion, nodeId, nodeHostname, objectClass})
[2015-12-24 09:55:48] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [1120975579168] |---- 0 result(s)
[2015-12-24 09:55:48] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [1120975579168] |--- or (base filter): 0
[2015-12-24 09:55:48] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [1120975579168] |--- or (special filter): 0
[2015-12-24 09:55:48] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [1120975579168] |--- or (total): 0
[2015-12-24 09:55:48] DEBUG com.normation.rudder.services.queries.InternalLDAPQueryProcessor - [1120975579168] `-> 0 results
[2015-12-24 09:55:48] DEBUG com.normation.rudder.services.servers.NewNodeManagerImpl - Pre accepted phase: accept_new_server:check_hostname_unicity
[2015-12-24 09:55:48] DEBUG com.normation.rudder.services.servers.NewNodeManagerImpl - Unit acceptors ok for NodeId(479d8ed6-38a7-4562-aee2-c7570f0e68f5)
[2015-12-24 09:55:48] INFO  com.normation.rudder.services.servers.NewNodeManagerImpl - New node accepted and managed by Rudder: 479d8ed6-38a7-4562-aee2-c7570f0e68f5
[2015-12-24 09:55:48] DEBUG com.normation.rudder.web.snippet.node.AcceptNode - Successfully added node '479d8ed6-38a7-4562-aee2-c7570f0e68f5'

It is completly missing the reload groups :/

Actions #3

Updated by Nicolas CHARLES over 5 years ago

  • Related to Bug #7024: Accepting two nodes seems to only accept one added
Actions #4

Updated by Nicolas CHARLES over 5 years ago

  • Related to Bug #7544: Accpeting several nodes *still* not accept them all added
Actions #5

Updated by Nicolas CHARLES over 5 years ago

  • Related to deleted (Bug #7024: Accepting two nodes seems to only accept one)
Actions #6

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
Actions #7

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/rudder/pull/1016
Actions #8

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #9

Updated by Anonymous over 5 years ago

Actions #10

Updated by Vincent MEMBRÉ about 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.13, 3.1.6 and 3.2.0 which were released today.

Actions #11

Updated by Nicolas CHARLES about 4 years ago

  • Related to Bug #10446: Policy validation fails added
Actions

Also available in: Atom PDF