Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Nicolas Marcq
@Sispheor

Hi there. I’m pretty new on ManageIQ. I’m trying to figure out how to manage secrets/credentials with Ansible playbboks.

Here is my case. I have multiple Openshift cluster. Each cluster could be attached to a “location”.
I would like to get the token of the cluster depending of the selected location from the dialog.

How I’m supposed to manage it with Embedded Ansible? The only way is to store my tokens in a variable file and vault them?

Like:

ocp_token_location_map:
  locationA:
    token: XXXX  # here I use vault
    url: openshift-a.domain.com
  locationB:
    token: XXXX  # here I use vault
    url: openshift-b.domain.com

I would like to split this kind of variable from my core repository that perform actions on the clusters. I should add a task that will git clone the variables?

Or maybe I should use here generic objects?

Thanks for any advice.

Jason Frey
@Fryguy
@vwbusguy I'm surprised that the upgrade gave that error... @simaishi does that make sense :point_up: November 12, 2020 7:32 PM
Satoe Imaishi
@simaishi
@vwbusguy how was the upgrade performed? Also, can you check which version of qpid-proton rpm you have on the system (rpm -qa |grep qpid-proton)?
Peter McGowan
@pemcg
@Sispheor are your OpenShift clusters already registered as providers in MIQ? If so your service dialog method can pull out the token for the selected cluster from the VMDB and write it to a password element in the service dialog (which is obfuscated rather than clear text). This should then be passed automatically to your playbook service
Nicolas Marcq
@Sispheor
Thx @pemcg . I'll give a try.
JVue
@JVue
Hello… I have an intermittent duplicate vm name problem when we request multiple VMs (qty) within the same catalog request… it appears sometimes the individual requests run nearly in parallel with each other, creating a race condition which creates duplicate names. We have an enterprise setup with multiple miq worker servers. Currently running Hammer5… Anyone come across this before and if there any known solutions/workarounds (perhaps without significant rearchitecting or recoding using some kind of mutex or queueing, etc solution?)
Scott Williams
@vwbusguy
@simaishi - git merge ivanchuk-7 and running the setup again. That worked for me from ivanchuk-5 to ivanchuk-6.
I reverted back to ivanchuk-6 via snapshot and it's running again. Was there any obvious dep change for qpid-proton between ivanchuk-6 and ivanchuk-7?
I have no qpid_proton rpms installed. Looks like it's an optional dep from the Gemfile, but seems to not actually be optional in ivanchuk-7.
Satoe Imaishi
@simaishi
all ivanchuk appliances should have qpid-proton-c/qpid-proton-c-devel rpms installed...
Scott Williams
@vwbusguy
This isn't from an appliance. It's installed on RHEL8 from git.
Jason Frey
@Fryguy
still, if if was working on ivanchuk-6 I think you would have had to have it installed previously?
Scott Williams
@vwbusguy
But I installed qpid-proton-c and tried the 3 that were in the repo yesterday and none of them were able to be loaded for activesupport. Those were 0.29.0, 0.30.0, and 0.32.0
The three rubygem versions, that is
@Fryguy Well, I have an ivanchuk-6 instance working here without it
Jason Frey
@Fryguy
interesting
Scott Williams
@vwbusguy
rpm -qa |grep qpid-proton
retruns nothing
*returns
Fryguy @Fryguy looks at what changed between 6 and 7
Scott Williams
@vwbusguy
It's optional in the Gemfile, IIRC
group :qpid_proton, :optional => true do
ivanchuk-6 had 0.26.0 and I think ivanchuk-7 is either 0.29.0 or 0.30.0
0.26.0 isn't in the repos
Jason Frey
@Fryguy
it shouldn't install the gem at all though if it's optional and you don't want it
Satoe Imaishi
@simaishi
ivanchuk should be using 0.29.x rpm
Scott Williams
@vwbusguy
I don't mean to not install it. It just appears to have broken ivanchuk-7 by activesupport not being able to grok it
Jason Frey
@Fryguy
Can you give the full stack trace of the error you are seeing?
Scott Williams
@vwbusguy
I think what I'll do is install qpid-proton-c on ivanchuk-6 and see what happens with it installed
Jason Frey
@Fryguy
:+1:
Scott Williams
@vwbusguy
I'm not sure what info I'm expecting from that, but I'd like to have an upgrade path before we eventually migrate to a k8s based deployment
Jason Frey
@Fryguy
but if anything that should have made it more optional
Scott Williams
@vwbusguy
Yeah - I would think so
Jason Frey
@Fryguy
@agrare Can you help out here?
Scott Williams
@vwbusguy
I wonder if activesupport changed
Maybe it's now a hard dep for activesupport where it didn't used to be
Jason Frey
@Fryguy
I don't understand how activesupport is involved at all (I think it's just a coincidence in the stacktrace, hence why I was asking for the full trace)
I think that line is just telling us that something else is requiring it (and activesupport messes with the require chain)
Scott Williams
@vwbusguy
Sadly, I reverted the machine via snapshot, so I don't have the log any more. But I can try again later on today.
Jason Frey
@Fryguy
There's also this commit @simaishi - ManageIQ/manageiq-pods#611 (but that's pods?)
Adam Grare
@agrare
@vwbusguy can you tell where it is being required from?
Scott Williams
@vwbusguy
/usr/share/gems/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:292:in `require': cannot load such file -- qpid_proton (LoadError)
Adam Grare
@agrare
that's just the first line of the exception, we need the full stack trace to see where it is being required from
Jason Frey
@Fryguy
yeah that got lost :(
Scott Williams
@vwbusguy
I reverted the machine back via snapshot. I can try again later today, though
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?