1. Install spacewalk 2. Install cobbler-web 3. restart spacewalk 4. see if taskomatic is up (It won't be) 5. see if you can access http://localhost/rpc/api via xmlrpc (You won't be able to). We need to investigate why cobbler-web's http config is breaking spacewalk.
Mass-moving to space13.
I think this is caused by the fact that both the cobbler_web.conf and zz-spacewalk-server.conf contain a <VirtualHost> section. The cobbler_web.conf specifies one for port 80 (<VirtualHost *:80>) while the zz-spacewalk-server.conf defines one for the default (it's just <VirtualHost>). As the VirtualHost for port 80 (as defined in the cobbler_web.conf) has preference over the default VirtualHost (as defined in zz-spacewalk-server.conf) the rewrite engine doesn't get enabled for port 80. This results in breakage of the spacewalk rewrite rules which are mentioned in zz-spacewalk-www.conf. A simple solution to this would be to adjust the cobbler_web.conf to something like this: <VirtualHost *:80> RewriteEngine on RewriteOptions inherit ... </VirtualHost> With this change spacewalk works fine again. A side effect of this is that apache complains on startup about the <VirtualHost> mentioned in zz-spacewalk-server.conf: [Tue Nov 23 13:49:23 2010] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.
Aligning under space16.
We do not support cobbler-web installation on Spacewalk. Maybe we should investigate adding a conflicts statement into rpm spec file until someone implements code to make this work side-by-side correctly. Cliff
Put a conflict into rpm for now commit fe6d334ff5bc86608b944fdc3300f115e78da54d 593402 - cobbler-web is known to break our configuration
Spacewalk 1.6 has been released.