On Wed, Dec 12, 2012 at 04:19:17AM -0800, digrouz wrote:
> Hello,
>
> Any updates when the fix will be implemented?
>
>
Hi digrouz,
I am currently assigned to the ticket
http://projects.puppetlabs.com/issues/11675 and have done some work
already. The problem is that I first have to improve the
Hello,
Any updates when the fix will be implemented?
On Thursday, October 11, 2012 9:23:42 PM UTC+2, Jeff McCune wrote:
>
> On Oct 11, 2012, at 12:13 PM, Stefan Schulte
> > wrote:
>
> > On Thu, Oct 11, 2012 at 10:47:41AM -0700, Jeff McCune wrote:
> >> Nicholas,
> >>
> >> [...]
> >> We can
On Oct 11, 2012, at 12:13 PM, Stefan Schulte
wrote:
> On Thu, Oct 11, 2012 at 10:47:41AM -0700, Jeff McCune wrote:
>> Nicholas,
>>
>> [...]
>> We can't make this idempotent as a result. This is definitely a bug,
>> would you mind filing it? If so, I'd be happy to do so on your behalf, but
>> bu
On Thu, Oct 11, 2012 at 10:47:41AM -0700, Jeff McCune wrote:
> Nicholas,
>
> [...]
> We can't make this idempotent as a result. This is definitely a bug,
> would you mind filing it? If so, I'd be happy to do so on your behalf, but
> bugs from users are always better than bugs I report.
>
> Ple
Nicholas,
An easy way to reproduce the problem is to run `puppet resource` a number
of consecutive times. We expect subsequent executions of Puppet to be
idempotent, but they're clearly not:
root@puppetmaster:~# puppet resource user jefftest expiry=2012-01-01
/User[jefftest]/expiry: defined 'exp
Hello,
Here is the output. It seems strange as puppet resource user foo does not
return something about expiry. Even if it's set correctly as chage -l is
showing. Does this help?
[root@host ~]# puppet resource user foo
user { 'foo':
ensure => 'present',
comment => 'userfo
I'm experencing this issue on both Red Hat 5 and 6.
I'll post the output of the puppet resource user foo tomorrow when i'll be
at work.
it seems that this is an active bug:
http://projects.puppetlabs.com/issues/11675#change-73099
--
You received this message because you are subscribed to the
On Wed, Oct 10, 2012 at 1:39 AM, digrouz wrote:
> Hello,
>
> I have class users with manage some user accounts. for some of them i have
> set the expiry attribut in the past '2012-01-01' to disable the account.
>
> The problem is that puppet set this expiration date at every run:
> ...
> /Stage[ma
Hello,
I have class users with manage some user accounts. for some of them i have
set the expiry attribut in the past '2012-01-01' to disable the account.
The problem is that puppet set this expiration date at every run:
...
/Stage[main]/Users/User[x]/expiry: defined 'expiry' as '2012-01-01'
