Quick confirmation re: foreman_ansible v2.3.0

Support
23

Sorry for the delay. Installing this right now. :slight_smile:

25

@Marek_Hulan

Just got this error message:

rpm -ivh tfm-rubygem-foreman_ansible-2.3.0-1.fm1_20.el7.noarch.rpm tfm-rubygem-foreman_ansible_core-2.2.0-1.fm1_21.el7.noarch.rpm

error: Failed dependencies:
        foreman-webpack-vendor-js(67078bd27be779a58ba6) is needed by tfm-rubygem-foreman_ansible-2.3.0-1.fm1_20.el7.noarch

Am I missing a step?

26

Hi,
I checked my Foreman version 1.20 build on Centos 7 and you may be missing the below rpm:

root@ansible01 ~]# rpm -qa | grep webpack
tfm-rubygem-webpack-rails-0.9.8-3.el7.noarch

1 Like
27

Thanks @flaporta, I appreciate the tip. I found the file here for anyone else looking to install it as well. I’ll give that a try.

28

Hmmm…that doesn’t seem to resolve the issue:

rpm -iv tfm-rubygem-webpack-rails-0.9.8-3.el7.noarch.rpm

Preparing packages...
        package tfm-rubygem-webpack-rails-0.9.8-3.el7.noarch is already installed

Any other ideas on how to resolve foreman-webpack-vendor-js(67078bd27be779a58ba6)?

29

foreman-webpack-vendor-js(67078bd27be779a58ba6) is provided by foreman 1.20.0-1.

1 Like
30

@tbrisker I just upgraded to 1.20.1, however, I’m still getting the same error:

31

Note that i mentioned 1.20.0-1 specifically :slight_smile:
I’ll be announcing 1.20.1 tomorrow, with further details about the incompatibility we’ve had there with the vendor.js file.
foreman-ansible has also been rebuilt to work with 1.20.1, but only 2.2.11 has been rebuilt as 2.3 isn’t yet in the 1.20 plugins repo, only in nightly. since 2.3.0 was built against 1.20.0, you’ll need to use it with the foreman-1.20.0-1.el7.noarch.rpm package until it gets rebuilt against 1.20.1.

1 Like
32

Ahhhhh… I was wondering if that was the cause! Thanks for the clarification on that. :slight_smile:
If I’m already 1.20.1, is it safe to install foreman-1.20.0-1.el7.noarch.rpm? Should I just wait?

33

Yes, downgrading from 1.20.1 to 1.20.0 should be safe to do.

1 Like
34

Awesome, ty!

35

just an update, during packaging we found one more issue with 2.3-stable branch, we’ll need to release 2.3.1 once fixed, I’ll let you all know when we have new scratch builds to test

1 Like