| ID | Description |
|---|---|
| 38496 | Creating a new server to replace another server in the cluster (using the --extend-cluster=false flag - note that this is also the default) - while dynamic rebalance is enabled - could cause the new server to participate in the dynamic rebalance process. The nodes on the server could then move automatically to active and not remain unattached. This prevents the server from acting as a replacement in the replace node process. |
| 28115 | The Lightbits upgrade cluster/server operation could fail to correctly handle some errors when the yum upgrade operation fails (i.e., when some dependencies are missing). For the upgrade server operation, this could result in the upgrade operation appearing to succeed, while the server continues using the previous Lightbits version. For the upgrade cluster operation, this could result in the upgrade operation being repeated in a loop, attempting to upgrade a server by rebooting it, continuing to the next server attempting to upgrade it, rebooting it, and continuing to the next one in a loop - as the Lightbits version was not upgraded. |
| 25573 | List events with the "--until" flag does not work. Specifying the until flag for list events could lead the specific API service to become unavailable for a short time after issuing the command. |
| 25248 | An upgrade server command could fail if another yum command is run at the same server on which the API is served (which is not necessarily the server that is intended to be upgraded). |
Was this page helpful?