When adopting the OpenStack Manila service configured with Ceph NFS from RHOSP 17.1 into RHOSO 18:

• The "standalone" Ceph NFS service deployed with TripleO/RHOSP Director is not adopted
• Instead, a new "ceph nfs" cluster is created on Ceph and Manila is configured to interact with it instead
• The old standalone Ceph NFS is not decomissioned immediately; and the prior VIP is configured with RHOSO 18 so that export paths of existing shares are still displayed for the convenience of users as they migrate.

The export paths belonging to the prior standalone Ceph NFS service must be annotated as "preferred: False" to allow humans and automation to parse the correct export path when migrating their applications. 

This was however not the case.