Bug 1994237

Summary: Executing any foreman-rake commands shows 'ErbParser' and 'RubyParser' are ignored.
Product: Red Hat Satellite Reporter: Satyajit Das <sadas>
Component: InfrastructureAssignee: Ewoud Kohl van Wijngaarden <ekohlvan>
Status: CLOSED ERRATA QA Contact: Lukas Pramuk <lpramuk>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.10.0CC: ahumbe, egolov, ehelms, ekohlvan, inecas, wclark
Target Milestone: 6.11.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-05 14:29:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Satyajit Das 2021-08-17 06:00:28 UTC
Description of problem:

Executing any foreman-rake commands shows 'ErbParser' and 'RubyParser' are ignored.

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

satellite-6.10.0-0.6.beta.el7sat.noarch

How reproducible:

100%

Steps to Reproduce:
1. Execute any foreman-rake commands and you will see the warnings.


Actual results:

# foreman-rake katello:reimport
'ErbParser' is ignored.
'RubyParser' is ignored.


Expected results:

If it's ignored, the command should not display the warnings


Additional info:

In satellite 6.9, not able to see the same behavior.

Comment 2 Evgeni Golov 2021-09-16 14:22:48 UTC
This comes from tfm-rubygem-gettext, and is visible e.g. here:

[root@pipe-katello-server-nightly-centos7 ~]# foreman-rake about
'ErbParser' is ignored.
'RubyParser' is ignored.
About your application's environment
…

Comment 3 Ewoud Kohl van Wijngaarden 2021-09-16 14:39:29 UTC
It is installed via rubygem-gettext_i18n_rails_js, rubygem-hammer_cli_foreman_azure_rm, and rubygem-hammer_cli_foreman_kubevirt if I look at the upstream packaging repository.

rubygem-gettext_i18n_rails_js is only a build dependency. I opened https://github.com/theforeman/hammer_cli_foreman_azure_rm/pull/18 as well and kubevirt probably needs a similar patch.

Comment 4 Ewoud Kohl van Wijngaarden 2021-11-03 11:02:49 UTC
Both hammer plugins have been updated and seen a new release. Packaging for Azure has been merged, Kubevirt (https://github.com/theforeman/foreman-packaging/pull/7222) was just opened. Once both are merged it will at least be solved for new installations.

For upgrading users there needs to be something to remove the packages.

Comment 5 Bryan Kearney 2022-04-04 16:04:12 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/33556 has been resolved.

Comment 6 Lukas Pramuk 2022-04-20 11:14:49 UTC
VERIFIED.

@Satellite 6.11.0 Snap16
tfm-rubygem-hammer_cli_foreman_kubevirt-0.1.5-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_azure_rm-0.2.2-1.el7sat.noarch

by the following manual reproducer:

1) Install optional kubevirt rubygem as only azure_rm rubygem is present by default

# yum --disableplugin foreman-protector install tfm-rubygem-hammer_cli_foreman_kubevirt

2) Run foreman-rake

# foreman-rake about
About your application's environment
Rails version             6.0.3.7
Ruby version              ruby 2.7.4p191 (2021-07-07 revision a21a3b7d23) [x86_64-linux]
RubyGems version          3.1.6
Rack version              2.2.3
...

>>> no warnings are displayed

# rpm -qa *rubygem-gettext
<empty>

>>> problematic rubygem is no longer present

However, for upgraded Satellites the warnings are still present - yet we need to obsolete the rubygem rpm => cloned BZ#2076987

Comment 9 errata-xmlrpc 2022-07-05 14:29:34 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 (Moderate: Satellite 6.11 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-2022:5498