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.

Sign up for GitHub

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

Jump to bottom

gcloud unrecognized arguments --fields #25153

Closed
yujuhong opened this issue May 4, 2016 · 7 comments
Closed

gcloud unrecognized arguments --fields #25153

yujuhong opened this issue May 4, 2016 · 7 comments
Assignees
@dchen1107
Labels
area/test-infra kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@yujuhong
Copy link
Contributor

yujuhong commented May 4, 2016

https://console.cloud.google.com/storage/browser/kubernetes-jenkins/pr-logs/pull/25054/kubernetes-pull-build-test-e2e-gce/38324/

INSTANCE_GROUPS=e2e-gce-master-1-minion-group
NODE_NAMES=e2e-gce-master-1-minion-0pce e2e-gce-master-1-minion-3mfi e2e-gce-master-1-minion-4jgj e2e-gce-master-1-minion-bmu8 e2e-gce-master-1-minion-qirl e2e-gce-master-1-minion-vywd
usage: gcloud compute instances describe  NAME [optional flags]
ERROR: (gcloud.compute.instances.describe) unrecognized arguments:
  --fields
  networkInterfaces[0].accessConfigs[0].natIP
@yujuhong yujuhong added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. labels May 4, 2016
@yujuhong
Copy link
Contributor Author

yujuhong commented May 4, 2016

I believe all per-PR builds failed because of the same reason.

@yujuhong yujuhong mentioned this issue May 4, 2016
Merged
@spxtr
Copy link
Contributor

spxtr commented May 4, 2016

It's not a flake, it's just plain broken. Assigning to @ixdy, test infra oncall.

@ixdy
Copy link
Member

ixdy commented May 4, 2016

There appears to be a new gcloud release today: https://cloud.google.com/sdk/release_notes

Not sure if this was an expected breaking change or not. I don't see it in the release notes, anyway.

@ixdy ixdy assigned dchen1107 and unassigned ixdy May 4, 2016
@a-robinson
Copy link
Contributor

cc @k8s-oncall as well

@ixdy
Copy link
Member

ixdy commented May 4, 2016 •
edited
Loading

Reassigning to the buildcop. I'm pretty sure this isn't a test infra issue - OSS k8s is just broken with the latest release of gcloud.

@ixdy ixdy added kind/bug Categorizes issue or PR as related to a bug. and removed kind/flake Categorizes issue or PR as related to a flaky test. labels May 4, 2016
@ixdy ixdy changed the title e2e flake: gcloud unrecognized arguments --fields gcloud unrecognized arguments --fields May 4, 2016
@a-robinson a-robinson mentioned this issue May 4, 2016
Merged
@ixdy
Copy link
Member

ixdy commented May 4, 2016

Apparently --fields was an undocumented hidden flag that we should not have used. We are to replace the --fields and --format flags with
--format="value(networkInterfaces[0].accessConfigs[0].natIP)

We'll probably need to cherry-pick this fix.

@ixdy ixdy mentioned this issue May 4, 2016
Merged
@ixdy
Copy link
Member

ixdy commented May 4, 2016

Fix PR: #25159

@andyzheng0831 andyzheng0831 mentioned this issue May 4, 2016
Merged
This was referenced May 4, 2016
Merged
Merged
Merged
Merged
@aaronlevy aaronlevy mentioned this issue May 4, 2016
Merged
@spxtr spxtr mentioned this issue May 4, 2016
Merged
@peebs peebs mentioned this issue May 5, 2016
Merged
This was referenced May 5, 2016
Merged
Merged
@roberthbailey roberthbailey mentioned this issue May 5, 2016
Merged
This was referenced May 5, 2016
Closed
Closed
@yujuhong yujuhong mentioned this issue May 6, 2016
Merged
@dcbw dcbw mentioned this issue May 10, 2016
Merged
wonderfly added a commit to wonderfly/test-infra that referenced this issue May 16, 2016
@wonderfly
Disable e2e jobs for Trusty stable
79d2bc6 
They pin to the latest release on the `release-1.1` branch, which is broken by
kubernetes/kubernetes#25153. Since there is no
immediate plan of a patch release on that old branch, these jobs will continue
to fail. I am not deleting the jobs as Trusty stable will eventualy pass 1.1 and
move to 1.2 then start passing again.
wonderfly added a commit to wonderfly/test-infra that referenced this issue May 16, 2016
@wonderfly
Disable e2e jobs for Trusty stable
c03856c 
They pin to the latest release on the `release-1.1` branch, which is broken by
kubernetes/kubernetes#25153. Since there is no
immediate plan of a patch release on that old branch, these jobs will continue
to fail. I am not deleting the jobs as Trusty stable will eventualy pass 1.1 and
move to 1.2 then start passing again.
@wonderfly wonderfly mentioned this issue May 16, 2016
Merged
wonderfly added a commit to wonderfly/test-infra that referenced this issue May 17, 2016
@wonderfly
Disable e2e jobs for Trusty stable
76fae64 
They pin to the latest release on the `release-1.1` branch, which is broken by
kubernetes/kubernetes#25153. Since there is no
immediate plan of a patch release on that old branch, these jobs will continue
to fail. I am not deleting the jobs as Trusty stable will eventualy pass 1.1 and
move to 1.2 then start passing again.
openshift-publish-robot pushed a commit to openshift/kubernetes that referenced this issue Jun 20, 2020
@k8s-publishing-bot
Merge pull request kubernetes#25153 from sttts/sttts-fieldmanager-err…
6cd50ff 
…or-91748

Bug 1842660: 4.6: UPSTREAM: 91748: FieldManager: Reset if we receive nil or a list with one

Origin-commit: cb5e7b5ae4bfa7ae2ad66646411bd8810dc6bd50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dchen1107 dchen1107

Labels
area/test-infra kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@a-robinson @spxtr @dchen1107 @ixdy @yujuhong