/etc/cobbler/settings 'server:' entry not respected when given an IP address. Cobbler 2.4.0

[barrowsr]

I have the following entry in my /etc/cobbler/settings
server: 192.168.1.101

Cobbler resolves this correctly as "server1" through my dns.
Then every place that cobbler needs to put my server it uses
"server1" instead of "192.168.1.101" for all instances of @@http_server@@
this goes for stanzas as well as repo paths, kickstart paths and tree paths

Perhaps there is an underlying reason I am missing but I believe cobbler
should respect what the user enters in /etc/cobbler/settings

It also does this when you specify --server=192.168.1.101 in a profile
I would of tried --server-override but it no longer seems to work.
cobbler: error: no such option: --server-override

The reason this is causing me a problem:
On a CentOS 6.4 install there is a problem with NetworkManager and
DNS resolution. A system with two NICs with only one plugged in will try to bring up
both. The plugged in one will come up fine, with the second failing shortly after.
However the failure of the second causes DNS problems and the installation cannot
see "server1"

For now I have edited stanzas out of my kickstarts, and manually changed tree, repo, and kickstart path entries to remove @@http_server@@

While I have overcome this for now, perhaps there is a hack I could make in the py files, or perhaps there is a better way I am missing?

Thanks for the great tool.

[gmcfrear]

Hi Barrowsr,

Instead of --server-override use just --server="string" (ip or hostname works well)

[barrowsr]

I will for now, thanks for the tip.

[chjohnst]

Does this problem still exist?

[barrowsr]

Yes the problem does still exist. I have worked around it by the way I described above. I haven't tried the --server="string" yet, since the setup is working for now. I do still think that an IP entry in /etc/cobbler/settings should persist. Thanks.

[claudiomll]

adding http_server=192.168.1.101 on the setting file will workaround this issue.

[SchoolGuy]

Let's try to replicate for 3.3.0 and if it persists then fix it.