I cannot check yet if this issue is fixed or not on bare-metal servers because that servers are affected by: https://bugs.launchpad.net/starlingx/+bug/1973888
But I checked it on the Virtual configurations and I observed that stx-openstack apply is still failing.
I checked the pods and all of them are fine.
I cannot check yet if this issue is fixed or not on bare-metal servers because that servers are affected by: /bugs.launchpad .net/starlingx/ +bug/1973888
https:/
But I checked it on the Virtual configurations and I observed that stx-openstack apply is still failing.
I checked the pods and all of them are fine.
[sysadmin@ controller- 1 log(keystone_ admin)] $ system application-list ------- ------- ------+ ------- ------- ------- ------- ---+--- ------- ------- ------- ------- +------ ------- ------- +------ ------- -+----- ------- ------- ------- ------- ------- ------- ------- + ------- ------- ------+ ------- ------- ------- ------- ---+--- ------- ------- ------- ------- +------ ------- ------- +------ ------- -+----- ------- ------- ------- ------- ------- ------- ------- + controller | 1.1-26 | fluxcd-manifests | fluxcd-manifests | applied | completed | integration- manifest | manifest.yaml | applied | completed | centos- stable- | openstack-manifest | stx-openstack.yaml | apply-failed | Unexpected process termination while application- | ------- ------- ------+ ------- ------- ------- ------- ---+--- ------- ------- ------- ------- +------ ------- ------- +------ ------- -+----- ------- ------- ------- ------- ------- ------- ------- +
+------
| application | version | manifest name | manifest file | status | progress |
+------
| cert-manager | 1.0-33 | fluxcd-manifests | fluxcd-manifests | applied | completed |
| nginx-ingress-
| oidc-auth-apps | 1.0-64 | oidc-auth-manifest | manifest.yaml | uploaded | completed |
| platform-integ-apps | 1.0-46 | platform-
| rook-ceph-apps | 1.0-16 | rook-ceph-manifest | manifest.yaml | uploaded | completed |
| stx-openstack | 1.0-199-
| | versioned | | | | apply was in progress. The application status has |
| | | | | | changed from 'applying' to 'apply-failed'. |
| | | | | | |
+------
[sysadmin@ controller- 1 log(keystone_ admin)] $ fm alarm-list ----+-- ------- ------- ------- ------- ------- ------- ------- ------- ------- -----+- ------- ------- ------- ------- ------- --+---- ------+ ------- ------- -----+ ----+-- ------- ------- ------- ------- ------- ------- ------- ------- ------- -----+- ------- ------- ------- ------- ------- --+---- ------+ ------- ------- -----+ a22d4fc2- 1d0b-4b3e- | critical | 2022-05-18T09:33: | 81.instance= | | 28.306899 | 9c0d-4791- ba86-e836a1ff31 e1 | | | -1.memory= platform | critical | 2022-05-18T09:07: | =stx-openstack | major | 2022-05-18T09:03: | ----+-- ------- ------- ------- ------- ------- ------- ------- ------- ------- -----+- ------- ------- ------- ------- ------- --+---- ------+ ------- ------- -----+
+------
| Alarm ID | Reason Text | Entity ID | Severity | Time Stamp |
+------
| 700.005 | Instance admin-vm-1 owned by admin is rebooting on host controller-0 | tenant=
| | | abc4-351dff8ff5
| | | 0c378a47-
| | | | | |
| 100.103 | Memory threshold exceeded ; threshold 90.00%, actual 111.50% | host=controller
| | | | | 09.696940 |
| | | | | |
| 750.002 | Application Apply Failure | k8s_application
| | | | | 33.056162 |
| | | | | |
+------
I will attach new collected logs.