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 2039059 - Pulp3: Migration fails with error "Katello::Errors::Pulp3Error: Empty variable tag"
Summary: Pulp3: Migration fails with error "Katello::Errors::Pulp3Error: Empty variabl...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.9.7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.9.9
Assignee: satellite6-bugs
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-10 20:22 UTC by wclark
Modified: 2022-04-20 20:35 UTC (History)
5 users (show)

Fixed In Version: pulp-2to3-migration-0.11.9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-20 20:34:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github pulp pulp-2to3-migration issues 496 0 None closed Migration fails with "TemplateSyntaxError: Empty variable tag" when filelists contain '{{' 2022-02-17 13:38:29 UTC
Red Hat Product Errata RHSA-2022:1478 0 None None None 2022-04-20 20:35:01 UTC

Description wclark 2022-01-10 20:22:04 UTC 
The condition to produce the bug is similar to https://bugzilla.redhat.com/show_bug.cgi?id=2020473 but this issue occurs during content migration rather than repository sync

To reproduce: Have some custom repository (ex. Fedora 35 synced from https://dl.fedoraproject.org/pub/fedora/linux/releases/35/Everything/x86_64/os/ ) which contains an RPM that has files with '{{' or similar characters in file names. Then filelists.xml will be like:

In "6dc8dae1be904c2613d5aa3667dacd2554d05077eb1ce4296b6edfa3c4db3a46-filelists.xml.gz"
<package pkgid="f2056c2614a2e47efd63138cf9ad2fac9ea5ea193d736fc35069c1bf6723d549" name="R-rlang" arch="x86_64">
  <version epoch="0" ver="0.4.11" rel="3.fc35"/>
  <file type="dir">/usr/lib/.build-id</file>
  <file type="dir">/usr/lib/.build-id/42</file>
  <file>/usr/lib/.build-id/42/5049f5a9e0d1ac25c21de795f28fe886bfa0ca</file>
  <file type="dir">/usr/lib64/R/library/rlang</file>
  <file>/usr/lib64/R/library/rlang/DESCRIPTION</file>
  <file>/usr/lib64/R/library/rlang/INDEX</file>
  <file>/usr/lib64/R/library/rlang/LICENSE</file>
  <file type="dir">/usr/lib64/R/library/rlang/Meta</file>
  snip...
  <file>/usr/lib64/R/library/rlang/help/wref_key.html</file>
  <file>/usr/lib64/R/library/rlang/help/wref_value.html</file>
  <file>/usr/lib64/R/library/rlang/help/zap.html</file>
  <file>/usr/lib64/R/library/rlang/help/zap_srcref.html</file>
  <file>/usr/lib64/R/library/rlang/help/{{.html</file>   <================= TemplateSyntaxError: Empty variable tag on line 548\n",
  <file>/usr/lib64/R/library/rlang/help/{{}}.html</file> <=================

And cause the TemplateSyntaxError: Empty variable tag when the migration plugin calls `render_filelists`
Comment 2 Grant Gainey 2022-02-17 13:42:07 UTC 
Fix backported to pulp-2to3-migration 0.11.9
Comment 3 Vladimír Sedmík 2022-03-28 15:25:02 UTC 
Verified on 6.9.9 snap 1:

1) Synchronized Fedora 35 repo from https://dl.fedoraproject.org/pub/fedora/linux/releases/35/Everything/x86_64/os/
(here I bumped into BZ#2020473 and had to apply its patch manually for successful sync)

2) Successfully migrated the content, no errors spotted.

[root@sat ~]# satellite-maintain prep-6.10-upgrade
Running Preparations for the Satellite 6.10 upgrade
================================================================================
Preparations for the Satellite 6.10 upgrade: 
prep-6.10-upgrade may take a while depending on the size of /var/lib/pulp/content
| # chgrp -R pulp /var/lib/pulp/content                               [OK]      
--------------------------------------------------------------------------------


[root@sat ~]# satellite-maintain content prepare
Running Prepare content for Pulp 3
================================================================================
...
2022-03-28 04:39:25 -0400: Importing migrated content type rpm: 65275/65732
2022-03-28 04:39:35 -0400: Importing migrated content type rpm: 65732/65732
Content Migration completed successfully
                                                                      [OK]
--------------------------------------------------------------------------------
...

[root@sat ~]# satellite-maintain content migration-stats
Running Retrieve Pulp 2 to Pulp 3 migration statistics
================================================================================
Retrieve Pulp 2 to Pulp 3 migration statistics: 
============Migration Summary================
Migrated/Total RPMs: 65732/65732
Migrated/Total errata: 0/0
Migrated/Total repositories: 1/1
Comment 8 errata-xmlrpc 2022-04-20 20:34:53 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.9.9 Async Bug Fix Update), 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:1478
Note You need to log in before you can comment on or make changes to this bug.