Bug 1971076
| Summary: | Changing "Sync Connection Timeout" in settings does not immediate take effect | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Lai <ltran> |
| Component: | Repositories | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED ERRATA | QA Contact: | Vladimír Sedmík <vsedmik> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.10.0 | CC: | apatel, jlenz, mhulan, pcreech, vsedmik |
| Target Milestone: | 6.10.0 | Keywords: | 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: | 2021-11-16 14:11:39 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1334989 | ||
@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?
Justin says this may have been fixed by https://github.com/theforeman/foreman-tasks/commit/1b174f10e64265ad93b6c29f96c4aa24ca161b88 Fixed in foreman-tasks and needs QE verification. Verified on 6.10.0 snap 12, the timeout is changed on the repo sync. 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 |
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.