Closed Bug 14330 Opened 21 years ago Closed 21 years ago
Last of 4
.x profiles migrates 'automatically'
Steps to reproduce: 1. create 3 4.x profiles 2. run apprunner -installer, migrate profile1 3. run apprunner -installer again (or apprunner -ProfileManager or apprunner -mail) and migrate profile2 4. Run apprunner a third time Actual Result: remaining profile, profile3, will show as migrated. Expected results: 3rd profile would display with 'migrate' tag to show it needed migration On Win32 machines, checking Linux, n/a on Mac yet
This is a Profile Manager issue. Reassigning to Bhuvan.
I have noticed that we are checking only the number 4.x profiles. That is incorrect. We need to add another condition i.e., number of 5.0 profiles should be zero for automatic migration. Will check in the fix when tree gets opened.
Moving the TFV to M12. Fix along with other migration bugs.
Component: Profile Migration → Profile Manager
Target Milestone: M12 → M13
Will be fixed along with cleanup changes. Until the status is updated, the TFV is M13.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Fixed. Automigration happens only when the number of 5.0 profiles is 0 (ZERO) and the number of 4x profiles is exactly 1 (ONE). Marking Fixed.
Moving all Profile Manager bugs to new Profile Manager Backend component. Profile Manager component to be deleted.
You need to log in before you can comment on or make changes to this bug.