Bug 1023583 - Blivet.copy does not update parted disk refs for partitions on hidden disks
Summary: Blivet.copy does not update parted disk refs for partitions on hidden disks
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: python-blivet
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: David Lehman
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On: 1023556
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-25 20:19 UTC by David Lehman
Modified: 2021-09-03 14:10 UTC (History)
5 users (show)

Fixed In Version: python-blivet-0.18.9-1
Doc Type: Bug Fix
Doc Text:
Clone Of: 1023556
Environment:
Last Closed: 2014-06-13 11:38:58 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description David Lehman 2013-10-25 20:19:14 UTC 
+++ This bug was initially created as a clone of Bug #1023556 +++

Description of problem:
During a deep-copy of blivet we have to update the parted.Partitions so they are associated with the same instance of parted.Disk that is in the newly copied disk's format instance. We failed to perform the same update on partitions that reside on hidden disks (eg: disks not selected during OS installation).

Version-Release number of selected component (if applicable):
python-blivet-0.18.7-1

How reproducible:
Always (using anaconda)

Steps to Reproduce:
1. select one of two full disks, choose custom, clear disk, autopart, save
2. revisit storage, select both disks, choose reclaim, delete all, reclaim

Actual results:
traceback from pyparted saying partition (on previously hidden disk) is not part of the disk it is being removed from

Expected results:
successful clearing and reinitialization, then autopart, of both disks

Additional info:
Comment 3 Ludek Smid 2014-06-13 11:38:58 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.