Red Hat Bugzilla – Bug 1429809
[Docs][Admin][Tech] Deprecation notice of net_persistence=ifcfg
Last modified: 2017-04-13 06:51:30 EDT
IFCFG persistence mode is declared deprecated starting from version 4.2. Unified persistence mode has been the default from 3.5, new features and fixes since then have been focused on it. Al suggested usages of net_persistence=ifcfg should be removed and upgrade to unified persistence should to be encouraged. Some customers may have been using ifcfg persistence and patch them with custom settings which RHV may or may not support. For these users, help with the upgrade may be required, including support for introducing features/abilities we do not have in the core product.
We need to make sure this is clearly mentioned.
Hi Edward, Is there a different requirement for this bug and bug 1422957, or can I close one as a duplicate of the other and track all changes in one bug?
*** Bug 1422957 has been marked as a duplicate of this bug. ***
Assigning to Emma for review. Emma, can you look into this one? I'm not sure we do mention 'net_persistence=ifcfg' or 'ifcfg persistence mode' anywhere in our books, so this message may be best positioned as a release note (using the Doc Text field in this bug).
(In reply to Lucy Bopf from comment #4) > Assigning to Emma for review. > > Emma, can you look into this one? I'm not sure we do mention > 'net_persistence=ifcfg' or 'ifcfg persistence mode' anywhere in our books, > so this message may be best positioned as a release note (using the Doc Text > field in this bug). There is no mention of net_persistence=ifcfg' or 'ifcfg persistence mode in the documentation, so I will handle it by writing a doc text for this bug.
Hi Yaniv, As this bug is being handled as doc text only, perhaps we need a KB article to document any steps customers using ifcfg persistence mode should take after upgrading to 4.2.
Hi Edward Shouldn't the target for this bug be 4.2 rather than 4.1? Thanks, Emma
No, we'd like customers to stop using this ASAP, and file a bug for anything that requires using this ancient configurable.
(In reply to Dan Kenigsberg from comment #8) > No, we'd like customers to stop using this ASAP, and file a bug for anything > that requires using this ancient configurable. Hi Dan So we should handle this by adding it to the 4.1 Release Notes, and remove the text "from 4.2"?
yes, please.