Description of problem:

The way of rally to validate the user-env.json file when creating an environment  
seems to be handled differently between release version 0.7.0.  



Version-Release number of selected component (if applicable):

openstack-rally-0.7.0-6el7ost 


How reproducible:

Always


Steps to Reproduce:

Using an upstream used existing-user.json 

1. rally deployment create --file ./CCI06-LinuxEng-env.json  --name CCI06-ENV 

Returns a validation ERROR 

Failed validating 'additionalProperties' in schema:
    {'additionalProperties': False,
     'definitions': {'user': {'oneOf': [{'additionalProperties': False,
                                         'properties': {'password': {'type': 'string'},
                                                        'tenant_name': {'type': 'string'},
                                                        'username': {'type': 'string'}},
                                         'required': ['username',
                                                      'password',
                                                      'tenant_name']},
                                        {'additionalProperties': False,
                                         'properties': {'domain_name': {'type': 'string'},
                                                        'password': {'type': 'string'},
                                                        'project_domain_name': {'type': 'string'},
                                                        'project_name': {'type': 'string'},
                                                        'user_domain_name': {'type': 'string'},
                                                        'username': {'type': 'string'}},
                                         'required': ['username',
                                                      'password',
                                                      'project_name']}],
                              'type': 'object'}},
     'properties': {'admin': {'$ref': '#/definitions/user'},
                    'auth_url': {'type': 'string'},
                    'endpoint': {'type': ['string', 'null']},
                    'endpoint_type': {'enum': ['admin',
                                               'internal',
                                               'public',
                                               None]},
                    'extra': {'additionalProperties': True,
                              'type': 'object'},
                    'https_cacert': {'type': 'string'},
                    'https_insecure': {'type': 'boolean'},
                    'region_name': {'type': 'string'},
                    'type': {'type': 'string'},
                    'users': {'items': {'$ref': '#/definitions/user'},
                              'type': 'array'}},
     'required': ['type', 'auth_url', 'admin'],
     'type': 'object'}

On instance:
    {'creds': {'openstack': {'admin': {'password': 'XXXXXXXXXXXXXXXXX',
                                       'project_domain_name': 'LinuxEng',
                                       'project_name': 'LinuxEng',
                                       'user_domain_name': 'default',
                                       'username': 'admin'},
                             'auth_url': 'https://cci06-ostctrl-oc.cloud.internal:35357/v3',
                             'endpoint_type': 'public',
                             'https_cacert': '/etc/pki/CA/certs/CCI06_Root_CA.pem',
                             'https_insecure': False,
                             'region_name': 'CCI06'}},
     'type': 'ExistingCloud'}.


Actual results:

Deployment creation fails for existing user.json on this version. 

The same json file has been used previously upstream. The deployment creation there succeeded. However, looking at the validation message it seems that there are no unknown properties set. 

Expected results:

Deployment succeeds and rally tests can be executed 

Additional info: