1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
|
============
trove-status
============
Synopsis
========
::
trove-status <category> <command> [<args>]
Description
===========
:program:`trove-status` is a tool that provides routines for checking the
status of a Trove deployment.
Options
=======
The standard pattern for executing a :program:`trove-status` command is::
trove-status <category> <command> [<args>]
Run without arguments to see a list of available command categories::
trove-status
Categories are:
* ``upgrade``
Detailed descriptions are below.
You can also run with a category argument such as ``upgrade`` to see a list of
all commands in that category::
trove-status upgrade
These sections describe the available categories and arguments for
:program:`trove-status`.
Upgrade
~~~~~~~
.. _trove-status-checks:
``trove-status upgrade check``
Performs a release-specific readiness check before restarting services with
new code. This command expects to have complete configuration and access
to databases and services.
**Return Codes**
.. list-table::
:widths: 20 80
:header-rows: 1
* - Return code
- Description
* - 0
- All upgrade readiness checks passed successfully and there is nothing
to do.
* - 1
- At least one check encountered an issue and requires further
investigation. This is considered a warning but the upgrade may be OK.
* - 2
- There was an upgrade status check failure that needs to be
investigated. This should be considered something that stops an
upgrade.
* - 255
- An unexpected error occurred.
**History of Checks**
**11.0.0 (Stein)**
* Checks if any Trove instance with assigned task is running.
The assigned tasks may fail during the upgrade process due to transient
unavailability of Trove control plane.
Upgrade should be postponed until all instances are in the Active state.
|
