-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
rhel-idm-ipa
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
Goal
- As an administrator, I expect ipa-migrate to be able to migrate most data from existing deployment - everything possible, created with common IPA tools (API, CLI), except the specifically listed data (e.g. CA keys, kerberos keys, etc.)
Acceptance criteria
A list of verification conditions, successful functional tests, or expected outcomes in order to declare this story/task successfully completed.
- ensure migration of all user-created data that doesn't violate the default IPA setup (e.g. schema extensions, custom attributes etc. are not expected to be migrated by default)
- ensure graceful handling of errors while adding entries and errornous entries (e.g. conflict entries)
- relates to
-
RHEL-153852 ipa-migrate doesn't migrate IPA locations
-
- New
-
-
RHEL-153853 ipa-migrate doesn't migrate custom realm domains
-
- New
-
-
RHEL-153855 ipa-migrate doesn't migrate RBAC delegations
-
- New
-
-
RHEL-153856 ipa-migrate fails to update existing entries: error: Type or value exists
-
- New
-
-
RHEL-153857 ipa-migrate doesn't properly handle replication conflicts
-
- New
-
-
RHEL-153858 ipa-migrate doesn't migrate custom password policies
-
- New
-
-
RHEL-154389 ipa-migrate doesn't copy ACI for IPA RBAC permissions
-
- New
-
-
RHEL-147173 ipa-migrate doesn't process users' sshpublickeys
-
- In Progress
-