juju attach does not like to be canceled

I experienced the same thing, except I didn't Ctrl-C the attach. It just timed out after several minutes. The kubernetes resource is about 1G in size.

Repeatable:

c@zeugmatic:~/src/master-node-split/cluster/juju$ juju attach kubernetes-master kubernetes=kubernetes.tar.gz
ERROR failed to upload resource "kubernetes": PUT https://10.55.32.49:17070/model/482a7b26-aff4-4bd6-8231-90adde29b8d3/applications/kubernetes-master/resources/kubernetes: cannot clean up after failed storage operation because: EOF: cannot add resource "buckets/482a7b26-aff4-4bd6-8231-90adde29b8d3/application-kubernetes-master/resources/kubernetes" to store at storage path "16e016a8-8dff-44ba-88dc-d96723a5d776": failed to write data: write tcp 10.55.32.49:42144->10.55.32.49:37017: write: broken pipe
c@zeugmatic:~/src/master-node-split/cluster/juju$ juju attach kubernetes-master kubernetes=kubernetes.tar.gz
ERROR failed to upload resource "kubernetes": PUT https://10.55.32.49:17070/model/482a7b26-aff4-4bd6-8231-90adde29b8d3/applications/kubernetes-master/resources/kubernetes: already staged

This is the workaround I came up with:

Connect to mongodb and run the following query to delete the staged documents:

To list the documents in staged state:

db.resources.find({"_id": /.*resource#.*#staged/}).pretty();

To remove the documents:

db.resources.deleteMany({"_id": /.*resource#.*#staged/});

Does anyone have any thoughts on why this approach could be wrong or incomplete?, for example other documents referencing the staged objects, etc.

Please reopen if this issue persists.