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

1.3.9 images not published on gcr.io? #34099

Closed
justinsb opened this issue Oct 5, 2016 · 17 comments
Closed

1.3.9 images not published on gcr.io? #34099

justinsb opened this issue Oct 5, 2016 · 17 comments
Assignees
Labels
area/build-release area/release-eng Issues or PRs related to the Release Engineering subproject kind/bug Categorizes issue or PR as related to a bug.

Comments

@justinsb
Copy link
Member

justinsb commented Oct 5, 2016

I can't pull e.g. kube-scheduler 1.3.8, but I can pull 1.3.7:

> docker pull gcr.io/google_containers/kube-proxy:v1.3.8
Pulling repository gcr.io/google_containers/kube-proxy
Tag v1.3.8 not found in repository gcr.io/google_containers/kube-proxy
> docker pull gcr.io/google_containers/kube-proxy:v1.3.7
v1.3.7: Pulling from google_containers/kube-proxy
fdd5d7827f33: Pull complete 
a3ed95caeb02: Pull complete 
224cd3e34dea: Pull complete 
420069371c3c: Pull complete 
Digest: sha256:64aeac4439486dea2485079f863a650d2310f9652d82a16cfc7e7a4223a1b292
Status: Downloaded newer image for gcr.io/google_containers/kube-proxy:v1.3.7
@k8s-github-robot k8s-github-robot added area/kube-proxy area/release-eng Issues or PRs related to the Release Engineering subproject labels Oct 5, 2016
@mikekap
Copy link
Contributor

mikekap commented Oct 23, 2016

Looks like 1.3.9 is missing too. 1.4.4 and 1.2.7 are present though.

@MikeSpreitzer
Copy link
Member

FYI, you can query for the list of tags that are available with this command: curl https://gcr.io/v2/google_containers/hyperkube/tags/list | jq .. Here is the tail of what I got just now:

    "v1.3.7",
    "v1.3.7-beta.0",
    "v1.3.8-beta.0",
    "v1.4.0",
    "v1.4.0-alpha.0",
    "v1.4.0-alpha.1",
    "v1.4.0-alpha.2",
    "v1.4.0-alpha.3",
    "v1.4.0-beta.0",
    "v1.4.0-beta.1",
    "v1.4.0-beta.10",
    "v1.4.0-beta.11",
    "v1.4.0-beta.2",
    "v1.4.0-beta.3",
    "v1.4.0-beta.5",
    "v1.4.0-beta.6",
    "v1.4.0-beta.7",
    "v1.4.0-beta.8",
    "v1.4.1",
    "v1.4.1-beta.0",
    "v1.4.2",
    "v1.4.2-beta.0",
    "v1.4.2-beta.1",
    "v1.4.3",
    "v1.4.3-beta.0",
    "v1.4.4",
    "v1.4.4-beta.0",
    "v1.4.5-beta.0",
    "v1.5.0-alpha.0",
    "v1.5.0-alpha.1"

@MikeSpreitzer
Copy link
Member

(and there's no v1.3.10-beta.0 either)

@MikeSpreitzer
Copy link
Member

@justinsb you might get more attention on this issue if you changed its name to refer to 1.3.9

@justinsb justinsb changed the title 1.3.8 images not published on gcr.io? 1.3.9 images not published on gcr.io? Oct 25, 2016
@ixdy
Copy link
Member

ixdy commented Oct 25, 2016

@david-mcmahon

@ixdy
Copy link
Member

ixdy commented Oct 25, 2016

cc @alex-mohr @nikhiljindal @fabioy

@david-mcmahon
Copy link
Contributor

@fabioy has the tooling to push these missing images.

@fabioy fabioy added kind/bug Categorizes issue or PR as related to a bug. area/build-release and removed area/kube-proxy labels Oct 25, 2016
@fabioy
Copy link
Contributor

fabioy commented Oct 25, 2016

Apologies for missing this earlier (bug triage didn't land this on my radar).

The 1.3.9 and v1.3.10-beta.0 images should be available now. I'm trying to figure out what to do with the 1.3.8 images.

@david-mcmahon david-mcmahon self-assigned this Oct 25, 2016
@david-mcmahon
Copy link
Contributor

Thanks @fabioy! I'l take care of 1.3.8.

@david-mcmahon
Copy link
Contributor

v1.3.8 uploaded.

@MikeSpreitzer
Copy link
Member

I see 1.3.9 and 1.3.10-beta.0 now, but not 1.3.8.

@MikeSpreitzer
Copy link
Member

FYI, still no 1.3.8 (not that I miss it very much)

@justinsb
Copy link
Member Author

Thanks for fixing! 1.3.9 is the one that is particularly important, so thank you.

@david-mcmahon
Copy link
Contributor

@MikeSpreitzer ok now?

$ curl -s https://gcr.io/v2/google_containers/kube-proxy/tags/list | jq . |fgrep -w v1.3.8\"
        "v1.3.8"
    "v1.3.8",

@MikeSpreitzer
Copy link
Member

MikeSpreitzer commented Oct 26, 2016

@david-mcmahon I do not see it for hyperkube.

mjs10:~ mspreitz$ curl -s https://gcr.io/v2/google_containers/hyperkube/tags/list | jq . | fgrep 1.3.8 ; date
        "v1.3.8-beta.0"
    "v1.3.8-beta.0",
Wed Oct 26 14:49:02 EDT 2016

@david-mcmahon
Copy link
Contributor

Yes, hyperkube didn't make it up due to a hiccup. Check now.

$ curl -s https://gcr.io/v2/google_containers/hyperkube/tags/list | jq . | fgrep 1.3.8
        "v1.3.8-beta.0"
        "v1.3.8"
    "v1.3.8",
    "v1.3.8-beta.0",

@MikeSpreitzer
Copy link
Member

AOK now. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build-release area/release-eng Issues or PRs related to the Release Engineering subproject kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

7 participants