Description of problem: When cloning errata, clone doesn't contain information about severity. Version-Release number of selected component (if applicable): 5.8 How reproducible: 100% Steps to Reproduce: 1. Sync erratum with severity set 2. Clone erratum 3. Check severity of the clone Actual results: Clone doesn't have severity set Expected results: Same severity as original Additional info:
spacewalk 0eae0307b712bddd8512c2856d58538e2502a1bf
spacewalk e52dbe58c800e9cfa2b931ceb47b03da4bcedb3b
and one more... cff642e085ed083e0277da1226421ca5df088dbc
Tested using the reproducer from the initial report on: spacewalk-java-2.5.14-119.el6sat.noarch spacewalk-schema-2.5.1-59.el6sat.noarch satellite-schema-5.8.0.45-1.el6sat.noarch $ echo "select id,advisory_name,advisory_type,severity_id from rhnerrata where advisory_name like 'CL-SA%';" | spacewalk-sql --select-mode - id | advisory_name | advisory_type | severity_id ------+-----------------+-------------------+------------- 6994 | CL-SA-2017:2907 | Security Advisory | 1 6996 | CL-SA-2017:2836 | Security Advisory | 0 6995 | CL-SA-2017:2882 | Security Advisory | 2 6985 | CL-SA-2018:1099 | Security Advisory | 6986 | CL-SA-2018:1055 | Security Advisory | 6987 | CL-SA-2018:0842 | Security Advisory | 6988 | CL-SA-2018:0805 | Security Advisory | 6989 | CL-SA-2018:0549 | Security Advisory | 6990 | CL-SA-2018:0527 | Security Advisory | (9 rows) First three cloned errata (CL-SA-2017:2907, CL-SA-2017:2836, CL-SA-2017:2882) with the severity set were cloned after applying the fix, so the severity was successfully cloned as well. Remaining errata without the severity set were cloned before applying the fix. Is there a way allowing re-syncing the severity for errata cloned before the fix, or has this ship sailed already, and we have to live with cloned errata without the severity set?
There's no option like that - after cloning, the original erratum and the clone are two unlinked errata.
Ok. VERIFIED
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, 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/RHEA-2018:1565