Description of problem: Current v7 won't check the version of /etc/v7.xml, so if upgrade v7 from an old release, e.g. from 1.4 to 1.5, the old v7.xml still there. # rpm -q v7 v7-1.5-21.el6.noarch # yes y | v7 clean all # v7 plan ... # cat /etc/v7.xml <?xml version='1.0' encoding='UTF-8'?> <?xml-stylesheet href="/v7/css/env.css" type="text/css"?> <v7-environment v7-version='1.4' v7-release='38'> ... </v7-environment> Version-Release number of selected component (if applicable): v7-1.5-21 How reproducible: always Expected results: /etc/v7.xml get sync-ed matching the current v7 version
This is intentional, as it preserves configuration settings across upgrades.
For a later release should we consider submitting the results and refreshing, retaining the applicable settings but updating to 1.6? After a 1.4->1.5 upgrade there will be updates to the xml which are unique to 1.5 so it's not 100% accurate to call it 1.4 anymore especially if any tests are run.
For clarification: The version reported by "v7 version" does not come from this file. Also the results will be marked with the installed version, not that shown in /etc/v7.xml. The version that appears in /etc/v7.xml is just the version that created the file.