Updated openstack/openstack
Project: openstack/tempest  3803836e873f36840c322b2c650f42e959fb1067
null
Verify list_hypervisors_detail Nova V2/V3 API

This patch adds the JSON Schema for response of Nova V2 & V3
list hypervisor detail API and validate the response with added
JSON Schema to block the backward incompatibility change in the future.

The response body of V2 list hypervisor detail API is below:

{
    "hypervisors": [
        {
            "cpu_info": "?",
            "current_workload": 0,
            "disk_available_least": null,
            "host_ip": "%(ip)s",
            "free_disk_gb": 1028,
            "free_ram_mb": 7680,
            "hypervisor_hostname": "fake-mini",
            "hypervisor_type": "fake",
            "hypervisor_version": 1,
            "id": 1,
            "local_gb": 1028,
            "local_gb_used": 0,
            "memory_mb": 8192,
            "memory_mb_used": 512,
            "running_vms": 0,
            "service": {
                "host": "%(host_name)s",
                "id": 2
            },
            "vcpus": 1,
            "vcpus_used": 0
        }
    ]
}

The response body of V3 list hypervisor detail API is below:

{
    "hypervisors": [
        {
            "cpu_info": "?",
            "current_workload": 0,
            "disk_available_least": 0,
            "host_ip": "%(ip)s",
            "free_disk_gb": 1028,
            "free_ram_mb": 7680,
            "hypervisor_hostname": "fake-mini",
            "hypervisor_type": "fake",
            "hypervisor_version": 1,
            "id": %(hypervisor_id)s,
            "local_gb": 1028,
            "local_gb_used": 0,
            "memory_mb": 8192,
            "memory_mb_used": 512,
            "running_vms": 0,
            "service": {
                "host": "%(host_name)s",
                "id": 2
            },
            "vcpus": 1,
            "vcpus_used": 0,
            "os-pci:pci_stats": []
        }
    ]
}

Partially implements blueprint nova-api-attribute-test

Change-Id: I0815ecf1dc985ba404f636a68dccbbf6be4188d5
Updated openstack/openstack
Project: openstack/cinder  a3a3b8358791fbe7db13361c8e532b6b97e8a73d
null
vmware: Use SessionIsActive to find stale session

An API invocation with a stale session returns an empty response. In order
to distinguish it from an API returning valid empty response, the session
is recreated and the API is retried. If an empty response is received even
after the retry, it can be assumed that the API response is actually empty.
But this behavior results in authentication error from the VMware server
when there is an active session and the API response is actually empty.
This change fix this behavior by using the SessionIsActive check to
identify stale session.

Change-Id: I6ddc4028bc5319cd22006de0590c13d6868c3494
Closes-Bug: #1284979