Closed jeevanullas closed 11 years ago
I think, I see what we are doing with authentication. Are we using mongo auth instead of using the remote user auth?
We are using mongo auth, but I'll merge this for future use so that we can make things more flexible/capable and give users more options in their deployment. The goal will be to break a lot of this out into parameters to make more options available to users by simply editing varaibles in the varfile
Hi,
While trying to run the playbook, found this happening
Transaction Check Error: file /usr/lib64/audit from install of glibc-2.16-30.fc18.x86_64 conflicts with file from package audit-2.2.1-2.fc18.x86_64
This was on an instance that was booted from image provided by Fedora ( http://fedoraproject.org/wiki/Cloud_images ).
Weird dependency problem and strange error, but it would help if this playbook works on a Fedora 18 instance on AWS, spun of from the official AMI.
Next package added was missing and causing issue with reaching out to the broker API , logs said following
[ pid=3064 thr=17166320 file=utils.rb:176 time=2013-04-08 09:29:44.227 ]: *\ Exception PhusionPassenger::UnknownError in PhusionPassenger::Rack::ApplicationSpawner (Could not find gem 'openshift-origin-auth-remote-user (>= 0) ruby' in the gems available on this machine. (Bundler::GemNotFound)) (process 3064, thread #Thread:0x000000020bdfe0):
Problem was resolved after installing the missing package that provided the gem required for it to work.
Hope this helps, if you have any questions please do let me know.
Cheers! Deependra