Ironic on MOS8.0 didn't support different ip ranges for baremetal and baremetal network parameter

Ironic team, please verify that all settings were correct on the bug committer env. Probably it's not a bug, but misconfiguration.

root@node-1:~# ip netns exec haproxy curl -v http://10.14.63.10:8080/v1/AUTH_d80930de52924222bdb4bb04da998032/glance/14de50d3-4de7-446c-a0b5-c0b6e646fadb?temp_url_sig=6dfe22781eee4f52425a3f1af858e75a71abb15d&temp_url_expires=1458383943
[1] 42025
root@node-1:~# * Hostname was NOT found in DNS cache
* Trying 10.14.63.10...
* Connected to 10.14.63.10 (10.14.63.10) port 8080 (#0)
> GET /v1/AUTH_d80930de52924222bdb4bb04da998032/glance/14de50d3-4de7-446c-a0b5-c0b6e646fadb?temp_url_sig=6dfe2
2781eee4f52425a3f1af858e75a71abb15d HTTP/1.1
> User-Agent: curl/7.35.0
> Host: 10.14.63.10:8080
> Accept: */*
>
< HTTP/1.1 401 Unauthorized
< Content-Length: 35
< Content-Type: text/html; charset=UTF-8
< Www-Authenticate: Swift realm="unknown"
< X-Trans-Id: txabef27aefcd34bc6b91ac-0056ed2112
< Date: Sat, 19 Mar 2016 09:51:14 GMT
< Connection: close
<
401 Unauthorized: Temp URL invalid
* Closing connection 0

That's where we got stuck.

The baremetal setting changed as below:
Baremetal 10.14.63.10~10.14.63.30 vlan:1103
Baremetal Network Parameters 10.14.63.32~10.14.63.240 gateway: 10.14.63.1

2016-03-20 05:05:09 WARNING keystonemiddleware.auth_token [-] Authorization failed for token
2016-03-20 05:05:09 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "Failed to validate token", "code": 404, "title": "Not Found"}}
2016-03-20 05:05:09 WARNING keystonemiddleware.auth_token [-] Authorization failed for token
2016-03-19 20:59:54 WARNING keystonemiddleware.auth_token [-] Authorization failed for token
2016-03-19 20:59:54 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "Failed to validate token", "code": 404, "title": "Not Found"}}
2016-03-19 20:59:54 WARNING keystonemiddleware.auth_token [-] Authorization failed for token
2016-03-19 17:57:58 WARNING keystonemiddleware.auth_token [-] Authorization failed for token
2016-03-19 17:57:58 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "Failed to validate token", "code": 404, "title": "Not Found"}}
2016-03-19 17:57:58 WARNING keystonemiddleware.auth_token [-] Authorization failed for token
2016-03-19 06:37:37 ERR wsme.api [req-95ca35fd-bc97-411d-b800-f88c0da649c8 ] Server-side error: "(_mysql_exceptions.OperationalError) (2003, "Can't connect to MySQL server on '10.14.68.3' (111)") [SQL: u'SELECT 1']". Detail:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/wsmeext/pecan.py", line 84, in callfunction
    result = f(self, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/ironic/api/controllers/v1/node.py", line 1065, in detail
    resource_url)
  File "/usr/lib/python2.7/dist-packages/ironic/api/controllers/v1/node.py", line 905, in _get_nodes_collection
    nodes = self._get_nodes_by_instance(instance_uuid)
  File "/usr/lib/python2.7/dist-packages/ironic/api/controllers/v1/node.py", line 938, in _get_nodes_by_instance
    instance_uuid)
  File "/usr/lib/python2.7/dist-packages/ironic/objects/node.py", line 183, in get_by_instance_uuid
    db_node = cls.dbapi.get_node_by_instance(instance_uuid)
  File "/usr/lib/python2.7/dist-packages/ironic/db/sqlalchemy/api.py", line 303, in get_node_by_instance
    result = query.one()
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2473, in one
    ret = list(self)
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2516, in __iter__
    return self._execute_and_instances(context)
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2529, in _execute_and_instances
    close_with_result=True)
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2520, in _connection_from_session
    **kw)
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 882, in connection
    execution_options=execution_options)
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 889, in _connection_for_bind
    conn = engine.contextual_connect(**kw)
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 2041, in contextual_connect
    **kwargs)
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 92, in __init__
    self.dispatch.engine_connect(self, self.__branch)
  File "/usr/lib/pyt...

Log from ironic conductor:
2016-03-19 07:16:36 ERR ironic.conductor.manager [-] During sync_power_state, max retries exceeded for node e8617c57-a9b0-42ec-a339-7afdf004916f, node state None does not match expected state 'power on'. Updating DB state to 'None' Switching node to maintenance mode.
2016-03-19 07:16:36 WARNING ironic.drivers.modules.ipmitool [-] IPMI power status failed for node e8617c57-a9b0-42ec-a339-7afdf004916f with error: Unexpected error while running command.
Command: ipmitool -I lanplus -H 10.14.252.119 -L ADMINISTRATOR -U root -R 12 -N 5 -f /tmp/tmpkvWdAb power status
Exit code: 1
Stdout: u''
Stderr: u'Error: Unable to establish IPMI v2 / RMCP+ session\n'.
2016-03-19 07:16:36 ERR ironic.drivers.modules.ipmitool [-] IPMI Error while attempting "ipmitool -I lanplus -H 10.14.252.119 -L ADMINISTRATOR -U root -R 12 -N 5 -f /tmp/tmpkvWdAb power status"for node e8617c57-a9b0-42ec-a339-7afdf004916f. Error: Unexpected error while running command.
Command: ipmitool -I lanplus -H 10.14.252.119 -L ADMINISTRATOR -U root -R 12 -N 5 -f /tmp/tmpkvWdAb power status
Exit code: 1
Stdout: u''
Stderr: u'Error: Unable to establish IPMI v2 / RMCP+ session\n'
2016-03-19 07:11:24 WARNING ironic.conductor.manager [-] During sync_power_state, could not get power state for node e8617c57-a9b0-42ec-a339-7afdf004916f, attempt 3 of 3. Error: IPMI call failed: power status..
2016-03-19 07:11:24 WARNING ironic.drivers.modules.ipmitool [-] IPMI power status failed for node e8617c57-a9b0-42ec-a339-7afdf004916f with error: Unexpected error while running command.
Command: ipmitool -I lanplus -H 10.14.252.119 -L ADMINISTRATOR -U root -R 12 -N 5 -f /tmp/tmpXiUKnI power status
Exit code: 1
Stdout: u''
Stderr: u'Error: Unable to establish IPMI v2 / RMCP+ session\n'.
2016-03-19 07:11:24 ERR ironic.drivers.modules.ipmitool [-] IPMI Error while attempting "ipmitool -I lanplus -H 10.14.252.119 -L ADMINISTRATOR -U root -R 12 -N 5 -f /tmp/tmpXiUKnI power status"for node e8617c57-a9b0-42ec-a339-7afdf004916f. Error: Unexpected error while running command.
Command: ipmitool -I lanplus -H 10.14.252.119 -L ADMINISTRATOR -U root -R 12 -N 5 -f /tmp/tmpXiUKnI power status
Exit code: 1
Stdout: u''
Stderr: u'Error: Unable to establish IPMI v2 / RMCP+ session\n'
2016-03-19 07:06:57 WARNING ironic.conductor.manager [-] During sync_power_state, could not get power state for node e8617c57-a9b0-42ec-a339-7afdf004916f, attempt 2 of 3. Error: IPMI call failed: power status..
2016-03-19 07:06:57 WARNING ironic.drivers.modules.ipmitool [-] IPMI power status failed for node e8617c57-a9b0-42ec-a339-7afdf004916f with error: Unexpected error while running command.
Command: ipmitool -I lanplus -H 10.14.252.119 -L ADMINISTRATOR -U root -R 12 -N 5 -f /tmp/tmp2USotP power status
Exit code: 1
Stdout: u''
Stderr: u'Error: Unable to establish IPMI v2 / RMCP+ session\n'.
2016-03-19 07:06:57 ERR ironic.drivers.modules.ipmitool [-] IPMI Error while attempting "ipmitool -I lanplus -H 10.14.252.119 -L ADMINISTRATOR -U root -R 12 -N 5 -f /tmp/tmp2USotP power status"for node e8617c57-a9b0-42ec-a339-7afdf004916f. Error: Unexpected error while running command.
Command: ipmitool -I lanplus -H 10.14.252.119 -L...

And also some failed items in OSTF testing after MOS 8.0 deployed:
Check usage of default credentials on master node
Target component: Configuration

Scenario:
1. Check user can not ssh on master node with default credentials.
20 s.
50.5

Check if default credentials for OpenStack cluster have changed
Default credentials values are used. We kindly recommend that you changed all defaults.
Target component: Configuration

Scenario:
1. Check if default credentials for OpenStack cluster have changed.
20 s.
0.0

Check usage of default credentials for keystone on master node
Default credentials for keystone on master node were not changed
Target component: Configuration

Scenario:
1. Check default credentials for keystone on master node are
changed.
20 s.
0.3

Won't Fix for 8.0-updates because of Medium importance

@Vitaly does Ironic for mos8.0 support vlan/trunk for baremetal network? or mos8.0 just support flat baremetal network?

@Johnson baremetal network may be tagged and included to trunk with other networks. Hardware servers should be plugged to baremetal netwrok VLAN in this case.

@Jonson should we close this ticket?

Added move-to-10.0 tag due to the fact bug was transferred from 9.0 to 10.0

@Vasyl, Thanks for your reply, I still can't work out ironic with fuel_ipmitool driver with a different vlan between baremetal service network(baremetal) and baremetal deployment network(Baremetal Network Parameter), maybe I can try this later. But I have the community drivers pxe_ipmitool worked on my fuel8.0 testing environment with some code&iptables revise.

@Serge, I still can't work it out with fuel_ipmitool driver, please feel free to close this ticket, I may try to test fuel_ipmitool driver later, and let you know if I have it worked on my environment.

@Johnson, any luck?

@Saerge， yes，we worked out the pxe_ipmitool driver with some modification， but not for fuel_ipmitool driver。