Bug 1996649 - Unable to promote content view due to "NoMethodError: undefined method `get_status' for nil:NilClass"
Summary: Unable to promote content view due to "NoMethodError: undefined method `get_s...
Keywords:
Status: CLOSED DUPLICATE of bug 1957035
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible Collection
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-23 11:36 UTC by lbenedit
Modified: 2021-08-23 14:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-23 14:43:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description lbenedit 2021-08-23 11:36:52 UTC
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

Comment 1 Evgeni Golov 2021-08-23 11:49:02 UTC
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?

Comment 2 Brad Buckingham 2021-08-23 14:43:36 UTC
Closing as a duplicate of bug 1957035, as the root cause appears to be the same.

*** This bug has been marked as a duplicate of bug 1957035 ***


Note You need to log in before you can comment on or make changes to this bug.