Bug #2808
puppetqd doesn't give an error when no config is given
| Status: | Closed | Start: | 11/12/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Jesse Wolfe |
% Done: | 0% |
|
| Category: | error reporting | |||
| Target version: | 0.25.2 | |||
| Affected version: | 0.25.1 | Branch: | http://github.com/jes5199/puppet/tree/ticket/0.25.x/2808 | |
| Keywords: | ||||
| Votes: | 0 |
Description
I was trying out puppetqd from 0.25.1 and I noticed that nothing from the queue was written into the database. After some searching, I found this to be because I had my database config in [puppetmaster] and not in [main]. It would be helpful if puppetqd could output something like “No database config found.” I spent my time now mostly trying different queuing software and the like.
Related issues
| related to Puppet - Feature #2935: Settings should use 'agent' and 'server' in addition to e... | Closed | 12/15/2009 |
History
Updated by James Turnbull 10 months ago
- Category set to queuing
- Status changed from Unreviewed to Accepted
- Assignee set to Markus Roberts
Updated by Markus Roberts 9 months ago
- Assignee changed from Markus Roberts to Jesse Wolfe
- Target version set to 0.25.2
Updated by Markus Roberts 9 months ago
- Category changed from queuing to error reporting
Updated by Luke Kanies 9 months ago
This is correct behaviour — it’s using the default because it didn’t find any configuration – but we can add some logging to make its choice more clear.
Updated by Jesse Wolfe 9 months ago
- Status changed from Accepted to Ready for Testing
- Branch set to http://github.com/jes5199/puppet/tree/ticket/0.25.x/2808
Added an info message about what database we're connecting to.
In the case of the default database, it looks like:
info: Connecting to sqlite3 database: /var/lib/puppet/state/clientconfigs.sqlite3
Updated by James Turnbull 9 months ago
- Status changed from Ready for Testing to Closed
Pushed in commit:“e0488b26f04e931b17b104fd7f69f6527436e81d” in branch 0.25.x