+++ This bug was initially created as a clone of Bug #1740325 +++
Description of problem:
Since Sahara is targeted for removal in OSP16, we need to a way to remove Sahara before a customer can FFU to OSP16.
Version-Release number of selected component (if applicable):
13 (although the upgrade target version is 16)
Expected results:
When a customer tries a FFU with Sahara enable it should by default fail.
There should be a process to remove Sahara from OSP13:
1/ An ad-hoc process that runs on OSP13
OR
2/ The process is part of the FFU, the operator explicitly mentions he wants to have Sahara removed
Additional info:
-------
Originally scheduled for 16.2, set as TestOnly, requires proper assessment.