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 1803988 - Changing on-demand to immediate not working with broken symlinks
Summary: Changing on-demand to immediate not working with broken symlinks
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-17 22:55 UTC by Partha Aji
Modified: 2024-12-20 19:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-18 19:44:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Partha Aji 2020-02-17 22:55:31 UTC
I created a bad repo the following way
"""
$ wget https://repos.fedorapeople.org/repos/pulp/pulp/stable/latest/7Server/x86_64/pulp-python-admin-extensions-2.0.3-1.el7.noarch.rpm
$ wget https://repos.fedorapeople.org/repos/pulp/pulp/stable/latest/7Server/x86_64/pulp-puppet-consumer-extensions-2.21.0-1.el7.noarch.rpm
$ wget https://repos.fedorapeople.org/repos/pulp/pulp/stable/latest/7Server/x86_64/python-pulp-ostree-common-1.4.0-1.el7.noarch.rpm

$ createrepo .
$ rm python-pulp-ostree-common-1.4.0-1.el7.noarch.rpm
"""
I also did 'python -m http.server 2020' so that the contents are available via http


On Satellite:
1) Create Repo pointing to http://<fqdn>:2020
2) Mark it as On Demand
3) Sync 
4) Get the backend identifier of the repo from repo details and look at 'ls -l /var/lib/pulp/published/yum/master/yum_distributor/<backend_identifier>/<...>/Packages/p'
you should see 3 broken symlinks
5) Now change the Repo to immediate and resync which should fail with a warning. Feel free to try complete sync also.

6) 'ls -l /var/lib/pulp/published/yum/master/yum_distributor/<backend_identifier>/<...>/Packages/p' 

Expected:
2 files in that directory and no python-pulp-ostree-common-1.4.0-1.el7.noarch.rpm

Actual:
There is still a bad symlink for python-pulp-ostree-common-1.4.0-1.el7.noarch.rpm

The larger issue here is the effect on capsule syncing if syncing was changed from On Demand to Immediate

Comment 4 Partha Aji 2020-02-18 22:58:09 UTC
1) If I synced a repo with "immediate" download policy AND  if the upstream repo had a broken/invalid symlink, pulp correctly does not try to pull that file to the disk. 

2) On the other hand on-demand sync does not really know that the upstream link is broken. It just notices that there is a file that is supposed to exist according to the repodata primary xml and put a "placeholder" symlink for that link.

3) In the above case in comment 1 the User set it to On-Demand, synced (creating placeholder links) and then switched it to Immediate and resynced.  In this case I would expect the behaviour to be similar to case 1. Remove the bad symlink and treat it as you would for straight up immediate.

Comment 5 Tanya Tereshchenko 2020-02-24 12:33:35 UTC
Partha, after switching to Immediate, in which mode do you sync, mirror or not?

Comment 6 Mike McCune 2022-01-28 22:30:40 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.

Comment 7 Mike McCune 2022-03-18 19:44:22 UTC
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.

Comment 8 Red Hat Bugzilla 2023-09-15 00:29:39 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


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