This is with qpid-proton installed:
# rpm -qa qpid\*
qpid-proton-c-0.32.0-2.el8.x86_64
qpid-proton-c-devel-0.32.0-2.el8.x86_64
The Gemfile looks like it has 0.26.0, so maybe the RHEL8 qpid-proton is too new?
Well, this seems to be the troublesome line:
@vwbusguy Looks like it is the same on ivanchuk:
then
bundle install --with qpid_proton
That line itself seems the same as ivanchuk-6: https://github.com/ManageIQ/manageiq-providers-openstack/blob/ivanchuk-6/lib/manageiq/providers/openstack/legacy/openstack_event_monitor.rb#L129 - but thtere are at least two added lines in ivanchuk-7
@simaishi I'll try that
@vwbusguy if you don't have manageiq yum repo, you need to add first https://github.com/ManageIQ/manageiq-appliance-build/blob/ivanchuk-7/kickstarts/partials/post/repos.ks.erb#L6-#L9
Looks like that fixed it!
Many thanks @simaishi , @NickLaMuro , @Fryguy !
It seems that I needed to have qpid-proton-c{,devel} installed, and specifically < 0.30.0
So something changed in ivanchuk-7 in the openstack that causes qpid-proton-c to now be required where it used to be optional. I'm not actually using the openstack provider for anything, which might be why I never bothered to install it before.
If it's trying to load qpid_proton when it's not needed, it's an issue in openstack provider. if you're using feature that requires it (openstack event monitor?), but didn't install it because it's not documented, then it's a documentation bug, I think... @agrare is that right?
I wasn't using any openstack features, but evm failed to start without it regardless
being able to run without it is primarily for development purposes
different branch has different version requirement
we could rescue
qpid_proton (LoadError) here but we would also have to make sure to not present STF as an option in the dropdown for event catcher types on the UI/API
This is one of those cases where the demo environment turned into the prod environment because a bunch of unexpected things happened that drew our resources elsewhere...
We were evaluating buying vRealize stuff, so I spun up ManageIQ just to get a sense of what a competing platform was like and generally, most ended up liking ManageIQ much more. Then company financial problems and COVID happened, so we ended up not being able to afford vRealize anyway, but we were already leaning toward MIQ at that point.
that made my week :smile:
Yes, you're right.
cinder manager is working well.
I want to know how swift manager would be working .
If people are curious about cross bot testing, the test by @NickLaMuro are some beautiful reading https://github.com/ManageIQ/miq_bot/blob/3bf7c223ae241db26f69bc0c8a93ece7ca6a2b56/spec/lib/github_service/commands/cross_repo_test_spec.rb