OpenStack Newton Installation(using packstack) Error

I've recently installed the OpenStack Newton on a freshly installed CentOS-7. I followed the Packstack quickstart guide for the single node setup. I'm stuck in this from this monday.

I have tow problems.

1. The installation stops with the error:

Error appeared during Puppet run: 192.168.x.xx_controller.pp

When I open the setup.log file I have this:

Error appeared during Puppet run: 192.168.x.xx_controller.pp Error: /Stage[main]/Nova::Db::Sync/Exec[nova-db-sync]: Failed to call refresh: /usr/bin/nova-manage db sync returned 1 instead of one of [0][0m You will find full trace in log /var/tmp/packstack/20161215-154418-GFnhLr/manifests/192.168.x.xx_controller.pp.log

2016-12-15 15:56:29::INFO::shell::94::root:: [192.168.x.xx] Executing script: rm -rf /var/tmp/packstack/fbb74d7f4c7f4e8c988aba9c28ffd3d9

I know I'm missing something but I don't know what!

I'm able to start the nova-api and nova-conductor services. But when I try to start scheduler service (though I've enabled the scheduler service but can't start it. If I install puppet externally, though I skip the scheduler error, I still get error nagios services can't be started), it says:

# systemctl start openstack-nova-scheduler.service
Job for openstack-nova-scheduler.service failed because the control process exited with error code. See "systemctl status openstack-nova-scheduler.service" and "journalctl -xe" for details.

So as it suggests I tried with both the commands and the output from them is like this:

# journalctl -xe
-- Unit openstack-nova-scheduler.service has failed.
-- 
-- The result is failed.
Dec 15 17:35:23 localhost.localdomain systemd[1]: Unit openstack-nova-scheduler.service entered failed state.
Dec 15 17:35:23 localhost.localdomain systemd[1]: openstack-nova-scheduler.service failed.
Dec 15 17:35:23 localhost.localdomain systemd[1]: openstack-nova-scheduler.service holdoff time over, scheduling restart.
Dec 15 17:35:23 localhost.localdomain systemd[1]: Starting OpenStack Nova Scheduler Server...
-- Subject: Unit openstack-nova-scheduler.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit openstack-nova-scheduler.service has begun starting up.
Dec 15 17:35:24 localhost.localdomain kernel: ata1: SATA link down (SStatus 1 SControl 310)
Dec 15 17:35:24 localhost.localdomain kernel: ata1: EH complete
Dec 15 17:35:24 localhost.localdomain kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen
Dec 15 17:35:24 localhost.localdomain kernel: ata1: irq_stat 0x00000040, connection status changed
Dec 15 17:35:24 localhost.localdomain kernel: ata1: SError: { DevExch }
Dec 15 17:35:24 localhost.localdomain kernel: ata1: limiting SATA link speed to 1.5 Gbps
Dec 15 17:35:24 localhost.localdomain kernel: ata1: hard resetting link
Dec 15 17:35:26 localhost.localdomain nova-scheduler[10172]: Option "rpc_backend" from group "DEFAULT" is deprecated


# systemctl status openstack-nova-scheduler.service
● openstack-nova-scheduler.service - OpenStack Nova Scheduler Server
   Loaded: loaded (/usr/lib/systemd/system/openstack-nova-scheduler.service; enabled; vendor preset: disabled)
   Active: activating (start) since Thu 2016-12-15 17:36:04 +0530; 1s ago
 Main PID: 10308 (nova-scheduler)
   CGroup: /system.slice/openstack-nova-scheduler.service
           └─10308 /usr/bin/python2 /usr/bin/nova-scheduler

Dec 15 17:36:04 localhost.localdomain systemd[1]: Starting OpenStack Nova Scheduler Server...

BTW I'm able to log into dashboard. I can create images and the second problem arises at this point.

2. I get this error while launching instances:

I have checked the System Info tab in Admin panel, which gives me this error:

and this is from the Hypervisor page:

Even if, somehow I skip these errors, while launching an instance there is a message just below the Image browser tab saying There are no Availability zones. And when I click on the Launch Instance button, the instance runs into the error status and a pop up says - Error: No valid host was found. There are not enough hosts available

Can anyone point me where am I going wrong? I dint face such errors while installing the OpenStack-Mitaka. Is there any bug with the new version.

Also please let me know how to revert back to (or install) the Mitaka version, as the RDO allows to install the latest (Newton) version only.

Regards :)

NOTE: I'm running all the commands as root.