Bug #9204
inventory.txt massively large
| Status: | Closed | Start date: | 08/25/2011 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | SSL | |||
| Target version: | - | |||
| Affected Puppet version: | 2.6.2 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
I’m not sure what the intended behavior of the inventory file is (maybe it is appending instead of rewriting?) but our inventory.txt file is 569217 lines long with many servers listed multiple times.
History
Updated by James Turnbull 9 months ago
- Category set to SSL
- Status changed from Unreviewed to Needs More Information
- Assignee set to Digant Kasundra
Digant – Have you recently made a major change or added a number of certs? If so how did you remove the old certs?
Updated by Digant Kasundra 9 months ago
We have not. When removing old certs, we always used the —clean option to puppetca.
Updated by Digant Kasundra 9 months ago
- Assignee changed from Digant Kasundra to James Turnbull
Updated by James Turnbull 9 months ago
- Status changed from Needs More Information to Investigating
- Assignee deleted (
James Turnbull)
Updated by Daniel Pittman 9 months ago
- Status changed from Investigating to Accepted
- Assignee set to Nigel Kersten
Nigel, we discussed this; can you add the details of what the problem was, so we can get this sorted out?
Updated by Nigel Kersten 9 months ago
Digant, are you sure you’re seeing this on 2.6.2 ?
We fixed this problem a long time ago in 0.24 or 0.25 I believe.
If you move inventory.txt out of the way, when you next sign a certificate it will include all the existing signed certs in a new file.
The previous bug was that it would append all certs to this file every time it signed a new cert.
Updated by Digant Kasundra 9 months ago
I’ll move the file and see what happens the next time.
Updated by Digant Kasundra 9 months ago
So, after blowing it away, it created an inventory of all the certs and now it seems to add just each new cert one at a time, so I’m guessing this is the fixed behavior. The inventory file was probably never cleared after having grown out of control during the buggy phase. This bug can be closed or rejected (I don’t want to do it in case there is something special you guys prefer for your file keeping).
Updated by Nigel Kersten 9 months ago
- Status changed from Accepted to Closed
Awesome. Thanks Digant.