Content origin temp var should be the same for both scenarios #138
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.
SUMMARY
If the
pulp_settings.content_origin
is set by the user, we should set the temp content_orgin var so that it is used in the token_server_dict var, otherwise if the user sets this variable it will fail on the task that sets that dict.Without this, the following error will be seen:
If the user does not set
pulp_settings.content_origin
, content_origin is set in theget_node_ip.yml
task.ADDITIONAL INFORMATION
This is follow-up for https://github.com/ansible/galaxy-operator/pull/137/files, which introduced this regression.