Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1429809

Summary: [Docs][Admin][Tech] Deprecation notice of net_persistence=ifcfg
Product: Red Hat Enterprise Virtualization Manager Reporter: Edward Haas <edwardh>
Component: DocumentationAssignee: Emma Heftman <eheftman>
Status: CLOSED CURRENTRELEASE QA Contact: Tahlia Richardson <trichard>
Severity: medium Docs Contact:
Priority: high    
Version: 4.1.0CC: danken, edwardh, lbopf, lsurette, rbalakri, srevivo, ykaul, ylavi
Target Milestone: ovirt-4.1.1-1   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Deprecated Functionality
Doc Text:
IFCFG persistence mode has been declared deprecated. The Unified persistence mode has been the default from version 3.5 and should now be used in all systems.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-13 10:51:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Docs RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Edward Haas 2017-03-07 06:59:20 UTC
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.

Comment 1 Yaniv Lavi 2017-03-08 09:14:29 UTC
We need to make sure this is clearly mentioned.

Comment 2 Lucy Bopf 2017-03-23 06:58:58 UTC
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?

Comment 3 Lucy Bopf 2017-03-30 01:41:39 UTC
*** Bug 1422957 has been marked as a duplicate of this bug. ***

Comment 4 Lucy Bopf 2017-04-06 01:53:43 UTC
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).

Comment 5 Emma Heftman 2017-04-09 07:58:00 UTC
(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.

Comment 6 Emma Heftman 2017-04-09 08:03:21 UTC
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.

Comment 7 Emma Heftman 2017-04-09 08:05:18 UTC
Hi Edward
Shouldn't the target for this bug be 4.2 rather than 4.1?
Thanks, Emma

Comment 8 Dan Kenigsberg 2017-04-09 08:36:41 UTC
No, we'd like customers to stop using this ASAP, and file a bug for anything that requires using this ancient configurable.

Comment 9 Emma Heftman 2017-04-09 08:52:32 UTC
(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"?

Comment 10 Dan Kenigsberg 2017-04-09 10:12:47 UTC
yes, please.