Andrej Podhradsky
Andrej Podhradsky
not ready...I still need to finish some changes and test it
Now, waiting until the wrapanapi's PR is merged https://github.com/RedHatQE/wrapanapi/pull/455
Right, so maybe we could consider introducing a new variable `DELETE_OCP` which will work similar to `DELETE_VM`. That means, if we identified a VM or VPC with tag `kubernetes.io/cluster/${DELETE_OCP}*` then...
The question is - which resource(s) should we look for and check the tag `kubernetes.io/cluster/${CLUSTER_ID}`. Maybe we could look for VPCs as many resources are directly tied with a VPC....
If someone is interested I have prepared a quick PoC (WIP) at https://github.com/RedHatQE/cloudwash/pull/18
I will just add a link to a nice solution I sometimes use https://github.com/lianghong/delete_vpc We can take some inspiration from that ;-)
Hi @LiZhang19817 I hit exactly the same error. Unfortunately, today with a fresh install I was not able reproduce it :(
That's a very good point. I will definitely try it. Thanks!
I have significantly increased the memory (from 16 GB to 64 GB) but the issue remains :(
I have noticed another thing... there is always only one process `gunicorn` consuming almost 100% CPU core (not happening with mirror-registry 1.3.x where I can see more `gunicorn` processes each...