All output looks ok:

[root@deploy ~]# facter domain
netbulae.dc01
[root@deploy ~]# facter fqdn
deploy.netbulae.dc01
[root@deploy ~]# hostname -f
deploy.netbulae.dc01
[root@deploy ~]# facter hostname
deploy

Can you try the DB reset? It might be the configuration when the DB was seeded was incorrect, but is now fixed.

I started from a fresh Centos 6.5 install (I had made a copy of the VM image before installing foreman) so there is nothing that changed.

I ran the DB reset for good measure but it fails also:

[ERROR 2014-03-17 16:06:03 main] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[deploy.netbulae.dc01]: Could not evaluate: 500 Internal Server Error
[ INFO 2014-03-17 16:06:03 main] RESOURCE Foreman_smartproxy[deploy.netbulae.dc01]

Hm, maybe the reset didn't work as I expected. Try running these commands manually:

foreman-rake db:migrate
foreman-rake db:seed

If they give the same error about the e-mail address, we can dig into the DB I guess. If they appear to succeed, run the installer once more to complete the configuration.

foreman-rake db:seed
rake aborted!
Unable to create admin user: Email address is invalid

Tasks: TOP => db:seed
(See full trace by running task with --trace)

Any way to see what address the installer tries to use?

Try sudo -u foreman psql and then run:

foreman=> select * from settings where name='administrator';
 id |     name      | value |               description               |     category     | settings_type |       defaul
t        |         created_at         |         updated_at         
----+---------------+-------+-----------------------------------------+------------------+---------------+-------------
---------+----------------------------+----------------------------
  1 | administrator |       | The default administrator email address | Setting::General | string        | --- root@exa
mple.com | 2014-03-17 13:33:28.533068 | 2014-03-17 13:33:28.533068
                                                                                                         : ...         

                                                                                                         :             

(1 row)

See inside the 'default' column there's an e-mail address set, which is initialised first when the database is empty from the domain as reported by Facter.

id | name | value | description | category | settings_type | default | created_at | updated_at
----+---------------+-------+-----------------------------------------+------------------+---------------+------------------------+----------------------------+----------------------------
14 | administrator | | The default administrator email address | Setting::General | string | --- root@netbulae.dc01 | 2014-03-17 15:05:56.464209 | 2014-03-17 15:05:56.464209

Ah, now I see....

The workaround doesn't work however. The setting.yml appears to be replaced from template so I put it in /usr/share/foreman-installer/modules/foreman/templates/settings.yaml.erb and it gets set in settings.yml.

But the address still gets generated with the number TLD.

For now, I'll just change to using a TLD without numbers.