xCAT Apache configuration conflicts with other software that uses the same web server

[conxuro]

xCAT adds its Apache configuration in addition to the default conf. Since Apache treat config files in alphanumeric order, if an additional service is added, in most cases with configs files starting with a letter before than "x" (or with a number), they take precedence breaking xCAT repositories (unabling to update nodes or to provision Statefull nodes).

The same happens if a service is configured with a virtualhost in the same Apache server, which is set as default, breaking also the xCAT Apache config.

A possible solution could be to add xCAT config inside a Virtualhost with a name starting with a number.

For example:

cat /etc/httpd/conf.d/0-xcat.conf
#
# This configuration file allows a diskfull install to access the install images
# via http.  It also allows the xCAT documentation to be accessed via
# http://localhost/xcat-doc/
# Updates to xCAT/xcat.conf should also be made to xCATsn/xcat.conf
#

<virtualhost *:80>
    ServerName xcat

    ErrorLog "logs/xcat-error.log"
    CustomLog "logs/xcat-access.log" combined
[...]
</virtualhost>

[samveen]

It will probably be better to match the value of ServerName to the value of DNS record for the management server in the xCAT DNS. This will also require corresponding changes in the provisioning and netboot infrastructure, which relies on the IP of the DHCP server, rather than names (via the value of the XCAT master setting)