Potential bugs

Hi,
I'm trying to get startet with foreman but I've run into a few issues and
I'm not sure if these are bugs or if I just don't quite get how things are
supposed to work:

When I create a new operating system I cannot select all partition tables
for example the already existing "Redhat default" does not appear in the
list and neither do newly create tables. Once I save the operating system
and then edit it again the missing tables show up though.
The same happens with installation media however here even when I edit the
operating system i cannot select all available configured media.
When I select the templates tab foreman tells me that it cannot find any
even though there are already lots of template configured out of the box.

When I try to provision a server I cannot select anything for "Puppet CA"
even though I activated the support in the proxy config and registered the
proxy with foreman.

I managed to get libvirt support going by installing the necessary keys and
files in /usr/share/foreman/.ssh. When I try to provision a new VM I can
only select the single physical interface "p2p1" on the host though and not
the virtual NAT network named "bridge" that the other VMs use. I'm not sure
how this interface can be used directly if it's not part of a bridge?

Regards,
Dennis

> Hi,
> I'm trying to get startet with foreman but I've run into a few issues and
> I'm not sure if these are bugs or if I just don't quite get how things are
> supposed to work:
>
> When I create a new operating system I cannot select all partition tables
> for example the already existing "Redhat default" does not appear in the
> list and neither do newly create tables. Once I save the operating system
> and then edit it again the missing tables show up though.
> The same happens with installation media however here even when I edit the
> operating system i cannot select all available configured media.
>
The media list and ptables are based on the OS family (e.g. you need to
mark the OS family and afair the list should be updated).
if it doesnt happen on the same time (e.g. only after you submit once, then
edit again - then its a missing ajax that should be opened as a bug.

> When I select the templates tab foreman tells me that it cannot find any
> even though there are already lots of template configured out of the box.
>

When editing a template, see the association tab, there
is explanation and instructions of how templates are associated

> When I try to provision a server I cannot select anything for "Puppet CA"
> even though I activated the support in the proxy config and registered the
> proxy with foreman.
>

PuppetCA makes sense only if you have more than one proxy, when you have
two proxies with PuppetCA feature, you will see the dropdown.

>
> I managed to get libvirt support going by installing the necessary keys
> and files in /usr/share/foreman/.ssh. When I try to provision a new VM I
> can only select the single physical interface "p2p1" on the host though and
> not the virtual NAT network named "bridge" that the other VMs use. I'm not
> sure how this interface can be used directly if it's not part of a bridge?
>

Which hypervisor is that, if its Debian based OS, they have no way of
listing the bridges (until netcf would be added).
if its not, double check your bridge / interface has already started.

Ohad

··· On Thu, Aug 9, 2012 at 4:49 AM, Dennis Jacobfeuerborn < djacobfeuerborn@gmail.com> wrote:

>
>
>
>
>> Hi,
>> I'm trying to get startet with foreman but I've run into a few issues and
>> I'm not sure if these are bugs or if I just don't quite get how things are
>> supposed to work:
>>
>> When I create a new operating system I cannot select all partition tables
>> for example the already existing "Redhat default" does not appear in the
>> list and neither do newly create tables. Once I save the operating system
>> and then edit it again the missing tables show up though.
>> The same happens with installation media however here even when I edit
>> the operating system i cannot select all available configured media.
>>
> The media list and ptables are based on the OS family (e.g. you need to
> mark the OS family and afair the list should be updated).
> if it doesnt happen on the same time (e.g. only after you submit once,
> then edit again - then its a missing ajax that should be opened as a bug.
>

Yeah, that seems to be a bug then. I'll file a bug for that later.

>
> When I select the templates tab foreman tells me that it cannot find any
>> even though there are already lots of template configured out of the box.
>>
>
> When editing a template, see the association tab, there
> is explanation and instructions of how templates are associated
>

Indeed once I associate the template this works as expected, thanks.

>
>> When I try to provision a server I cannot select anything for "Puppet CA"
>> even though I activated the support in the proxy config and registered the
>> proxy with foreman.
>>
>
> PuppetCA makes sense only if you have more than one proxy, when you have
> two proxies with PuppetCA feature, you will see the dropdown.
>

This started working once I edited the proxy and saved it again. It would
probably a good idea to add a comment to the proxy setting that says that
the proxy needs to be re-registered with foreman if any of the services are
(de)activated.

>
>> I managed to get libvirt support going by installing the necessary keys
>> and files in /usr/share/foreman/.ssh. When I try to provision a new VM I
>> can only select the single physical interface "p2p1" on the host though and
>> not the virtual NAT network named "bridge" that the other VMs use. I'm not
>> sure how this interface can be used directly if it's not part of a bridge?
>>
>
> Which hypervisor is that, if its Debian based OS, they have no way of
> listing the bridges (until netcf would be added).
> if its not, double check your bridge / interface has already started.
>

This is a Fedora 15 host with an updated libvirt/qemu stack. I also
installed netcf but that doesn't list the bridge used for the NAT network:

[dennis@nexus ~]$ ncftool list
lo
p2p1
[dennis@nexus ~]$ ifconfig virbr1
virbr1 Link encap:Ethernet HWaddr 52:54:00:BF:82:96
inet addr:10.99.0.1 Bcast:10.99.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1116414 errors:0 dropped:0 overruns:0 frame:0
TX packets:1549074 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:413937227 (394.7 MiB) TX bytes:3205282356 (2.9 GiB)
[dennis@nexus ~]$ sudo virsh net-dumpxml bridge
<network>
<name>bridge</name>
<uuid>dfb49698-440d-0e03-a799-c11f1d7d90f1</uuid>
<forward mode='nat'/>
<bridge name='virbr1' stp='on' delay='0' />
<mac address='52:54:00:BF:82:96'/>
<ip address='10.99.0.1' netmask='255.255.0.0'>
</ip>
</network>

Regards,
Dennis

··· On Thursday, August 9, 2012 8:42:42 AM UTC+2, ohadlevy wrote: > On Thu, Aug 9, 2012 at 4:49 AM, Dennis Jacobfeuerborn < > djacobf...@gmail.com > wrote: