Custom Query (894 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (115 - 117 of 894)

Ticket Owner Reporter Resolution Summary
#282 desai naapuri fixed bcfg2-server starts serving before it is ready
Description

When testing bcfg2, I occasionally get errors such as

Incomplete information for entry ConfigFile:/etc/motd; cannot install

and on respectively on the server:

Failed to bind entry: ConfigFile /etc/motd

It took me a while to realize that this occurs when I've just restarted the bcfg2-server and then run the client too quickly.

How to reproduce:

  1. Start the server: # bcfg2-server
  1. The server says: "Bound to port 6789" but no lines telling "Processed 3 gamin events..." yet.
  1. Run the client.
  1. See the server output

A correct run:

# bcfg2-server
/etc/bcfg2.pem
Bound to port 6789
Processed 23 gamin events in 6.161 seconds. 0 collapsed
Processed 3 gamin events in 0.100 seconds. 0 collapsed
Processed 3 gamin events in 0.100 seconds. 0 collapsed
Generated config for etchbase in 0.0238389968872 seconds
Client etchbase reported state clean

An incorrect run:

# bcfg2-server
/etc/bcfg2.pem
Bound to port 6789
Processed 23 gamin events in 6.081 seconds. 0 collapsed
Processed 3 gamin events in 0.101 seconds. 0 collapsed
Failed to bind entry: ConfigFile /etc/motd
Generated config for etchbase in 0.024423122406 seconds
Processed 3 gamin events in 0.101 seconds. 0 collapsed
Client etchbase reported state dirty

How to fix: the server should first read the config and only then start listening on the port.

#283 desai naapuri fixed bcfg2's -I option seems to imply "-r all"
Description

When running bcfg2 -I, the "-r all" seems to be implied. IMO, running without -I should result in the same condition as running with -I and answering "y" to every question.

How to fix: -I should not imply "-r all".

#284 desai naapuri fixed Should be able to use -n and -r together
Description

"bcfg2 -n -r all" exits telling "cannot use -n and -r together".

I find it very important to be able to dry-run configurations, especially those that will remove something.

See also #283.

Note: See TracQuery for help on using queries.