I've filed a bug for this in Redmine . Please add any additional info or things I may have missed. Hopefully I'll have time tomorrow to write a fix and submit a pull request.
Tim, sorry your original post didn't get responded to in a timely fashion.
- Bug #2352: Uppercase hostnames are not preserved in routes due to certname/hostname mismatches, causing 404's - Foreman
···----- Original Message ----- From: "Seth Matheson" To: firstname.lastname@example.org Sent: Monday, March 25, 2013 3:00:42 PM Subject: [foreman-users] Re: Forman 1.1 case sensitive to hostname?
I’m having the same issue, Ubuntu 12.0.4 host, PostgreSQL backend. We see it for linux hosts as well (whose hostnames are have uppercase letters).
On Monday, February 11, 2013 1:22:59 PM UTC-5, Tim Owens wrote:
I’m working with Foreman 1.1RC4 on CentOS 6.3 and a PostgreSQL 9.1.7 backend.
I’m noticing that our Windows agents will report with a hostname that is uppercase (which it is on the agent), which show up fine in the Foreman GUI and the PSQL DB.
The puppet certname in lowercase, of course.
When a user clicks on the hostname in the GUI, it throws a “Host not found” page. e.g. http://foreman:3000/hosts/1OFOURSERVERS.domain.tld
If you then add a ‘/facts’ in the above URL, it goes through successfully to the hosts’ facts page. This also works with ‘/audits’ and ‘/reports’.
I have also removed the uppercased host, renamed the Windows servers to a lowercase name and it all works okay. We just can’t do this manual process for each of our three hundred machines.
Can anyone help me with a workaround or help fix this bug?
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 email@example.com.
To post to this group, send email to firstname.lastname@example.org.
Visit this group at http://groups.google.com/group/foreman-users?hl=en .
For more options, visit https://groups.google.com/groups/opt_out .