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.

Description of problem:"invalid Unicode Property \p: /\b\perform various actions through those proxies\b(?!-)/" warning messages appears in dynflow-sidekiq@worker-hosts-queue 


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

How reproducible:
always

Steps to Reproduce:
1. Install satellite on the IPv6 environment.
2. Configure the proxy on satellite.
3. Restart foreman-maintain services.

Actual results:
"invalid Unicode Property \p: /\b\perform various actions through those proxies\b(?!-)/" warning messages appears in dynflow-sidekiq@worker-hosts-queue 

Expected results:
These warning messages should not come.

Additional info:

When you look at output of journalctl -u foreman, you will see it there too, so this hints away from Dynflow. The message explicitly mentions foreman_theme_satellite. If you look at the given file and line, you will see that there is a \p being used, which as far as I know is invalid. Passing this on to branding

Verified on 6.8 Snap3.
Didn't see an invalid Unicode property warning message in foreman-maintain service status.

# rpm -q tfm-rubygem-foreman_theme_satellite
tfm-rubygem-foreman_theme_satellite-6.0.1.1-1.el7sat.noarch

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