Description of problem: fog-kubevirt is not latest with all the fixes of fog-kubevirt. It is causing error in provider. Version-Release number of selected component (if applicable): 5.10.0.29 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
New commit detected on ManageIQ/manageiq-providers-kubevirt/hammer: https://github.com/ManageIQ/manageiq-providers-kubevirt/commit/fca04ce5d98d380ca57d24a6724348d5b3d239f8 commit fca04ce5d98d380ca57d24a6724348d5b3d239f8 Author: Gregg Tanzillo <gtanzill> AuthorDate: Mon Dec 3 16:06:46 2018 -0500 Commit: Gregg Tanzillo <gtanzill> CommitDate: Mon Dec 3 16:06:46 2018 -0500 Merge pull request #125 from pkliczewski/master gemspec: use latest fog-kubevirt (cherry picked from commit 9b94e38db0d8b5567ddc3494bcd30f67cfac45e1) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1660099 manageiq-providers-kubevirt.gemspec | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
The following PRs are also backported to hammer branch due to gem version conflicts: https://github.com/ManageIQ/manageiq/pull/18256 https://github.com/ManageIQ/manageiq-providers-kubernetes/pull/311 https://github.com/ManageIQ/manageiq-providers-kubernetes/pull/263
@Piotr, Do we want to address this issue along with https://github.com/fog/fog-kubevirt/issues/57
@Vatsal I think it is different issue. Once it is fixed we need to make sure it is backported.
Able to see the new version of fog-kubevirt in 5.10.0.31 ``` [root@host-192-168-100-238 vmdb]# gem list | grep fog-kubevirt fog-kubevirt (0.1.8) ```