We basically need a 'killall -HUP dbus-daemon' or equivalent added to %post to get the message bus to allow certmonger to claim the service name it attempts to register when it's started.

I have the same issue when testing on a new VM installed from scratch:

Fedora release 14 (Laughlin)
Linux ca1.example.com 2.6.35.6-45.fc14.x86_64 #1 SMP Mon Oct 18 23:57:44 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
ipa-server-2.0.0.pre1-0.fc14.x86_64

could we add the workaround in comment 1 to either
the ipa-server-install script
or the ipav2beta1 release notes at
http://freeipa.org/page/IPAv2_beta
?

(
which is linked from http://freeipa.org/page/Main_Page
for
# RELEASED FreeIPA v2 Beta 1 (2.0.0.pre1), Release Notes 
under the news section
)

at second though, probably the release notes would make more sense since it seem to be a F14 issue more than IPA itself, I will update my ks %post section.

update: in my test case, the workwound in comment 1 did not work for me, I had to do the following in order to get certmonger to start and to be able to complete ipa-server-instal:
/etc/init.d/messagebus start
ipa-server-install --uninstall
ipa-server-install ...options...

We made a change in IPA post-beta to always start the messagebus service.

Package certmonger-0.35.1-1.fc14:
* should fix your issue,
* was pushed to the Fedora 14 updates-testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing certmonger-0.35.1-1.fc14'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/certmonger-0.35.1-1.fc14
then log in and leave karma (feedback).

Package certmonger-0.35.1-1.fc15:
* should fix your issue,
* was pushed to the Fedora 15 updates-testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing certmonger-0.35.1-1.fc15'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/certmonger-0.35.1-1.fc15
then log in and leave karma (feedback).

Package certmonger-0.35.1-1.fc13:
* should fix your issue,
* was pushed to the Fedora 13 updates-testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing certmonger-0.35.1-1.fc13'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/certmonger-0.35.1-1.fc13
then log in and leave karma (feedback).

Please pardon the comment spew.  I wasn't thinking quite right when filing the update for F14 and F15, which should already have included this.  The testing update for F13 adds a 'killall' to the %post as noted in comment #1 to get the message bus to reload its configuration, so that it'll permit certmonger to start and claim the service name on the bus.

certmonger-0.35.1-1.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update certmonger'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/certmonger-0.35.1-1.fc13

certmonger-0.35.1-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.