| Summary: | [RFE] Upgrading rhevm versions should show all rhevm-config changed settings | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Anand Nande <anande> |
| Component: | RFEs | Assignee: | Eli Mesika <emesika> |
| Status: | CLOSED WONTFIX | QA Contact: | Pavel Stehlik <pstehlik> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | aberezin, dfediuck, emesika, iheim, lpeer, oschreib, rbalakri, yeylon |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | integration | ||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-09-09 15:43:10 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: | |
|
Comment 1
Itamar Heim
2013-09-06 05:20:39 UTC
as for the general request, we could go with: - print all new keys which are new? - print all keys which their 3.4 (latest) is different than 3.3 (last) - not sure if we know to print all keys which value is different for 'general' items. Why can't we add those entries in the release notes per minor version? (In reply to Itamar Heim from comment #1) > i find this strange. usually this would appear in a new version when we are > adding the new config. livnat? you are right, it should not have been the case. When adding the anti-spoofing feature we should have added a single config value to enable or disable this for the setup, by mistake it was added per cluster version. We have a bug with release notes where we fixed that specific config value - bug 1063711 All new features and behavior changes are supposed to be covered by RFE Bugs covered in the Errata/release notes/what's new in the admin guide. a config key is not the only way this could come about. (see bug 1063711 which changed this to be a 'general' level config later on in 3.4) |