IT37915: ALL OTHER VMS REMOVED FROM SLA WHEN A PREVIOUSLY REMOVED VM IS READDED

APAR status

• Closed as program error.

Error description

• After removing a Virtual Machine (VM) or folder from a SLA in
  IBM Spectrum Protect Plus and adding it back to this same SLA at
  a later stage, all other VMs are removed from this SLA.
  
  
  The issue can be seen after following these steps:
  1. Assign an SLA to a complete datacenter --> all the folders
  and VMs in the datacenter are added to the SLA.
  2. Remove a single folder or VM from the SLA --> the folder and
  the VMs in it, or the single VM in case a single VM was removed,
  are removed from the SLA. Others remain in the SLA as expected.
  3. Add this single folder or VM back to the SLA --> this folder
  and all VMs in it (or the single VM) are readded to the SLA, BUT
  ALL other VMs and folders are removed from the SLA.
  
  
  | MDVREGR 10.1.7.0-TIV_5737SPLUS |
  
  IBM Spectrum Protect Plus Versions Affected:
  IBM Spectrum Protect Plus 10.1.8
  
  Additional Keywords: SPP, SPPlus, TS005889414
  

Local fix

• Manually add all VMs back to the SLA.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus level 10.1.8                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply the fixing level when available. This problem is       *
  * currently projected to be fixed in IBM Spectrum Protect Plus *
  * level 10.1.8 ifix2 and 10.1.9.                               *
  ****************************************************************
  

Problem conclusion

• A bug in the comparison of children and parents (children were
  treated as parents and vice-versa) in the storage profile
  association logic caused siblings of a resource (such as a VM)
  to have a storage profile removed when the same storage profile
  is added to the resource. This bug has been corrected so that
  siblings are no longer cleared when a storage profile is
  associated with a resource.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• Platform App      Hyperv
  

Fix information

• Fixed component name

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels