Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Unable to promote content view due to "NoMethodError: undefined method `get_status' for nil:NilClass" as there is no method for setting the same workaround as the UI.
https://access.redhat.com/solutions/6038731
Version-Release number of selected component (if applicable):
Tested in 6.9
How reproducible:
Only in environments where the nil:NilClass happens.
Steps to Reproduce:
1. Run a playbook using the module `redhat.satellite.content_view_version`
```
- name: Publish new content view version to lib and dev
redhat.satellite.content_view_version:
username: "{{ user }}"
password: "{{ pw }}"
server_url: "{{ url }}"
content_view: "{{ view }}"
organization: "{{ org }}"
validate_certs: no
description: "testing content view"
lifecycle_environments:
- Dev
loop: "{{ views }}"
loop_control:
loop_var: view
```
Actual results:
"msg": "Task Promote content view 'Test'; organization 'Test'(xxxxxx) did not succeed. Task information: [\"undefined method `get_status' for nil:NilClass\"]",
Expected results:
Success
I honestly don't see us adding a workaround for this in the module, but could you try unsetting the "default location" of the user you're running this with?