Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Jason Frey
@Fryguy
cool thanks
Adam Grare
@agrare
:+1:
also can you run bundle config with from /var/www/miq/vmdb
Scott Williams
@vwbusguy
This isn't an appliance, but it's installed on top of a base RHEL8, so the pathing isn't the same, but I did a bundle update as part of the upgrade
Jason Frey
@Fryguy
ok, then can you run that from the application root dir?
Scott Williams
@vwbusguy
sure
From the app root
bin/bundle config
Settings are listed in order of priority. The top value will be used.
jobs
Set for your local app (/opt/manageiq/manageiq/.bundle/config): 3

gemfile
Set via BUNDLE_GEMFILE: "/opt/manageiq/manageiq/Gemfile"
I'm restarting ivanchuk-6 with qpid-proton-c{,-devel} installed just to see if there's any difference
The setup on this is 2 RHEL8 machines, with one of them just serving postgres, and the other having manageiq installed via git, with manageiq-api and manageiq-providers-redfish being overridden since they include patches that weren't in the ivanchuk branch (at least at the time). I updated those as well by git merge before running evm.
Scott Williams
@vwbusguy
I don't see any errors for qpid-proton in ivanchuk-6 with it installed
Let me take another snapshot and I'll try the ivanchuk-7 upgrade again
Maybe it somehow makes a difference having qpid-proton-c installed first before upgrading? I can't imagine how, though.
Scott Williams
@vwbusguy
Here's the stack trace:
[----] I, [2020-11-13T09:39:33.861823 #25283:2b0453a305d4]  INFO -- : 
---
:guid: e56bf3b0-f39f-41ce-a888-5c7f0ad1217f
/usr/share/gems/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:292:in `require': cannot load such file -- qpid_proton (LoadError)
    from /usr/share/gems/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:292:in `block in require'
    from /usr/share/gems/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:258:in `load_dependency'
    from /usr/share/gems/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:292:in `require'
    from /usr/share/gems/bundler/gems/manageiq-providers-openstack-41275114e535/lib/manageiq/providers/openstack/legacy/events/openstack_stf_event_receiver.rb:1:in `<top (required)>'
    from /usr/share/gems/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:292:in `require'
    from /usr/share/gems/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:292:in `block in require'
    from /usr/share/gems/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:258:in `load_dependency'
    from /usr/share/gems/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:292:in `require'
    from /usr/share/gems/bundler/gems/manageiq-providers-openstack-41275114e535/lib/manageiq/providers/openstack/legacy/events/openstack_stf_event_monitor.rb:4:in `<top (required)>'
    from /usr/share/gems/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:292:in `require'
    from /usr/share/gems/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:292:in `block in require'
    from /usr/share/gems/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:258:in `load_dependency'
    from /usr/share/gems/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:292:in `require'
    from /usr/share/gems/bundler/gems/manageiq-providers-openstack-41275114e535/lib/manageiq/providers/openstack/legacy/openstack_event_monitor.rb:131:in `block in <top (required)>'
    from /usr/share/gems/bundler/gems/manageiq-providers-openstack-41275114e535/lib/manageiq/providers/openstack/legacy/openstack_event_monitor.rb:131:in `each'
    from /usr/share/gems/bundler/gems/manageiq-providers-openstack-41275114e535/lib/manageiq/providers/openstack/legacy/openstack_event_monitor.rb:131:in `<top (required)>'
    from /usr/share/gems/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:292:in `require'
    from /usr/share/gems/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:292:in `block in require'
    from /usr/share/gems/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:258:in `load_dependency'
    from /usr/share/gems/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:292:in `require'
    from /usr/share/gems/bundler/gems/manageiq-providers-openstack-41275114e535/app/models/manageiq/providers/openstack/cloud_manager/event_catcher.rb:9:in `all_valid_ems_in_zone'
    from /opt/manageiq/manageiq/app/models/mixins/per_ems_worker_mixin.rb:32:in `desired_queue_names'
    from /opt/manageiq/manageiq/app/models/mixins/per_ems_worker_mixin.rb:38:in `sync_workers'
    from /opt/manageiq/manageiq/app/models/miq_server/worker_management/monitor.rb:54:in `block in sync_workers'
    from /opt/manageiq/manageiq/app/models/miq_server/worker_management/monitor.rb:50:in `each'
    from /opt/manageiq/manageiq/app/models/miq_server/worker_management/monitor.rb:50:in `sync_workers'
    from /opt/manageiq/manageiq/app/models/miq_server.rb:156:in `start'
    from /opt/manageiq/manageiq/app/models/miq_server.rb:247:in `start'
    from /opt/manageiq/manageiq/lib/workers/evm_server.rb:27:in `start'
    from /opt/manageiq/manageiq/lib/workers/evm_server.rb:48:in `start'
    from /opt/manageiq/manageiq/lib/workers/bin/evm_server.rb:4:in `<main>'
So it does look like it's related to the openstack provider
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?
Scott Williams
@vwbusguy
Does it matter that that's on master branch and not ivanchuk?
Satoe Imaishi
@simaishi
@vwbusguy you need 0.29.x rpm for ivanchuk branch.ManageIQ/manageiq-appliance-build#410
Satoe Imaishi
@simaishi
can you uninstall 0.32, then run the yum-config-manager command in that PR, then install again? that should install 0.29.x
then bundle install --with qpid_proton
Scott Williams
@vwbusguy
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
Satoe Imaishi
@simaishi
Scott Williams
@vwbusguy
@simaishi I was able to get to 0.29.0 with a few dnf downgrades. I'll add it to excludes= for now
Satoe Imaishi
@simaishi
ok
Scott Williams
@vwbusguy
I ran the bundle install and am trying to start evm again now
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.
Scott Williams
@vwbusguy
About it being required now, should I file an issue for it in manageiq-providers-openstack?
Satoe Imaishi
@simaishi
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?
Adam Grare
@agrare

That line itself seems the same as ivanchuk-6

The difference is the STF event monitor was added in ivanchuk-7

Scott Williams
@vwbusguy
So it seems like a documentation issue then, as qpid-proton-c <0.30.0 is now required
I wasn't using any openstack features, but evm failed to start without it regardless
Adam Grare
@agrare
It is something we could handle but we never expected to be running the full-up server without qpid-proton installed
being able to run without it is primarily for development purposes
Scott Williams
@vwbusguy
So it sounds like it should probably just be required then?
Satoe Imaishi
@simaishi
< 0.30.0 is only for ivanchuk, fyi
different branch has different version requirement
Adam Grare
@agrare
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
Scott Williams
@vwbusguy
We're planning on moving to containers for jansa anyway, so I imagine those deps will be handled at the image level at that point
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...
Adam Grare
@agrare
correct
Scott Williams
@vwbusguy
But the upside is, I get to learn more about how MIQ works this way :-)
Adam Grare
@agrare
:laughing: I like the optimism!
Scott Williams
@vwbusguy
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.
Jason Frey
@Fryguy

and generally, most ended up liking ManageIQ much more

💕💖