(#6112) Acceptance test handles host with uninitialized ssl

Running the acceptance test on Jenkins discovered a third case, and
helped use clarify behavior for the expected cases on an initialized
master/agent.  The third case is a host which has not initialized yet
(has no ssl info created or cached) which is similar to what happens
when a master initializes through a 'puppet master' call, but this is
through a 'puppet generate' call and what the node should be capable of
as a master or agent afterwords is ambiguous.

Acceptance test now checks this case, showing that a cert does generate
in this instance, and leaves the host in an ambiguous state of ssl
configuration where they cannot authenticate with the master afterwords.
(#6112) Clearing test of whether puppet agent fails

Whether a puppet agent -t fails after a puppet cert generate in a bare
host (no ssl setup) seems to have platform specific issues which need to
be figured out.  It fails for me locally in Ubuntu, and the Lucid
Jenkins job failed, but RHEL did not.

Commenting this portion out and marking pending until we have more time
to investigate.
Merge pull request #1756 from jpartlow/issue/master/6112-fixing-acceptance-test

(#6112) Acceptance test handles host with uninitialized ssl