Updated openstack/openstack
Project: openstack/nova  a0963452c4ce498972deb9a5c5e089812721f61c
null
Recover from REBOOT-* state on compute manager start-up

If a compute manager is stopped / fails during certain REBOOT-*
operations then the instance will be left stuck in a transitional
task_state

This change handles two possible task states REBOOT_PENDING and
REBOOT_STARTED (for both soft and hard reboots). And either clears
these states or retries the reboot depending on the instance state.

Both task states are set after the request has gotten to the compute
manager so we can handle these safely knowing the operation has
ended/failed with the restart of the compute manager.

We retry the reboot where the state is PENDING and where the state is
STARTED and the instance is not running.

Where the instance is running and the state is STARTED we simply
transition the instance to an ACTIVE state. The user can retry the
reboot if required.

Related to blueprint recover-stuck-state

Change-Id: Ib318b3d444a67616441302f3daa8de20ee946f3f
Updated openstack/openstack
Project: openstack/tempest  ffb6d819612e2c63f743189a001401e3f1921b44
null
Verify more information in API tests for LBaaS

In API tests for LBaaS not all information is checked  that is
required.
For example, test_show_* checks only equality of name and id;
test_associate_disassociate_health_monitor_with_pool does not check
that pool containts healthmonitor after assosiating.

This tests should be corrected.

Also create_member and update_member was updated to use _create and
_update from network_client_base.

Closes-bug: #1262112

Change-Id: I352253ce9e28b46324a81e40c6b86759e0687420