[CentOS] firewalld cloud-init dhcp error

Sun Jul 17 06:52:50 UTC 2016
望月忠雄 <tadao at creative-japan.org>

Dear members,

Please tell me what's wrong.
After setig firewalld, I got fail on cloud-init with reboot.
The server is rebooted, but I cannot access from internet.
Before reboot I can access form internet.
And before setig firewalld, there's no problem on reboot.

/var/log/cloud-init.log shows following
Jul 17 14:18:46 biz105 cloud-init: ci-info:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info
failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Jul 17 14:21:01 biz105 cloud-init: 2016-07-17 14:21:01,476 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [3/120s]:
unexp
ected error ['NoneType' object has no attribute 'status_code']
Jul 17 14:21:04 biz105 cloud-init: 2016-07-17 14:21:04,482 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [6/120s]:
unexp
ected error ['NoneType' object has no attribute 'status_code']
Jul 17 14:21:07 biz105 cloud-init: 2016-07-17 14:21:07,488 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [9/120s]:
unexp
ected error ['NoneType' object has no attribute 'status_code']


# cat /etc/firewalld/direct.xml
<?xml version="1.0" encoding="utf-8"?>
<direct>
  <rule priority="0" table="nat" ipv="ipv4" chain="POSTROUTING_direct">-s
192.168.1.5 -o eth0 -j SNAT --to 153.153.xxx.xxx</rule>
  <rule priority="0" table="nat" ipv="ipv4" chain="PREROUTING_direct">-s
153.153.xxx.xxx -o eth0 -j DNAT --to 192.168.1.5</rule>
</direct>

# firewall-cmd --zone=external --list-all
external (active)
  interfaces: eth0
  sources:
  services: dns ftp http https imaps pop3s smtp ssh
  ports: 110/tcp 21/tcp 106/tcp 53/tcp 990/tcp 5432/tcp 8447/tcp 113/tcp
143/tcp 3306/tcp 5224/tcp 22/tcp 465/tcp 995/tcp 25/tcp 8443/tcp 993/tcp
443/tcp 8880/tcp 587/tcp 20/tcp 53/udp 12768/tcp
  masquerade: yes
  forward-ports:
  icmp-blocks:
  rich rules:

# nmcli c show System-eth0 | grep connection.autoconnect
connection.autoconnect:                 yes
connection.autoconnect-priority:        0