Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't push to staging charmstore #818

Closed
cmars opened this issue Jul 31, 2018 · 4 comments
Closed

Can't push to staging charmstore #818

cmars opened this issue Jul 31, 2018 · 4 comments
Assignees
Labels
Milestone

Comments

@cmars
Copy link
Contributor

cmars commented Jul 31, 2018

I'm unable to push a charm to staging for testing:

$ charm push ./docker-registry cs:\~yellow/docker-registry
ERROR cannot post archive: cannot put archive blob: failed to PUT object 6c7efa2332159e63-ae6bf8e21af639c0 from container charmstore-blobs
caused by: failed reading the request data, read 0 of 4641529 bytes
caused by: EOF
@wallyworld
Copy link
Member

We don't think this is a charmstore issue. See go-goose/goose#66

@johnsca
Copy link

johnsca commented Jul 31, 2018

@wallyworld I don't know if that issue is the cause of the failures I see because it would imply that immediately calling charm push again would succeed but that's not what I see. When I do it in a while loop, it can take anywhere between 1 and 30-something attempts before it succeeds, but it always does eventually, and there's no consistency in how many attempts it takes. (NB: the failures I see are identical to what @cmars put above.)

@johnsca
Copy link

johnsca commented Jul 31, 2018

It's also worth noting that even for a brand new charm or bundle, when it fails the rev counter gets incremented even when nothing gets uploaded. An example:

[johnsca@murdoch:~/juju/envs/caas/bundles] $ while ! JUJU_CHARMSTORE=https://api.staging.jujucharms.com/charmstore charm push ./kubeflow cs:~johnsca/kubeflow; do sleep 1; done
ERROR cannot post archive: cannot put archive blob: failed to PUT object 767bafc550926094-a36bf8e21af639c0 from container charmstore-blobs
caused by: failed reading the request data, read 0 of 756 bytes
caused by: EOF
ERROR cannot post archive: cannot put archive blob: failed to PUT object 767bafc550926094-a26bf8e21af639c0 from container charmstore-blobs
caused by: failed reading the request data, read 0 of 756 bytes
caused by: EOF
ERROR cannot post archive: cannot put archive blob: failed to PUT object 767bafc550926094-dd6bf8e21af639c0 from container charmstore-blobs
caused by: failed reading the request data, read 0 of 756 bytes
caused by: EOF
ERROR cannot post archive: cannot put archive blob: failed to PUT object 767bafc550926094-dc6bf8e21af639c0 from container charmstore-blobs
caused by: failed reading the request data, read 0 of 756 bytes
caused by: EOF
ERROR cannot post archive: cannot put archive blob: failed to PUT object 767bafc550926094-df6bf8e21af639c0 from container charmstore-blobs
caused by: failed reading the request data, read 0 of 756 bytes
caused by: EOF
ERROR cannot post archive: cannot put archive blob: failed to PUT object 767bafc550926094-de6bf8e21af639c0 from container charmstore-blobs
caused by: failed reading the request data, read 0 of 756 bytes
caused by: EOF
ERROR cannot post archive: cannot put archive blob: failed to PUT object 767bafc550926094-d96bf8e21af639c0 from container charmstore-blobs
caused by: failed reading the request data, read 0 of 756 bytes
caused by: EOF
ERROR cannot post archive: cannot put archive blob: failed to PUT object 767bafc550926094-d86bf8e21af639c0 from container charmstore-blobs
caused by: failed reading the request data, read 0 of 756 bytes
caused by: EOF
ERROR cannot post archive: cannot put archive blob: failed to PUT object 767bafc550926094-db6bf8e21af639c0 from container charmstore-blobs
caused by: failed reading the request data, read 0 of 756 bytes
caused by: EOF
ERROR cannot post archive: cannot put archive blob: failed to PUT object 767bafc550926094-da6bf8e21af639c0 from container charmstore-blobs
caused by: failed reading the request data, read 0 of 756 bytes
caused by: EOF
ERROR cannot post archive: cannot put archive blob: failed to PUT object 767bafc550926094-d56bf8e21af639c0 from container charmstore-blobs
caused by: failed reading the request data, read 0 of 756 bytes
caused by: EOF
ERROR cannot post archive: cannot put archive blob: failed to PUT object 767bafc550926094-d46bf8e21af639c0 from container charmstore-blobs
caused by: failed reading the request data, read 0 of 756 bytes
caused by: EOF
ERROR cannot post archive: cannot put archive blob: failed to PUT object 767bafc550926094-d76bf8e21af639c0 from container charmstore-blobs
caused by: failed reading the request data, read 0 of 756 bytes
caused by: EOF
url: cs:~johnsca/bundle/kubeflow-13
channel: unpublished

Then:

