Project

General

Profile

Bug #12474

Updated by Fran├žois ARMAND almost 2 years ago

 
 *WORAROUND*: we are not sure of the cause of that ticket (hard to reproduce, but it DID happen two times at least). In all cases, you can correct the problem by executing the following command in the root server: 
 <pre> 
 rudder agent inventory 
 </pre> 

 Description: 

 After upgrading, root server disapeared from the node list 
 However, it looks like it is there in ldap: 
 <pre> 
 dn: nodeId=root,ou=Nodes,cn=rudder-configuration 
 objectClass: rudderPolicyServer 
 objectClass: rudderNode 
 objectClass: top 
 cn: root 
 nodeId: root 
 description: the policy server 
 isSystem: TRUE 
 isBroken: FALSE 
 structuralObjectClass: rudderPolicyServer 
 entryUUID: 33359356-d6a4-1037-9ee3-1d253a7788ee 
 creatorsName: cn=manager,cn=rudder-configuration 
 createTimestamp: 20180417160031Z 
 entryCSN: 20180417160031.621579Z#000000#000#000000 
 modifiersName: cn=manager,cn=rudder-configuration 
 modifyTimestamp: 20180417160031Z 

 </pre> 

 <pre> 
 dn: nodeId=root,ou=Nodes,ou=Accepted Inventories,ou=Inventories,cn=rudder-co 
  nfiguration 
 objectClass: top 
 objectClass: node 
 objectClass: unixNode 
 objectClass: linuxNode 
 nodeId: root 
 osKernelVersion: 1.0-dummy-version 
 osName: Linux 
 osVersion: Linux 
 localAccountName: root 
 cn: root 
 localAdministratorAccountName: root 
 nodeHostname: server.rudder.local 
 policyServerId: root 
 inventoryDate: 19700101000000+0200 
 receiveDate: 19700101000000+0200 
 ipHostNumber: 127.0.0.1 
 agentName: Community 
 rudderServerRole: rudder-web 
 structuralObjectClass: linuxNode 
 entryUUID: 3335b732-d6a4-1037-9ee4-1d253a7788ee 
 creatorsName: cn=manager,cn=rudder-configuration 
 createTimestamp: 20180417160031Z 
 entryCSN: 20180417160031.622498Z#000000#000#000000 
 modifiersName: cn=manager,cn=rudder-configuration 
 modifyTimestamp: 20180417160031Z 
 </pre> 

 Chaos follow :/

Back