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.
DescriptionJaroslav Krajicek
2020-02-13 15:12:10 UTC
Created attachment 1662979[details]
Full trace of NoMethodError variables_importer.rb
Description of problem:
`Satellite WebUI -> Configure -> Ansible -> Variables -> Import`
fails with below mentioned error
Version-Release number of selected component (if applicable):
satellite-6.6.0-7.el7sat.noarch
How reproducible:
Unable to reproduce in lab on Satellite 6.6
System with issue upgraded from 6.4
Actual results:
(Full trace attached as file)
~~~
NoMethodError
undefined method `map' for nil:NilClass
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_ansible-3.0.7.1/app/services/foreman_ansible/variables_importer.rb:48:in `initialize_variables'
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_ansible-3.0.7.1/app/services/foreman_ansible/variables_importer.rb:34:in `block in import_variables'
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_ansible-3.0.7.1/app/services/foreman_ansible/variables_importer.rb:31:in `each'
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_ansible-3.0.7.1/app/services/foreman_ansible/variables_importer.rb:31:in `map'
...
...
~~~
Expected results:
Successful import of Ansible variables `foreman_scap_client_server, foreman_scap_client_port, foreman_scap_client_policies`
Additional info:
Original issue that the customer seemed to hit:
https://bugzilla.redhat.com/show_bug.cgi?id=1753313
foreman-debug output attached to the case 02581501
VERIFIED.
@Satellite 6.8.0 Snap12
tfm-rubygem-foreman_ansible-5.1.1-1.el7sat.noarch
by the following manual reproducer:
1) Create a bogus role 'foo'
# touch /usr/share/ansible/roles/foo
2) Import the role 'foo'
# hammer ansible roles import --proxy-id 1 --role-names foo
Result:
The following ansible roles were changed
Imported:
1) foo
3) Import ansible variables (for the role 'foo')
REPRO:
# hammer ansible variables import --proxy-id 1
Could not import variables:
Internal Server Error: the server was unable to finish the request. This may be caused by unavailability of some required service, incorrect API call or a server-side bug. There may be more information in the server's logs.
vs.
FIX:
# hammer ansible variables import --proxy-id 1
Result:
No changes in ansible variables detected.
>>> if there is bogus role then ansible variables import is not failing on that
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.8 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-2020:4366