Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies replies
    3
  • Answers answer
    1
  • Subscribers subscribers
    16
  • Views views
    192
  • Users 0 members are here
Related
Options

How to get rid of failed deployment icons in OMT Apphub

gero_1

NNMI 23.4

Oracle Linux 9

OMT 23.4 on one machine

Verdtca DB on dedicated machine

We had one failed deployment attempt, see icon in the middle with namespace nom and a successful deployment with namespace nom1 

Now we cannot delete the failed one from the apphub deployment because the tree little points in the lower right corner are greyed out, do

we have a procedure to delete the failed deployment "tile-icon" 

  • Suggested Answer

    0

    I have not tried myself but following points to a remedy..

    Can't delete an application deployment on AppHub - OPTIC Management Toolkit

  • 0 in reply to 

    Thanks for the idea, tested that but when it comes to the helm list -a -A I of course there I can 

    see a deployment, basically the second one with namespace nom1 that worked (1) but here stops the procedure because of:

     you can't see that deployment in the Kubernetes environment anymore, continue with the following steps. However, if you still see the deployment in the Kubernetes environment, don't perform the following steps.

     (1).  [root@XXXXX ~]# helm list -a -A
    NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
    apphub core 1 2024-09-06 14:49:15.510630579 +0200 CEST deployed apphub-1.24.0+23.4.0-190 23.4
    itom-logrotate core 1 2024-09-06 14:49:25.957024327 +0200 CEST deployed itom-log-rotate-1.9.0-48 1.9.0-48
    itom-velero core 1 2024-09-06 14:53:17.048686751 +0200 CEST deployed itom-velero-1.3.0-111 1.3.0-111
    itudepoyment nom1 1 2024-09-17 09:44:47.128950893 +0000 UTC deployed nom-1.10.0+23.4.0-318 23.4
    kube-registry core 1 2024-09-06 14:49:32.008282553 +0200 CEST deployed itom-kube-registry-1.8.0-58 1.8.0-58
    nfs-provisioner core 1 2024-09-06 14:49:01.02456171 +0200 CEST deployed itom-nfs-provisioner-1.3.0-12 1.3.0-0012

  • 0 in reply to 

    There are some options but may be a better idea to get support from OT by opening a support case. I think its related with a corruption in one of the DB tables record.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.