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
I just posted where the root problem was (and it isn't that)
Anyone seen problem with embedded ansible in kubernetes deployment? I'm getting and error when I try to run playbook. it complains about permissions on /root/.ansible. If I exec into container I can see that indeed /root is missing write permissions.
[root@1-generic-8d88f4d7-v9vnz /]# ls -lad /root/
dr-xr-x---. 1 root root 4096 Nov 17 08:47 /root/
thus ansible can't create .ansible directory inside root. there are few possible solutions for that issue:
- grant write to owner on /root
- change temp dir location to /tmp, like here https://stackoverflow.com/a/49747156
thing is can't see where it's coming from though, there is no reports of this issue on github issues, so I'm not sure if this is something about my particular deployment or it's a genuine issue. Any thoughts?
After some digging I ended up with the following:
- it's known issue in centos,rhel - CentOS/sig-cloud-instance-images#67
- my containers were running with requiredDropCapabilities: ["ALL"], depriving container of CAP_FOWNER that would allow bypass permission checks on operations that normally require the filesystem UID of the process to match the UID of the file, thus allowing access even owner permissions is wrong.
"timed out stalled task"
Is there anyone who can help me?
if this was a development setup are you running
simulate_queue_worker ?