New description:
It seems that we don't need this functionality more. But there are some lines in centos.ks which use yum-version-lock: [0] lines 127, 151-153.
Let's remove these unnecessary lines.
[0] https://github.com/stackforge/fuel-library/blob/stable/5.0/deployment/puppet/cobbler/templates/kickstart/centos.ks.erb
Old description:
SHA commits:
fuel-lib: edf52f8f69a050722532c9ae6fcc8b53ba6f44a4
fuelweb: 2ceae8dbf4ba9abe4ad1e3cbe8c91477ec65fc77
fuel-main: aeea2a7881ec575bffdb4f925dfb44f484abdef2
We added yum-plugin-versionlock to our manifests at May 31 (fuel-library commit 7bbf097e). But we didn't addd it to requirements-rpm.txt file. So all commands 'yum versionlock' (we trying to lock puppet, kernel and iproute2 packages) in Cobbler kickstart files don't work now. Andrey Korolyov said it's good to lock at least kernel and iproute2, so lets add the package to the our repo and introduce it to the master node kickstart.
To do:
1) Add the package to requirements-rpm.txt and update the repo.
2) Add 'yum versionlock' commands to the master node kickstart file like fuel-lib does: https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/cobbler/templates/kickstart/centos.ks.erb
We need to request package from OSCI team