search

crossplane / crossplane-cli

Tools and commands for managing and developing Crossplane
Apache License 2.0
14 stars 12 forks source link

kubectl crossplane package uninstall: gets stuck for 30 seconds and returns error #56

Closed prasek closed 4 years ago

prasek commented 4 years ago

Problem

kubectl crossplane package uninstall gets stuck for 30 seconds, but the package is successfully deleted.

Using:

RELEASE=master && curl -sL https://raw.githubusercontent.com/crossplane/crossplane-cli/"${RELEASE}"/bootstrap.sh | RELEASE=${RELEASE} bash

kubectl crossplane package install --namespace ws1 crossplane/app-wordpress:v0.3.0 app-wordpress <registry>

kubectl crossplane package uninstall --namespace ws1 app-wordpress

stackinstall.stacks.crossplane.io "app-wordpress" deleted

Error from server (InternalError): an error on the server ("<html><head>\n<meta http-equiv=\"content-type\" content=\"text/html;charset=utf-8\">\n<title>502 Server Error</title>\n</head>\n<body text=#000000 bgcolor=#ffffff>\n<h1>Error: Server Error</h1>\n<h2>The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds.</h2>\n<h2></h2>\n</body></html>") has prevented the request from succeeding

Additional repro steps:

RELEASE=master && curl -sL https://raw.githubusercontent.com/crossplane/crossplane-cli/"${RELEASE}"/bootstrap.sh | RELEASE=${RELEASE} bash

kubectl crossplane package install --cluster --namespace crossplane-system crossplane/provider-aws:v0.8.0 provider-aws <registry>

kubectl crossplane package uninstall --cluster --namespace crossplane-system provider-aws

clusterstackinstall.stacks.crossplane.io "provider-aws" deleted

Error from server (InternalError): an error on the server ("<html><head>\n<meta http-equiv=\"content-type\" content=\"text/html;charset=utf-8\">\n<title>502 Server Error</title>\n</head>\n<body text=#000000 bgcolor=#ffffff>\n<h1>Error: Server Error</h1>\n<h2>The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds.</h2>\n<h2></h2>\n</body></html>") has prevented the request from succeeding
hasheddan commented 4 years ago

@prasek it appears this is likely unrelated to recent updates, do you have more context around the situation in which this happened?

prasek commented 4 years ago

@hasheddan agree unlikely related to recent updates, added repro steps and env info above

prasek commented 4 years ago

still running into this

kubectl delete mysqlservervirtualnetworkrules.database.azure.crossplane.io my-cool-app-vnetrule

mysqlservervirtualnetworkrule.database.azure.crossplane.io "my-cool-app-vnetrule" deleted

Error from server (InternalError): an error on the server ("<html><head>\n<meta http-equiv=\"content-type\" content=\"text/html;charset=utf-8\">\n<title>502 Server Error</title>\n</head>\n<body text=#000000 bgcolor=#ffffff>\n<h1>Error: Server Error</h1>\n<h2>The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds.</h2>\n<h2></h2>\n</body></html>") has prevented the request from succeeding
jbw976 commented 4 years ago

I also ran into this today while testing the flow for using packages from private repos:

> kubectl crossplane package uninstall -n private-app private-repo-wordpress
stackinstall.stacks.crossplane.io "private-repo-wordpress" deleted
Error from server (InternalError): an error on the server ("<html><head>\n<meta http-equiv=\"content-type\" content=\"text/html;charset=utf-8\">\n<title>502 Server Error</title>\n</head>\n<body text=#000000 bgcolor=#ffffff>\n<h1>Error: Server Error</h1>\n<h2>The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds.</h2>\n<h2></h2>\n</body></html>") has prevented the request from succeeding
jbw976 commented 4 years ago

This does not appear to be specific to the crossplane-cli, as @prasek last example was actually on a kubectl delete for an azure resource. From my recent debugging, it looks specific to Upbound's internal infrastructure. I'm going to close this issue out and follow up in an internal project.