Modify

Ticket #392 (closed defect: fixed)

Opened 15 years ago

Last modified 15 years ago

New entries in client.xml fail until server restarted

Reported by: [email protected] Owned by: desai
Priority: major Milestone: Bcfg2 0.9.3 Release
Component: bcfg2-server Version: 0.9.x
Keywords: Cc:

Description

Adding a new entry in clients.xml (with corresponding entries in groups.xml) fails with:

bcfg2-server[3d29375196c124405db4d256dc8368f39e9160d1] (SVN r4833): Processed 2 gamin events in 0.123 seconds. 0 collapsed
bcfg2-server[3d29375196c124405db4d256dc8368f39e9160d1] (SVN r4833): Cannot set group for client conway.wsg.mcgill.ca; no default group set
bcfg2-server[3d29375196c124405db4d256dc8368f39e9160d1] (SVN r4833): Client metadata resolution error for 132.216.177.33

Here are the corresponding entries in clients.xml and groups.xml:

clients.xml

<Client profile="ras-server" name="conway.wsg.mcgill.ca" pingable="Y"/>

groups.xml

<Group profile="true" public="false" name="ras-server">
    <Group name="el4-i386"/>
    <Group name="syslog-client"/>
    <Group name="mail-client"/>
    <Group name="postgresql-server"/>
    <Group name="httpd-server"/>
</Group>

Restarting bcfg2-server fixes the problem.

Attachments

metadata.diff (1.8 KB) - added by desai 15 years ago.

Change History

comment:1 follow-up: ↓ 2 Changed 15 years ago by desai

I can't replicate this problem here. To narrow things down, can you:

  • run bcfg2-info
  • wait until it has processed all events
  • add a new client to <repo>/Metadata/clients.xml
  • run the "update" command at the bcfg2-info prompt
  • run the "clients" command at the bcfg2-info prompt

What I need to know is:

  • what is displayed in response to the "update" command
  • is the client displayed in the output of "clients" after the update command?g

comment:2 in reply to: ↑ 1 Changed 15 years ago by [email protected]

Replying to desai:

I can't replicate this problem here. To narrow things down, can you:

  • run bcfg2-info
  • wait until it has processed all events
  • add a new client to <repo>/Metadata/clients.xml
  • run the "update" command at the bcfg2-info prompt
  • run the "clients" command at the bcfg2-info prompt

What I need to know is:

  • what is displayed in response to the "update" command
  • is the client displayed in the output of "clients" after the update command?g

I had the same error and after doing the steps you suggested it worked.

comment:3 Changed 15 years ago by desai

  • Status changed from new to assigned

I suspect that the attached patch will fix the problem. Can either of you verify this? The problematic sequence of events was:

  • Add a new client entry, with profile set to a non-existent profile
  • the server processes this change, and drops the client's setting
  • Add the new profile group (or even just the profile attribute)
  • The server doesn't re-add the client mapping

The new patch tracks when clients map to non-existent profiles (or non profile groups) and will map them if the profile group is subsequently created (or an existing group is set to be a profile group)

Changed 15 years ago by desai

comment:4 Changed 15 years ago by desai

  • Status changed from assigned to closed
  • Resolution set to fixed
  • Milestone set to Bcfg2 0.9.3 Release

This seems to have been resolved with the metadata patch included.

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.