Transient failure processing deployments during boot

Booting a domain managed server with a deployment assigned to the server group leads to transient problems in the server log:

[Server:server-one] 19:37:02,784 INFO [stdout] (Controller Boot Thread) Prepared response is {
[Server:server-one] 19:37:02,784 INFO [stdout] (Controller Boot Thread) "outcome" => undefined,
[Server:server-one] 19:37:02,784 INFO [stdout] (Controller Boot Thread) "failure-description" =>

{"Services with transitive problems" => ["jboss.deployment.unit.\"test.war\""]}

[Server:server-one] 19:37:02,784 INFO [stdout] (Controller Boot Thread) }
[Server:server-one] 19:37:02,792 INFO [org.jboss.as.controller] (Controller Boot Thread) Service status report
[Server:server-one] New missing/unsatisfied dependencies:
[Server:server-one] service jboss.deployment.chains (missing)
[Server:server-one]
[Server:server-one] 19:37:02,801 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "test.war"
[Server:server-one] 19:37:03,266 INFO [org.jboss.web] (MSC service thread 1-3) registering web context: /test
[Server:server-one] 19:37:03,266 INFO [org.jboss.as] (MSC service thread 1-3) JBoss AS 7.0.0.Beta4-SNAPSHOT "(TBD)" started in 4022ms - Started 121 of 194 services (73 services are passive or on-demand)
[Server:server-one] 19:37:03,267 INFO [org.jboss.as.controller] (MSC service thread 1-3) Service status report
[Server:server-one] Newly corrected services:
[Server:server-one] service jboss.deployment.chains (now available)
[Server:server-one]

I expect the same thing would happen with a standalone server with the deployment in standalone.xml.

The stdout stuff above is some debug logging.