[johnsca@murdoch:~/juju/envs/caas/bundles] $ for i in {0..13}; do JUJU_CHARMSTORE=https://api.staging.jujucharms.com/charmstore charm show cs:~johnsca/kubeflow-$i; done
ERROR cannot get metadata from /~johnsca/kubeflow-0/meta/any?include=perm&include=charm-metadata&include=bundle-metadata&include=published&include=promulgated&include=owner&include=terms&include=id-name&include=id-revision&include=supported-series&include=common-info: no matching charm or bundle for cs:~johnsca/kubeflow-0
ERROR cannot get metadata from /~johnsca/kubeflow-1/meta/any?include=perm&include=charm-metadata&include=bundle-metadata&include=published&include=promulgated&include=owner&include=terms&include=id-name&include=id-revision&include=supported-series&include=common-info: no matching charm or bundle for cs:~johnsca/kubeflow-1
ERROR cannot get metadata from /~johnsca/kubeflow-2/meta/any?include=perm&include=charm-metadata&include=bundle-metadata&include=published&include=promulgated&include=owner&include=terms&include=id-name&include=id-revision&include=supported-series&include=common-info: no matching charm or bundle for cs:~johnsca/kubeflow-2
ERROR cannot get metadata from /~johnsca/kubeflow-3/meta/any?include=perm&include=charm-metadata&include=bundle-metadata&include=published&include=promulgated&include=owner&include=terms&include=id-name&include=id-revision&include=supported-series&include=common-info: no matching charm or bundle for cs:~johnsca/kubeflow-3
ERROR cannot get metadata from /~johnsca/kubeflow-4/meta/any?include=perm&include=charm-metadata&include=bundle-metadata&include=published&include=promulgated&include=owner&include=terms&include=id-name&include=id-revision&include=supported-series&include=common-info: no matching charm or bundle for cs:~johnsca/kubeflow-4
ERROR cannot get metadata from /~johnsca/kubeflow-5/meta/any?include=perm&include=charm-metadata&include=bundle-metadata&include=published&include=promulgated&include=owner&include=terms&include=id-name&include=id-revision&include=supported-series&include=common-info: no matching charm or bundle for cs:~johnsca/kubeflow-5
ERROR cannot get metadata from /~johnsca/kubeflow-6/meta/any?include=perm&include=charm-metadata&include=bundle-metadata&include=published&include=promulgated&include=owner&include=terms&include=id-name&include=id-revision&include=supported-series&include=common-info: no matching charm or bundle for cs:~johnsca/kubeflow-6
ERROR cannot get metadata from /~johnsca/kubeflow-7/meta/any?include=perm&include=charm-metadata&include=bundle-metadata&include=published&include=promulgated&include=owner&include=terms&include=id-name&include=id-revision&include=supported-series&include=common-info: no matching charm or bundle for cs:~johnsca/kubeflow-7
ERROR cannot get metadata from /~johnsca/kubeflow-8/meta/any?include=perm&include=charm-metadata&include=bundle-metadata&include=published&include=promulgated&include=owner&include=terms&include=id-name&include=id-revision&include=supported-series&include=common-info: no matching charm or bundle for cs:~johnsca/kubeflow-8
ERROR cannot get metadata from /~johnsca/kubeflow-9/meta/any?include=perm&include=charm-metadata&include=bundle-metadata&include=published&include=promulgated&include=owner&include=terms&include=id-name&include=id-revision&include=supported-series&include=common-info: no matching charm or bundle for cs:~johnsca/kubeflow-9
ERROR cannot get metadata from /~johnsca/kubeflow-10/meta/any?include=perm&include=charm-metadata&include=bundle-metadata&include=published&include=promulgated&include=owner&include=terms&include=id-name&include=id-revision&include=supported-series&include=common-info: no matching charm or bundle for cs:~johnsca/kubeflow-10
ERROR cannot get metadata from /~johnsca/kubeflow-11/meta/any?include=perm&include=charm-metadata&include=bundle-metadata&include=published&include=promulgated&include=owner&include=terms&include=id-name&include=id-revision&include=supported-series&include=common-info: no matching charm or bundle for cs:~johnsca/kubeflow-11
ERROR cannot get metadata from /~johnsca/kubeflow-12/meta/any?include=perm&include=charm-metadata&include=bundle-metadata&include=published&include=promulgated&include=owner&include=terms&include=id-name&include=id-revision&include=supported-series&include=common-info: no matching charm or bundle for cs:~johnsca/kubeflow-12
Name                    kubeflow
Owner                   johnsca
Revision                13
Promulgated             false
Home page
Bugs url
Read                    johnsca
Write                   johnsca
                         
CHANNEL                 CURRENT

@hmlanigan
Copy link
Member

@wallyworld, it looks like the charmstore imports swift from github.com/ncw/swift, not the goose version? I tracked the error to the blob store, but I haven't found the link from the blob store to goose/swift yet.

@mhilton mhilton self-assigned this Aug 8, 2018
@mhilton mhilton added the bug label Aug 8, 2018
@mhilton mhilton added this to the next milestone Aug 8, 2018
@mhilton mhilton closed this as completed Sep 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants