-
Notifications
You must be signed in to change notification settings - Fork 104
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
orawls printing notice messages even when there is no change in properties #546
Comments
it can be it could read the xaproperties and uses [] , in that case it wants it to change it to the requested. So we need to find out why this happening. can you do puppet resource wls_datasource --debug --trace. and see if it shows the xaproperties. |
below is output or the command you said - puppet resource wls_datasource --debug --trace I dont see xaproperties in this. but if I run puppet apply with --debug, its hows xaproperties its taking form yaml.
|
I would expect to see the wlst output on this �[0;36mDebug: index wls_datasource�[0m can you paste your datasource entry so I can re-produce it. |
you mean this? =========================== |
and jms queue entry where other message is as below:wls_jms_queues: |
any suggestion? |
@biemond - any suggestions to overcome this? |
I have provided same hiera files and running puppet apply again and again without any changes in yaml files.
puppet is printing some messages which says properties changed from [] to some other value, can someone help to understand why its printing messages even when there are no change at all?
I get this in puppet logs:
The text was updated successfully, but these errors were encountered: