VMware Cloud Community
ymichalak
Hot Shot
Hot Shot

[vRA 8.1] - Cannot delete project

Hello,

On vRA 8.1 patch 2 we can't delete an empty project :

pastedImage_0.png

pastedImage_1.png

Anyone have this error ?

Thx for your feedback

Tags (3)
6 Replies
siglert
Enthusiast
Enthusiast

Use Postman or the API to delete the project.

Reply
0 Kudos
ymichalak
Hot Shot
Hot Shot

Thx siglert​,

Already try... It's the same error :

pastedImage_0.png

Reply
0 Kudos
Lalegre
Virtuoso
Virtuoso

Could be possible that you actually still have somethings associated to the Project?

Have you also checked in Service Broker?

Reply
0 Kudos
ymichalak
Hot Shot
Hot Shot

Nothing on cloud broker :

pastedImage_0.png

Nothing on Cloud assembly :

pastedImage_1.png

Reply
0 Kudos
Paul87
Contributor
Contributor

Hello,

Were you able to delete the projects?

I am encountering the same issue and nothing is working.

 

Thank you,

Paul

Reply
0 Kudos
Paul87
Contributor
Contributor

In case someone has the same issue. I managed to fix this.

In the vRA logs, I found the below error:



"ERROR codestream [host='codestream-app-8664b5f6bb-2sv7v' thread='reactor-http-epoll-6' user='' org='' trace='0f3e28d2-91b3-4945-89d6-1714824789ba' parent='' span='93dec90d-2dcf-4379-8e53-45bad69331e7'] c.v.c.service.impl.ToggleServiceImpl.lambda$fetch$2:124 - Error refreshing feature toggle list at timestamp 1699336877248 with error PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target; nested exception is javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target"

The issue is was that when we enabled the multi-tenant, the vRA LB kept it's old certificate.

Once I deleted the LB certificate and re-deployed, I was able to delete old and new projects.

Commands that I used can be found here -> https://kb.vmware.com/s/article/91815

---

Just in case the KB goes down:

  1. SSH / PuTTy into one vRA virtual appliance in the cluster (no need to do this on each node)
  2. Run the following command to check the current load-balancer certificate:
    vracli certificate load-balancer --list
  3. If the command from Step # 2 returns some certificate information, perform the following to correct the load-balancer certificate.
    1. Run the same command to store the current certificate data:
      vracli certificate load-balancer --list > /usr/current_cert.pem
    2. Delete the certificate information:
      vracli certificate load-balancer --delete
    3. Redeploy services:
      /opt/scripts/deploy.sh

 

Reply
0 Kudos