Bug 1914751
Summary: | After upgrade default_download_policy changed from "on_demand" to "immediate" | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Devendra Singh <desingh> |
Component: | Repositories | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED NOTABUG | QA Contact: | Tasos Papaioannou <tpapaioa> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.9.0 | CC: | ahumbe, apatel, jsherril, mhulan, ssainkar |
Target Milestone: | 6.9.0 | Keywords: | PrioBumpGSS, Regression, Triaged |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
After upgrading Satellite from version 6.8 to 6.9, the default_download_policy changed from *on_demand* to *immediate*.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2021-02-16 17:33:48 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: |
Description
Devendra Singh
2021-01-11 06:34:36 UTC
the default on new installs changed as part of https://bugzilla.redhat.com/show_bug.cgi?id=1732056 in 6.7, its strange that its being reset upon upgrade to 6.9. we will investigate I'm not able to reproduce this. I installed Satellite 6.8, changed default_download_policy to 'on_demand' (from immediate). Then upgraded to 6.9 and examined the administer > settings > content page. Are you able to reproduce on the latest snap? If you can reproduce, being pointed to a reproducer server might be helpful After talking with Devendra, we discovered that the satellite in question had been upgraded from 6.6. The default download policy was updated from 'on_demand' to 'immediate' as part of 6.7, but it appears that the default value wasn't actually updated in the db at that time. This is likely due to a bug in the settings related code. It seems that this bug was fixed as part of 6.9 though, and thus the default value was updated resulting in a change in behavior. Here's the 6.7 bz that changed it: https://bugzilla.redhat.com/show_bug.cgi?id=1732056 and it includes appropriate docs text. So in reality this was a 6.7/6.8 bug in settings as the change was expected at that time. As a result we're going to close this bz |