Description of problem:
firewall-cmd allows adding non-existing --permanent services.  This in itself is not such a big issue, but this distrubs the firewall-cmd --reload or startup process.

Version-Release number of selected component (if applicable):
firewalld-0.2.12-2.fc18.noarch

How reproducible:
Always.

Steps to Reproduce:
(note that the 'smtps' service does not exist)
1. firewall-cmd --permanent --zone=public --add-service=smtps
2. firewall-cmd --permanent --zone=public --list-services
mdns ident http dhcpv6-client smtp smtps imaps ssh dns imap
3. firewall-cmd --reload
4. firewall-cmd --zone=public --list-services
mdns ident http dhcpv6-client smtp
  
Actual results:
The services get enabled up to the non-existent "smtps" service.  Because of that, the firewall seems to stop and doesn't enable the "imaps", "ssh" (eek!), "dns" and "imap" services.

Expected results:
An error during
1. firewall-cmd --permanent --zone=public --add-service=smtps
about adding a non-existent service.

Perhaps it would also be a good idea if firewalld continued loading the rest of the services if a service file doesn't exist.  I imagine the same situation could appear if, for example, one of the enabled services were removed from the system.

Additional info:
-