fuel hanged on provisioning phase with fuel plugins

Hi,

recently I just want to deploy mirantis openstack with some fuel plugins in fuel 7.0 as I did in fuel 6.1. But surprisingly, fuel even can't finish the provisioning, all nodes were with status like "INSTALLING UBUNTU: 100%", but just hanged there without proceeding to next deploying phase.

I checked the log in fuel master from web backend like below:
--------------------------------------------------------------------------------------------------------------------------------------------------------------
2015-11-27 12:11:15 INFO [7fc13ae5f740] (node) Interfaces are locked for update on node CCCM-1
[pid: 708|app: 0|req: 924/5011] 10.20.0.4 () {36 vars in 522 bytes} [Fri Nov 27 12:11:15 2015] PUT /api/nodes/agent/ => generated 9 bytes in 133 msecs (HTTP/1.1 200) 4 headers in 185 bytes (2 switches on core 0)
[pid: 710|app: 0|req: 482/5012] 150.236.223.74 () {44 vars in 854 bytes} [Fri Nov 27 12:11:19 2015] GET /api/tasks/15?_=1448620462295 => generated 158 bytes in 11 msecs (HTTP/1.1 200) 4 headers in 185 bytes (2 switches on core 0)
[pid: 703|app: 0|req: 383/5013] 150.236.223.74 () {44 vars in 874 bytes} [Fri Nov 27 12:11:19 2015] GET /api/nodes?cluster_id=1&_=1448620462296 => generated 23544 bytes in 337 msecs (HTTP/1.1 200) 4 headers in 185 bytes (2 switches on core 0)
[pid: 704|app: 0|req: 1621/5014] 150.236.223.74 () {44 vars in 854 bytes} [Fri Nov 27 12:11:25 2015] GET /api/tasks/15?_=1448620462297 => generated 158 bytes in 11 msecs (HTTP/1.1 200) 4 headers in 185 bytes (2 switches on core 0)
[pid: 704|app: 0|req: 1622/5015] 150.236.223.74 () {44 vars in 874 bytes} [Fri Nov 27 12:11:25 2015] GET /api/nodes?cluster_id=1&_=1448620462298 => generated 23544 bytes in 336 msecs (HTTP/1.1 200) 4 headers in 185 bytes (2 switches on core 0)
2015-11-27 12:11:15 INFO [7fc13ae5f740] (node) Volume information is locked for update on node CCCM-1
2015-11-27 12:11:15 DEBUG [7fc13ae5f740] (node) Node CCCM-1 has provisioning or error status - status not updated by agent
--------------------------------------------------------------------------------------------------------------------------------------------------------------

it seems that agent is not working, but this is log from fuel-agent in CCCM-1 node:
--------------------------------------------------------------------------------------------------------------------------------------------------------------
2015-11-27 11:25:16 INFO fuel_agent.manager [-] --- Provisioning END (do_provisioning) ---
2015-11-27 11:25:16 INFO fuel_agent.utils.utils [-] Trying to execute command: umount /tmp/target/
2015-11-27 11:25:16 INFO fuel_agent.utils.fs [-] Trying to umount /tmp/target/
2015-11-27 11:25:16 INFO fuel_agent.utils.utils [-] Trying to execute command: mountpoint -q /tmp/target/
2015-11-27 11:25:16 INFO fuel_agent.utils.utils [-] Trying to execute command: umount /tmp/target/boot
2015-11-27 11:25:16 INFO fuel_agent.utils.fs [-] Trying to umount /tmp/target/boot
2015-11-27 11:25:16 INFO fuel_agent.utils.utils [-] Trying to execute command: mountpoint -q /tmp/target/boot
2015-11-27 11:25:16 INFO fuel_agent.utils.utils [-] Trying to execute command: umount /tmp/target/var/log
2015-11-27 11:25:16 INFO fuel_agent.utils.fs [-] Trying to umount /tmp/target/var/log
--------------------------------------------------------------------------------------------------------------------------------------------------------------
it looks like provisioning has already ended, but why fuel master can't received the status? but once I removed the plugins, the provisioning just work properly, does plugins cause this problem? anyone met the same problem as me?

by the way, i have not found the error in the execution, who can tell me what happened?

I almost installed all OPERATIONS MANAGEMENT PLUGINS i the link below:
https://www.mirantis.com/products/openstack-drivers-and-plugins/fuel-plugins/

I suspected maybe just someone of them introduced this problem, but even I tried to install one plugin in one time, this problem always happened as long as I installed it.

if you want to have any info or logs to trace, feel free to ask.

thanks in advance.