Bug 1697467

Summary: Extending a RHV storage causes duplication and does not copy tags over
Product: Red Hat CloudForms Management Engine Reporter: Felix Dewaleyne <fdewaley>
Component: ProvidersAssignee: Boriso <bodnopoz>
Status: CLOSED ERRATA QA Contact: Angelina Vasileva <anikifor>
Severity: medium Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: medium    
Version: 5.10.1CC: bodnopoz, dmetzger, fdewaley, gekis, jfrey, jhardy, jocarter, mperina, mshriver, obarenbo, simaishi, smallamp
Target Milestone: GA   
Target Release: 5.11.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: 5.11.0.15 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-12 13:36:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: RHEVM Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1704905    

Description Felix Dewaleyne 2019-04-08 13:17:22 UTC 
Description of problem:
Extending a RHV storage  causes duplication and does not copy tags over

Version-Release number of selected component (if applicable):
5.10.2

How reproducible:
customer environment

Steps to Reproduce:
1.configure a CloudForms 5.10.2 with a RHV provider
2.refresh the provider
3. tag the storages
4. provision and retire a couple vms
5. extend the storages that were used by the vms retired (and are in use in others)

Actual results:
the storage is duplicated in the UI , tags are not copied into the new storage

Expected results:
only the current storage shows, with all the relevant tags.

Additional info:
the tag issue broke automation, customer is arguing that the old record should not show into the UI, only the latest, valid one.
customer refused to provide a database dump for security reasons
Comment 12 Angelina Vasileva 2019-11-11 08:44:29 UTC 
Fixed and verified in 5.11.0.27.20191001204742_d9cf38b.
Comment 14 errata-xmlrpc 2019-12-12 13:36:21 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:4199