Description of problem:
As described in the upstream bug @ https://bugs.launchpad.net/tripleo/+bug/1630247 Sahara services go from default On in OSP9 but default Off for OSP10.
This bug is to track the related changes for the downstream package builds (see upstream bug for details on reviews)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Adding a note here on request:
For the duration of the OSP9 to OSP10 upgrade we handle this special case and default to keeping the existing sahara services, both after the controller upgrade step and after the converge step. This is done with the review at  which has now landed into stable/newton.
However, *any* subsequent stack update operations will *have* to include the existing -e 'services/sahara.yaml'  environment file, as part of the deployment command. Not doing so would mean that none of the Sahara related configuration would be effected, since by default Newton specifies that sahara services map to 'OS::Heat::None' 
If the operator decides they do *not* want sahara after their upgrade, they need to include the provided -e 'major-upgrade-remove-sahara.yaml' environment file as part of the deployment command for the controller upgrade and converge steps. The sahara services would not be restarted after the major upgrade in this case.
moved to POST as it merged into newton upstream
I am seeing the same thing with Upgrade from OSP 8 to OSP 9 is the same fix available for this?
What rpm supplies the -e 'major-upgrade-remove-sahara.yaml'?
I have installed the following:
Hi Randy - I think you are seeing the opposite in fact. There was no sahara in 8 and then it was introduced as a service in 9 (so you would have gained a sahara service after upgrading 8->9).
The 'major-upgrade-remove-sahara.yaml' is new for Newton (see the gerrit review above in external trackers) so will be part of the 10 release.
I see you have filed two bugzillas which must be related to what you're seeing (BZ 1387344 and 1387343 - will comment there momentarily) but the fix for this bug is specific to a Mitaka to Newton upgrade (and so OSP9-->OSP10) and where the default path is to *keep* sahara, unless the operator chooses not to by including that env. file
Deployed RHOS 9 successfully
Upgrade 9-> and included /usr/share/openstack-tripleo-heat-templates/environments/major-upgrade-remove-sahara.yaml
during the control and convergence steps and upgrade was successful.
I saw no issues with controller and everything running
[heat-admin@controller-0 ~]$ sudo systemctl list-unit-files | grep sahara
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.