Bug #4284
some specs still require group "puppet"
| Status: | Closed | Start date: | 07/19/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Nick Lewis |
% Done: | 0% |
|
| Category: | testing | |||
| Target version: | - | |||
| Affected Puppet version: | 2.6.0rc4 | Branch: | http://github.com/nicklewis/puppet/tree/ticket/2.6.x/4284 | |
| Keywords: | ||||
| Votes: | 0 |
Description
Please review the attached log from a rake specs run. All failures vanished once a group “puppet” was created on the system.
Related issues
History
Updated by David Schmitt almost 2 years ago
Forgot to say: This was on a current Debian testing machine.
Updated by James Turnbull almost 2 years ago
- Status changed from Unreviewed to Accepted
- Assignee set to Nick Lewis
Updated by Nick Lewis almost 2 years ago
- Status changed from Accepted to In Topic Branch Pending Review
- Branch set to http://github.com/nicklewis/puppet/tree/ticket/2.6.x/4284
The failing specs were integration specs which were using quite a few settings, some of which were creating directories as the service user/group. When running the specs as root, it tries to manage the group on the directories, but since the default service user ‘puppet’ isn’t available, it fails. This patch adds an explicit setting for group using the gid of the process. User isn’t an issue because files are owned by root if running as root.
Updated by Markus Roberts almost 2 years ago
- Status changed from In Topic Branch Pending Review to Closed
commit:83c2419771de45317e4bf79e7f71469d9a19a09a [#4284] Fix failing specs run as root due to missing puppet group