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 1971076 - Changing "Sync Connection Timeout" in settings does not immediate take effect
Summary: Changing "Sync Connection Timeout" in settings does not immediate take effect
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.10.0
Assignee: satellite6-bugs
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks: 1334989
TreeView+ depends on / blocked
 
Reported: 2021-06-11 21:13 UTC by Lai
Modified: 2021-11-16 14:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-16 14:11:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:11:49 UTC

Description Lai 2021-06-11 21:13:14 UTC 
Description of problem:
Changing "Sync Connection Timeout" in settings does not immediate take effect when you change the number.

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

How reproducible:
100%

Steps to Reproduce:
1. Administer -> Settings -> Content -> Sync Connection Timeout
2. Change number to 5
3. Create a custom repo and sync it
4. Run sudo -u postgres psql pulpcore -c 'select url, total_timeout from core_remote;' to check the db

Actual results:
total_timeout column does not have 5:

                                    url                                     | total_timeout 
----------------------------------------------------------------------------+---------------
 http://infra-robottelo-fixtures.infra.sat.rdu2.redhat.com:50123/fake_yum0/ |           300

Expected results:
total_timeout column should have 5

Additional info:
Workaround is to restart dynflow.
Comment 1 Jeremy Lenz 2021-07-28 14:21:32 UTC 
@ltran I've been unable to reproduce this both on dev and on sat-deploy (which should be the latest snap.)


Immediately after syncing the repo, the total_timeout column is always updated as expected:


[vagrant@sat-6-10-qa-rhel7 ~]$ sudo -u postgres psql pulpcore -c 'select url, total_timeout from core_remote;'
could not change directory to "/home/vagrant": Permission denied
                              url                              | total_timeout 
---------------------------------------------------------------+---------------
 https://jlsherrill.fedorapeople.org/fake-repos/needed-errata/ |             5
(1 row)


Could you test again with the latest snap and verify if this is still an issue?
Comment 2 Jeremy Lenz 2021-07-28 15:22:15 UTC 
Justin says this may have been fixed by https://github.com/theforeman/foreman-tasks/commit/1b174f10e64265ad93b6c29f96c4aa24ca161b88
Comment 3 Jeremy Lenz 2021-07-28 15:34:47 UTC 
Fixed in foreman-tasks and needs QE verification.
Comment 4 Vladimír Sedmík 2021-08-09 18:29:51 UTC 
Verified on 6.10.0 snap 12, the timeout is changed on the repo sync.
Comment 7 errata-xmlrpc 2021-11-16 14:11:39 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.10 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-2021:4702
Note You need to log in before you can comment on or make changes to this bug.