Foreman 1.2 and autodiscovery

Hello,

I seem to be having a devil of a time getting the auto discovery plugin to play nicely with my fresh install.

CentOS6.4 - updated to latest version
EPEL installed

Follow instructions on the wiki and use the foreman installer to get foreman up and running as a fresh install. As this is a virtual machine add libvirt packages, then follow instructions on auto discovery plugin git page and when I restart apache passenger will not run due to an error with apipie. I tried this a couple of times for no particular result and I was wondering if anyone else has tripped across this?

If the way this is being installed seems awry please let me know. FWIW if I do not attempt to use the auto discovery plugin then foreman performs perfectly well after running the installer and setting up the environment.

kind regards,

> Hello,
>
> I seem to be having a devil of a time getting the auto discovery plugin to
> play nicely with my fresh install.
>
> CentOS6.4 - updated to latest version
> EPEL installed
>
> Follow instructions on the wiki and use the foreman installer to get
> foreman up and running as a fresh install. As this is a virtual machine add
> libvirt packages, then follow instructions on auto discovery plugin git
> page and when I restart apache passenger will not run due to an error with
> apipie. I tried this a couple of times for no particular result and I was
> wondering if anyone else has tripped across this?
>
> If the way this is being installed seems awry please let me know. FWIW if
> I do not attempt to use the auto discovery plugin then foreman performs
> perfectly well after running the installer and setting up the environment.
>
>
How did you install the plugin? using the packages? if you have the exact
error that would help too :wink:

Ohad

··· On Sat, Aug 24, 2013 at 1:46 AM, Luke Kearney wrote:

kind regards,


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.

Right, we have just released RPMs for RHEL6 and clones week ago. Debian
packages are on the way. Check out

http://projects.theforeman.org/projects/1/wiki/How_to_Install_a_Plugin

LZ

··· On Sun, Aug 25, 2013 at 01:48:50PM +0300, Ohad Levy wrote: > How did you install the plugin? using the packages? if you have the exact > error that would help too ;)


Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

I am sorry I no longer have the error message though may be able to reproduce it. From memory it was apipie related. To install I used the foreman-installer to get foreman in place then followed the instructions in the read me [ https://github.com/theforeman/foreman_discovery#readme ] - I did manage to get it installed using the rpms I located it the yum repo.

Thanks

··· On Aug 25, 2013, at 7:48 PM, Ohad Levy wrote:

On Sat, Aug 24, 2013 at 1:46 AM, Luke Kearney luke@kearney.jp wrote:
Hello,

I seem to be having a devil of a time getting the auto discovery plugin to play nicely with my fresh install.

CentOS6.4 - updated to latest version
EPEL installed

Follow instructions on the wiki and use the foreman installer to get foreman up and running as a fresh install. As this is a virtual machine add libvirt packages, then follow instructions on auto discovery plugin git page and when I restart apache passenger will not run due to an error with apipie. I tried this a couple of times for no particular result and I was wondering if anyone else has tripped across this?

If the way this is being installed seems awry please let me know. FWIW if I do not attempt to use the auto discovery plugin then foreman performs perfectly well after running the installer and setting up the environment.

How did you install the plugin? using the packages? if you have the exact error that would help too :wink:

The RPMs are quite new so the README hasn't been updated yet - good to hear
they work well though ;). I'll try to get the README updated soon. What
error are you having with building the image?

Greg

··· On 27 August 2013 08:09, Luke Kearney wrote:

I am sorry I no longer have the error message though may be able to
reproduce it. From memory it was apipie related. To install I used the
foreman-installer to get foreman in place then followed the instructions in
the read me [ https://github.com/theforeman/foreman_discovery#readme ] -
I did manage to get it installed using the rpms I located it the yum repo.

Hello,

Thanks for the note - I did ' discover ' the rpms in the yum repo on sunday and installed them. They worked perfectly though I did have / still have an issue with the boot image build - it seems to have some permissions issues but I have not spent enough time digging into it yet to be able to report any useful information.

Kind Regards,

LukeK

··· On Aug 27, 2013, at 4:03 PM, Lukas Zapletal wrote:

On Sun, Aug 25, 2013 at 01:48:50PM +0300, Ohad Levy wrote:

How did you install the plugin? using the packages? if you have the exact
error that would help too :wink:

Right, we have just released RPMs for RHEL6 and clones week ago. Debian
packages are on the way. Check out

How to Install a Plugin - Foreman

LZ


Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman


You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.