Impact of platform-integ-apps
Hi, After increasing the size of the kubelet, controller-1 (stand by controller) unlocked and then noticed platform-integ-apps applying had been triggered automatically. Change of the application status manually in the db, did not work. There are multiple workers and VMs running in the Openstack side and dedicated ceph also in use. Is it possible to completely remove the platform-integ-apps application and upload the application and apply, without impact on ceph and other components related to platform-integ-apps? Regards, Danishka
Hi, Here are the logs from both controllers and storage nodes. https://drive.google.com/drive/folders/1lKYUwWhit3BVC6xBl5U_3_V5csbM6bxx?usp... Please let me know if you need further information. Btw, there stx-openstack-apply log under /var/log/armada. Where exactly do logs available for platform-intg-apps apply? Regards, Danishka On Mon, Dec 4, 2023 at 10:55 AM open infra <openinfradn@gmail.com> wrote:
Hi,
After increasing the size of the kubelet, controller-1 (stand by controller) unlocked and then noticed platform-integ-apps applying had been triggered automatically.
Change of the application status manually in the db, did not work. There are multiple workers and VMs running in the Openstack side and dedicated ceph also in use.
Is it possible to completely remove the platform-integ-apps application and upload the application and apply, without impact on ceph and other components related to platform-integ-apps?
Regards, Danishka
Hello Danishka, If I got it right, the issue is that the platform-integ-apps was applied, then the system automatically initiated a reapply, and the app status stayed in 'applying' for an extended period, correct? It looks like, based on the logs, the reapplication was triggered due to an override, which coincidentally happened at a time close to the change in kubelet: sysinv 2023-12-03 09:39:33.984 99487 INFO sysinv.conductor.manager [-] There has been an overrides change, setting up reapply of platform-integ-apps sysinv 2023-12-03 09:46:41.127 99487 INFO sysinv.conductor.kube_app [-] Doing FluxCD operation apply with the following manifest: /opt/platform/fluxcd/22.06/platform-integ-apps/1.0-53/platform-integ-apps-fluxcd-manifests Do you just want the platform-integ-apps to remain normally as applied? There shouldn't be any problems with this reapply. If the app gets stuck in the 'applying' status, one approach to follow is to use application-abort and run the application-apply again. Regarding your question about performing a remove -> delete -> upload -> apply sequence without affecting Ceph and associated components, it shouldn't have any impacts and it could be a solution too. During the removal and deletion of this app, existing pools, volumes, and pods are not removed. Then you can proceed with uploading and applying the app again. As for platform-integ-apps logs, information associated with app operations (upload, apply, update, abort, remove, and delete) can be found in '/var/log/sysinv.log'. For operational details, there are individual pod logs that are created for platform-integ-apps and can be accessed using the command 'kubectl logs -n <namespace> <pod_name>'. Best regards, Gabriel Cabral
participants (2)
-
gabriel.cabral＠windriver.com
-
open infra