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

Swich to new gcloud API for GCE MIGs #11692

Merged
merged 1 commit into from Aug 3, 2015

Conversation

wojtek-t
Copy link
Member

@k8s-bot
Copy link

k8s-bot commented Jul 22, 2015

GCE e2e build/test failed for commit 632f1d74443d1948d5750e9a5329db622245053e.

# command returns, but currently it returns before the instances come up due
# to gcloud's deficiency.
wait-for-minions-to-run
gcloud beta compute instance-groups managed wait-until-stable "${NODE_INSTANCE_PREFIX}-group"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this need || true at the end in case of errors? or some other error checking?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

@roberthbailey
Copy link
Contributor

@wojtek-t why did you mark this as do not merge?

@wojtek-t
Copy link
Member Author

@roberthbailey - the new API is not yet released (should be today according to MIG team from Warsaw) - this is why Jenkins tests failed. [I've tested by updating my gcloud to (still) experimental version]

@wojtek-t
Copy link
Member Author

[by new API I mean support for it in gcloud]

@roberthbailey
Copy link
Contributor

Ah. I know that the new raw API is out already; I didn't realize gcloud support hadn't rolled out yet.

@k8s-bot
Copy link

k8s-bot commented Jul 22, 2015

GCE e2e build/test failed for commit bc4c526a4400035d8af8812f62ba6ab524e54e27.

@k8s-bot
Copy link

k8s-bot commented Jul 23, 2015

GCE e2e build/test failed for commit 247cf8faa56debaef38bf467780cedcbc0e0e151.

@wojtek-t
Copy link
Member Author

Jenkins is now failing with the following error:

You do not currently have this command group installed.  Using it requires the installation of components: [beta]
ERROR: (gcloud) You cannot perform this action because you do not have permission to modify the Google Cloud SDK installation directory [/usr/local/share/google/google-cloud-sdk].

How can we workaround it (and do we want?)?

@roberthbailey
Copy link
Contributor

/cc @jlowdermilk

@j3ffml
Copy link
Contributor

j3ffml commented Jul 23, 2015

It looks like the beta component actually is installed for shared gcloud. Maybe someone recently bumped it? @k8s-bot retest this please

@mikedanese
Copy link
Member

Please reassign when this is ready to merge.

@k8s-bot
Copy link

k8s-bot commented Jul 27, 2015

GCE e2e build/test failed for commit 59962376f6e7c77a6d0a4d11d0be0d90fb391d04.

@k8s-bot
Copy link

k8s-bot commented Jul 30, 2015

GCE e2e build/test failed for commit 92623bcdcf4ff930315e4e97110be371c48986d6.

@k8s-bot
Copy link

k8s-bot commented Jul 30, 2015

GCE e2e build/test failed for commit ef9f6c72de45151142061fe1f99eee61a3e840ef.

@wojtek-t
Copy link
Member Author

@jlowdermilk (sorry for late response). It seems that beta is not installed - i.e. after rebasing today it's still not there. Is there any way to work around it? Is it possible to proceed with that change?

@j3ffml
Copy link
Contributor

j3ffml commented Jul 30, 2015

@wojtek-t, sorry I was looking at the wrong project. I don't have access to the pr builder jenkins master to install the beta component, but I've pinged @ixdy, and will update it shortly.

@j3ffml
Copy link
Contributor

j3ffml commented Jul 30, 2015

@k8s-bot test this please

@k8s-bot
Copy link

k8s-bot commented Jul 30, 2015

GCE e2e build/test failed for commit ef9f6c72de45151142061fe1f99eee61a3e840ef.

@wojtek-t
Copy link
Member Author

@wojtek-t, sorry I was looking at the wrong project. I don't have access to the pr builder jenkins master to install the beta component, but I've pinged @ixdy, and will update it shortly.

@ixdy - did you have chance to look into it?

@k8s-bot
Copy link

k8s-bot commented Jul 31, 2015

GCE e2e build/test failed for commit ff9292509de6c3d03395ff909264373f24c0ea0c.

@k8s-bot
Copy link

k8s-bot commented Jul 31, 2015

GCE e2e build/test failed for commit ef189bbb1cde4b961fee5fe1649c4051eee17a21.

@k8s-bot
Copy link

k8s-bot commented Jul 31, 2015

GCE e2e build/test passed for commit 74a73511767e7f2e336442459436c50433ce4e58.

@wojtek-t wojtek-t changed the title [Do NOT merge] Swich to new gcloud API for GCE MIGs Swich to new gcloud API for GCE MIGs Jul 31, 2015
@wojtek-t
Copy link
Member Author

This is now ready for review.

@wojtek-t wojtek-t assigned roberthbailey and unassigned wojtek-t Jul 31, 2015
@wojtek-t
Copy link
Member Author

@roberthbailey - can you please take a look (or delegate)?

@@ -695,16 +677,16 @@ function kube-up {
write-node-env
create-node-instance-template

gcloud preview managed-instance-groups --zone "${ZONE}" \
gcloud beta compute instance-groups managed \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I tested a similar command yesterday this was working for me without the 'beta' cmd group, so I think we can remove that from the script.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes - it seems to work now.

Done.

@roberthbailey
Copy link
Contributor

LGTM, but I think we should use gcloud compute instance-groups rather than gcloud beta compute instance-groups in all of these commands.

# command returns, but currently it returns before the instances come up due
# to gcloud's deficiency.
wait-for-minions-to-run
gcloud beta compute instance-groups managed wait-until-stable \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

probably need --project here too

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's not needed, but I've added it for consistency.

@k8s-bot
Copy link

k8s-bot commented Aug 3, 2015

GCE e2e build/test passed for commit 2d95cd4.

@wojtek-t
Copy link
Member Author

wojtek-t commented Aug 3, 2015

@roberthbailey - PTAL

@roberthbailey
Copy link
Contributor

LGTM.

@roberthbailey roberthbailey added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 3, 2015
@roberthbailey
Copy link
Contributor

@wojtek-t Please cherry pick this into the 1.0 release branch (after it's been merged) so that our release branch validation tests are using the current API for MIGs as well (I doubt the preview commands will work for much longer).

@brendandburns
Copy link
Contributor

@k8s-bot test this [testing build queue, sorry for the noise]

@k8s-bot
Copy link

k8s-bot commented Aug 3, 2015

GCE e2e build/test passed for commit 2d95cd4.

@brendandburns
Copy link
Contributor

Automatic merge from SubmitQueue

brendandburns added a commit that referenced this pull request Aug 3, 2015
@brendandburns brendandburns merged commit 2e68002 into kubernetes:master Aug 3, 2015
@wojtek-t wojtek-t deleted the new_api_instance_groups branch August 4, 2015 08:44
alex-mohr referenced this pull request Aug 4, 2015
…92-upstream-release-1.0

Auto commit by PR queue bot
@brendandburns brendandburns mentioned this pull request Aug 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants