[plugin] rpm/yum work incorrectly with Fuel plugins

[Sergii Golovatiuk]

fuel plugin builder generates rpm. Making rpm means that it should be installed using rpm -i, yum install
However, yum install doesn't work properly as after installation it requires

fuel plugins —sync

which should be added to post: section of plugin's RPM specification. Operator should use regular commands instead of some tricky

fuel plugins --install $RPM —force

which has very bad UX for operator. Operator should use regular commands. wget/yum install only instead of any other commands

Same should be applied to rpm -e/yum remove. As when I do

rpm -e $PLUGIN

I still see configuration in database with

fuel plugins --install $RPM
or
fuel plugins —sync

%preun and %postun should be updated to run

fuel plugins --remove plugin==ver

[OpenStack Infra (hudson-openstack)]

Change abandoned by Maciej Kwiek (<email address hidden>) on branch: master
Review: https://review.openstack.org/209498
Reason: Bug was deemed invalid

[Evgeniy L (rustyrobot)]

It's by design was done this way, in rpm world people don't expect that during the installation of rpm some **REST API** calls to third party service will be performed. Doing it the way it's described in the ticket breaks system administrator's expectations and common practice accepted in this packaging system.

[Sergii Golovatiuk (sgolovatiuk)]

This bug is valid. People are allowed to use *yum*, thus there should be some calls. Many RPMs contain rules to remove database on package removal. At the moment UX is very bad as it's not intuitive for operators and plugin developers.

[Vladimir Sharshov (vsharshov)]

This bug describe new behavior for fuel plugins. Does not affect deployment. Moving to 8.0

[Alexander Kislitsky (akislitsky)]

We passed SCF in 8.0. Moving the bug to 9.0.