Bug 2147579 - 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 ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.10.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.13.0
Assignee: Samir Jha
QA Contact: Sam Bible
URL:
Whiteboard:
: 2107136 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-24 10:47 UTC by Satyajit Das
Modified: 2024-02-08 19:36 UTC (History)
9 users (show)

Fixed In Version: tfm-rubygem-katello-4.7.0.7-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2184127 (view as bug list)
Environment:
Last Closed: 2023-05-03 13:23:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35861 0 Normal Closed Unable to promote content view due to "NoMethodError: undefined method `get_status' for nil:NilClass" 2023-04-03 13:55:11 UTC
Red Hat Issue Tracker SAT-14152 0 None None None 2022-12-01 15:48:01 UTC
Red Hat Knowledge Base (Solution) 6994614 0 None None None 2023-01-18 16:02:48 UTC
Red Hat Product Errata RHSA-2023:2097 0 None None None 2023-05-03 13:23:18 UTC

Description Satyajit Das 2022-11-24 10:47:47 UTC
Description of problem:

Unable to promote content view due to "NoMethodError: undefined method `get_status' for nil:NilClass" 

Version-Release number of selected component (if applicable):

Satellite version 6.10

How reproducible:
100%

Steps to Reproduce:

1. Publish job is working as expected using the Ansible playbook.
2. Promoting with the below playbook fails with error:-
3. 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 8 Samir Jha 2022-12-13 15:12:52 UTC
Created redmine issue https://projects.theforeman.org/issues/35861 from this bug

Comment 9 Bryan Kearney 2023-01-16 16:03:14 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35861 has been resolved.

Comment 12 Sam Bible 2023-02-21 18:49:19 UTC
Verified on 6.13 - Snap 11

Steps to Verify:
Followed steps from the PR here:https://github.com/Katello/katello/pull/10391
These reproduced the orphaned content facet issue, and I was able to use the rake task
foreman-rake katello:clean_orphaned_facets 
to clean them up.

Expected Results:
Using the foreman-rake katello:clean_orphaned_facets command allows publishing without the "NoMethodError: undefined method `get_status' for nil:NilClass" issue

Actual Results:
Using the foreman-rake katello:clean_orphaned_facets command allows publishing without the "NoMethodError: undefined method `get_status' for nil:NilClass" issue

Comment 13 Jeremy Lenz 2023-03-17 20:27:16 UTC
*** Bug 2107136 has been marked as a duplicate of this bug. ***

Comment 18 errata-xmlrpc 2023-05-03 13:23:05 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.13 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:2097


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