-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
False
-
Undefined
-
-
-
-
-
- Proposed title of this feature request- Require a preflight health checker before upgrade
- What is the nature and description of the request? We have reviwed quite a number of cases where upgrade is having issues like below :
- NodeClockNotSynchronising could lead issues later for upgrade.
- Operators are in degraded state after upgrade but the root cause of the operators are because of low resources hence it should be checked before
- Upgrade stuck because default scc was modified.
- Conflicting issues in machineconfig causes upgrade failures. hence machine configs should be checked before upgrade and a proper message to resolve it should be notified.
- etcd latency issues often lead to api failures and causes different operators in degraded state after upgrade hence user should be notified before upgrade aboyut health of etcd and api because operators are degraded sometimes and sometimes not.
- csr check
- Certificate check
- Check for : Service Catalog, Template Service Broker, Ansible Service Broker, and their associated Operators to be notified to customers that they are not upgradeable
- Check for the image pull before upgrade in case of disconnected : https://docs.openshift.com/container-platform/4.4/updating/updating-restricted-network-cluster.html#updating-restricted-network-image-signature-configmap
- relates to
-
RFE-5104 Automate pre-update critical alert check
- Under Review
-
OCPSTRAT-1834 OCP Update Precheck command to improve update experience
- In Progress
- links to