Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unregistered clients don't get a pool assigned at first run #13

Open
fonk opened this issue Dec 19, 2014 · 4 comments
Open

unregistered clients don't get a pool assigned at first run #13

fonk opened this issue Dec 19, 2014 · 4 comments

Comments

@fonk
Copy link

fonk commented Dec 19, 2014

Hi,

the first run on an unregistered system doesn't assign the pool:

[root@test1e ~]# puppet agent --test --server puppet --environment development
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Info: Caching catalog for test1e.buch.de
Info: Applying configuration version '1418977889'
Notice: /Stage[main]/Role::Default-server/Rhsm_register[subscription.rhn.redhat.com]/ensure: created
Notice: Finished catalog run in 7.26 seconds
[root@test1e ~]# puppet agent --test --server puppet --environment development
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Info: Caching catalog for test1e.buch.de
Info: Applying configuration version '1418977903'
Notice: /Stage[main]/Role::Default-server/Rhsm_register[subscription.rhn.redhat.com]/pool: pool changed '' to 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
Notice: Finished catalog run in 17.79 seconds
[root@test1e ~]# 
@fennm
Copy link

fennm commented Mar 29, 2015

Puppet expects that creating a resource also correctly sets all its properties, so it looks like the rhsm_register provider should also call attach if pool is set. I unfortunately don't have a RHEL license handy to test this right now.

@jlaska
Copy link
Owner

jlaska commented Mar 29, 2015

I no longer have access to RHEL subscriptions to verify the expected behavior. If someone is able to test and submit a PR, that'd be great!

@fonk
Copy link
Author

fonk commented May 28, 2015

Hi!
Is this supposed to be fixed? Then I could (and would :-)) test it... Or are you still waiting for a second confirmation of this issue?
Best regards,
Frank

@jlaska
Copy link
Owner

jlaska commented May 28, 2015

@fonk No fixes have been applied for this issue. If someone with access to RHEL subscriptions can verify the reported issue, we should start there. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants