mco prints non-intuitive error when running from unconfigured account
|Assignee:||R.I. Pienaar||% Done:|
|Keywords:||Affected mCollective version:||1.2.1|
If you haven’t set up mc for your user account (e.g., if you forget to switch to the peadmin user on the training VM) before running mco, you get an unintuitive error message.
[root@nigel ~]# mco find connect to nigel.puppetlabs.lan failed: can't convert nil into String will retry(#0) in 5 connect to nigel.puppetlabs.lan failed: can't convert nil into String will retry(#1) in 5 [...] find failed to run: Could not connect to Stomp Server: (RuntimeError) [root@nigel ~]#
#2 Updated by R.I. Pienaar over 1 year ago
- Status changed from Accepted to Closed
Investigated this, there’s literally nothing I can do about it – that error message comes from the stomp gem, the stomp gem has better means of error reporting but the PE setup is not configured to use that. Either way, we do not control the stomp gem so not much we can do about it.
The root cause is due to a setup bug in PE, I’ll open a ticket for that though.