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.
Bug 1881066 - Safemode doesn't allow to access 'host_cores' on #<Safemode::ScopeObject>
Summary: Safemode doesn't allow to access 'host_cores' on #<Safemode::ScopeObject>
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Reporting
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.8.0
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks: 1875660
TreeView+ depends on / blocked
 
Reported: 2020-09-21 13:39 UTC by Lukáš Hellebrandt
Modified: 2020-10-27 13:09 UTC (History)
5 users (show)

Fixed In Version: foreman-2.1.2.16-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 13:09:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 13:09:24 UTC

Description Lukáš Hellebrandt 2020-09-21 13:39:51 UTC
Description of problem:
Host core count can be accessed by `host.cores` and returns correct value. However, there is no macro host_cores in the Help tab and when I attempt to use it anyway by "host_cores(host)", it fails and I get "Safemode doesn't allow to access 'host_cores' on #<Safemode::ScopeObject>".

Version-Release number of selected component (if applicable):
Sat 6.8 snap 15

How reproducible:
Deterministic

Steps to Reproduce:
1. Use host_cores macro in some report
2. Generate that report

Actual results:
"Safemode doesn't allow to access 'host_cores' on #<Safemode::ScopeObject>"

Expected results:
Successfully generated result, the report with a correct number of cores

Additional info:
Discovered during verification of bug 1875660

Comment 1 Brad Buckingham 2020-09-21 14:05:48 UTC
Can you provide which report is impacted by this bugzilla?  Is it a new report introduced in 6.8?

Comment 2 Marek Hulan 2020-09-21 14:20:21 UTC
I didn't find the report that uses that (sorry, I was under the impression some default report added in 6.8 uses it). However I sent a fix which is trivial.

Comment 3 Brad Buckingham 2020-09-21 14:27:41 UTC
Moving to MODIFIED based upon a referenced MR.

Comment 5 Lukáš Hellebrandt 2020-09-30 09:42:16 UTC
Verified with Sat 6.8 snap 17. Used reproducer from OP. Host_cores macro is now present in Help and can be used in the report.

Comment 8 errata-xmlrpc 2020-10-27 13:09:06 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.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


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