I'm not sure when this error started occurring, but I first noticed it
today when attempting to a delete a host from the Foreman GUI. I'm running
Foreman 1.3.1 on CentOS 6.4, apache 2.4.9, passenger 4.0.38, ruby 1.8.7.
It sounds like this is something fog-related, but I've never had an issue
before. I'm not sure how to tell what version of fog foreman is looking
at, so let me know if I can give more info than this:
me@foremanhost:/usr/local/foreman> gem list fog
*** LOCAL GEMS ***
fog (1.19.0, 1.18.0, 1.15.0, 1.9.0)
Here's the steps to reproduce the issue:
http://foremanhost:4000/compute_resources/new
Provider: VMware
On next page, I enter credentials for my vcenter server and click Load
Datacenters and then I get the error: "vsphere is not a recognized compute
provider"
I also get this when attempting to delete a host that is tied to one of my
existing compute resources.
On a related note, I tried to upgrade to 1.4.2 recently, ran into some
issues, then tried 1.3.2 which went smoothly, but thought this issue was a
bug in 1.3.2 so I went back down to 1.3.1. Not sure if this crazy upgrade
screwed up something, perhaps fog. As far as my install goes, I cloned
the foreman git repo to /usr/local/foreman then I do "cd /usr/local/foreman
&& git pull && git checkout tags/1.3.1 && bundle install".
Thanks for any help!
Looks like I'm getting this error for ALL compute providers, and not just
VMware.
···
On Thursday, March 27, 2014 3:42:30 PM UTC-4, Jason Ashby wrote:
>
> I'm not sure when this error started occurring, but I first noticed it
> today when attempting to a delete a host from the Foreman GUI. I'm running
> Foreman 1.3.1 on CentOS 6.4, apache 2.4.9, passenger 4.0.38, ruby 1.8.7.
>
> It sounds like this is something fog-related, but I've never had an issue
> before. I'm not sure how to tell what version of fog foreman is looking
> at, so let me know if I can give more info than this:
>
>
> me@foremanhost:/usr/local/foreman> gem list fog
>
> *** LOCAL GEMS ***
>
> fog (1.19.0, 1.18.0, 1.15.0, 1.9.0)
>
>
> Here's the steps to reproduce the issue:
>
> http://foremanhost:4000/compute_resources/new
> Provider: VMware
>
> On next page, I enter credentials for my vcenter server and click Load
> Datacenters and then I get the error: "vsphere is not a recognized compute
> provider"
>
> I also get this when attempting to delete a host that is tied to one of my
> existing compute resources.
>
>
> On a related note, I tried to upgrade to 1.4.2 recently, ran into some
> issues, then tried 1.3.2 which went smoothly, but thought this issue was a
> bug in 1.3.2 so I went back down to 1.3.1. Not sure if this crazy upgrade
> screwed up something, perhaps fog. As far as my install goes, I cloned
> the foreman git repo to /usr/local/foreman then I do "cd /usr/local/foreman
> && git pull && git checkout tags/1.3.1 && bundle install".
>
> Thanks for any help!
>
>
I restored my foreman install from a backup from a few days ago and good to
go now. Not sure what the heck happened. Moving forward, I'm going to put
foreman on a separate host and let the foreman-installer do all the work
for me :).
···
On Thursday, March 27, 2014 4:01:21 PM UTC-4, Jason Ashby wrote:
>
> Looks like I'm getting this error for ALL compute providers, and not just
> VMware.
>
> On Thursday, March 27, 2014 3:42:30 PM UTC-4, Jason Ashby wrote:
>>
>> I'm not sure when this error started occurring, but I first noticed it
>> today when attempting to a delete a host from the Foreman GUI. I'm running
>> Foreman 1.3.1 on CentOS 6.4, apache 2.4.9, passenger 4.0.38, ruby 1.8.7.
>>
>> It sounds like this is something fog-related, but I've never had an issue
>> before. I'm not sure how to tell what version of fog foreman is looking
>> at, so let me know if I can give more info than this:
>>
>>
>> me@foremanhost:/usr/local/foreman> gem list fog
>>
>> *** LOCAL GEMS ***
>>
>> fog (1.19.0, 1.18.0, 1.15.0, 1.9.0)
>>
>>
>> Here's the steps to reproduce the issue:
>>
>> http://foremanhost:4000/compute_resources/new
>> Provider: VMware
>>
>> On next page, I enter credentials for my vcenter server and click Load
>> Datacenters and then I get the error: "vsphere is not a recognized compute
>> provider"
>>
>> I also get this when attempting to delete a host that is tied to one of
>> my existing compute resources.
>>
>>
>> On a related note, I tried to upgrade to 1.4.2 recently, ran into some
>> issues, then tried 1.3.2 which went smoothly, but thought this issue was a
>> bug in 1.3.2 so I went back down to 1.3.1. Not sure if this crazy upgrade
>> screwed up something, perhaps fog. As far as my install goes, I cloned
>> the foreman git repo to /usr/local/foreman then I do "cd /usr/local/foreman
>> && git pull && git checkout tags/1.3.1 && bundle install".
>>
>> Thanks for any help!
>>
>>