Project

General

Profile

Actions
Copy link

Bug #7689

closed

Error on promise generation after accepting a node

Bug #7689: Error on promise generation after accepting a node

Added by Nicolas CHARLES over 10 years ago. Updated over 10 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
Web - Config management
Target version:
3.0.13
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

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 2 (0 open — 2 closed)

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

Updated by Nicolas CHARLES over 10 years ago Actions
Copy link
 #1

  • Target version changed from 3.2.0~rc2 to 3.0.13

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

Updated by Nicolas CHARLES over 10 years ago Actions
Copy link
 #2

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 :/

Updated by Nicolas CHARLES over 10 years ago Actions
Copy link
 #3

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

Updated by Nicolas CHARLES over 10 years ago Actions
Copy link
 #4

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

Updated by Nicolas CHARLES over 10 years ago Actions
Copy link
 #5

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

Updated by Nicolas CHARLES over 10 years ago Actions
Copy link
 #6

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

Updated by Nicolas CHARLES over 10 years ago Actions
Copy link
 #7

  • 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

Updated by Nicolas CHARLES over 10 years ago Actions
Copy link
 #8

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

Updated by Anonymous over 10 years ago Actions
Copy link
 #9

Updated by Vincent MEMBRÉ over 10 years ago Actions
Copy link
 #10

  • 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.

Updated by Nicolas CHARLES over 9 years ago Actions
Copy link
 #11

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

Also available in: PDF Atom