Don’t overwrite supervisor config

[Aleksey Zvyagintsev]

Due upgrade process, superviors configs overwrites by function from :
https://github.com/stackforge/fuel-web/blob/master/fuel_upgrade_system/fuel_upgrade/fuel_upgrade/utils.py#L170-L184

using this template
https://github.com/stackforge/fuel-web/blob/master/fuel_upgrade_system/fuel_upgrade/fuel_upgrade/templates/supervisor.conf

So, that means - partial loosing configuration from :
(at least, prioritizing)
https://github.com/stackforge/fuel-library/tree/master/deployment/puppet/docker/files/supervisor

Please, refactor this function for merge process, or something else.

[Evgeniy L (rustyrobot)]

I can suggest the next flow.

If there is config, don't generate own config and use existing instead.
During the upgrade autostart parameter should be set for existing config accordingly to upgrade logic.

If there is no config for service, upgrade script should generate it's own config.
It's required because Docker upgrade can be run without any other upgrade engines, it simplifies testing and debugging process.

[Aleksey Zvyagintsev (azvyagintsev)]

Guys, please move fix-time at least in 6.1

[Dmitry Pyzhov (dpyzhov)]

We agreed that this bug is Medium and can be moved to 7.0

[Vladimir Sharshov (vsharshov)]

Known issue. Can be safely moved to 8.0

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/222051

[OpenStack Infra (hudson-openstack)]

Change abandoned by Igor Kalnitsky (<email address hidden>) on branch: master
Review: https://review.openstack.org/222051
Reason: It was decided to use backup-restore upgrade approach . Moreover, fuel-upgrade has its own repo now.