Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322970 - [planner] When removing IUs, the default (bundle) fragment is not attached
Summary: [planner] When removing IUs, the default (bundle) fragment is not attached
Status: RESOLVED INVALID
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.6   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-17 23:48 EDT by Ian Bull CLA
Modified: 2010-09-12 04:35 EDT (History)
2 users (show)

See Also:

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

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Bull CLA 2010-08-17 23:48:43 EDT 
I created a profile, and then removed an IU from that profile.  Looking at the operands, the default Bundle fragment (CU) is not attached.  This means that while the IU is removed, it's not unconfigured.

See DirectorApplicationTest#testEPPProfileRemoveIU for the test case.
Comment 1 Ian Bull CLA 2010-08-18 15:32:38 EDT 
This appears only to be a problem with certain IUs.  In this case, ch.logback.* was installed in the profile, but these IUs are not really needed, that is, on the next operation the planner wants to remove them. We first slice the profile, and attach the fragments to only those things in the slice. These IUs are not in that slice (hence they don't have the default CU).
Comment 2 Ian Bull CLA 2010-09-12 04:35:44 EDT 
This is actually not a problem with p2, but rather a problem with the profile we started from.  That is, p2 created a bad profile (see bug 323322), and now when use this, things go south pretty quickly.  (Garbage in -- Garbage out).