ardana-pre-upgrade-status.yml

#
# (c) Copyright 2016 Hewlett Packard Enterprise Development LP
# (c) Copyright 2017-2018 SUSE LLC
#
# Licensed under the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License. You may obtain
# a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations
# under the License.
#
# Top-level Ardana pre-upgrade status playbook
# A separate pre-upgrade status is required to account for parts of a
# service not yet deployed as part of the upgrade, e.g. the introduction of
# of the object-reconstructor service in Ardana OpenStack.
# Another possible solution is to implement a check that handles the fact
# that a service has not been deployed yet (e.g. not registered with
# systemd). For the majority of cases, the pre-upgrade status check is
# identical to the regular status check.
# BUG 2913 used to track an alternative solution.
---

- include: osconfig-status.yml
- include: ardana-status.yml
  vars:
    ardana_pre_upgrade_check: true
    # We may be transitioning TLS in RabbitMQ so we cannot check the TLS
    # state. For example we are rerunning upgrade play after a failure.
    rabbitmq_tls_check_status: false