search

oswaldlabs / chef-rundeck

Integrates Chef with RunDeck, we are referring users to https://github.com/atheiman/better-chef-rundeck as this repository is inactive at this time.
Apache License 2.0
97 stars 85 forks source link

Not able to search Chef nodes on old chef server #58

Open bhalothia opened 10 years ago

bhalothia commented 10 years ago

We are using an older version of chef server (10.10) for our server configuration management. I wanted to test Rundeck as an orchestration tool for our operations pipeline so I installed this chef-rundeck plugin as per instructions. I'm not able to access the sinatra webapp on 9980 port.

In the log it says, it's searching for nodes but nothing shows up in the UI. We have around 200 nodes but I don't think that can be an issue.

Here's the gist with all logs: https://gist.github.com/bhalothia/7068bd4a34f0cd96f1e3

When I tried to curl the webapp, it gives me this:

curl: (52) Empty reply from server

Is it a known issue? I tried to look up the threads but couldn't find any relevant match.

Also, this plugin works well with a chef 11 server, which I set up for the POC.

leftathome commented 10 years ago

If I'm reading that gist correctly, it looks like you are (were?) trying to run chef-rundeck on Ruby 1.8 with the Chef 11 client gem. On the one hand, I think the Chef 11 client is supposed to "do the right thing" when speaking to a Chef 10 server (just make sure chef-rundeck doesn't try to use partial search for its query).

However, if you're running the whole thing on Ruby 1.8 ... I think Chef 11 is targeted for Ruby 1.9 in all omnibus installs and I don't know if 1.8 is a supported environment. I'm pretty sure we do not test for it in chef-rundeck, so I'd be equally surprised to find out it was broken as to find out that it worked for you in that environment.

About all I can recommend is that you use an older version of chef-rundeck until you can upgrade your Chef server. I know it's kind of a cliche for the open source maintainer of something to callously tell someone in your situation "UPGRADE LOLZ" but in this case you're really moving to a much more stable, efficient and easer-to-operate system by doing so. I also know from my own bitter experience that going from 10 to 11 is a pretty ... um ... exciting upgrade. You may want to stand up the Chef 11 server, migrate your objects to it and then just pivot all your nodes to the new server rather than attempt an upgrade in place. That can be pretty bad times.

The Chef folks tell me that upgrading from Chef 11 Server to Chef 12 Server will be a snap, though.

If you're still stuck in this situation and want to pursue further troubleshooting against the latest version of chef-rundeck, then run that curl test of yours again with the chef-rundeck app logging at debug level or higher and send that along. I promise I'll respond in less than 2 months this time. ;)

(Sorry about that, by the way)