Handle the case when the oinstall group already exist on the network #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Ari,
I ran into this problem while installing the oracle client on our machine as the group
oinstall
is already created on the network. With this change, we can avoid the error that chef will throw when trying to create an existing group.The
oracli_user_config.rb
will also try to create as it is a default group innode[:oracle][:cliuser][:sup_grps]
but this can be disabled by removing it from the default attributes or overriding it at the node/role level.Let me know if you have any comments or questions