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

move columns into wide option to make result more readable #20557

Merged
merged 1 commit into from
Feb 15, 2016

Conversation

adohe-zz
Copy link

@adohe-zz adohe-zz commented Feb 3, 2016

Fixes #19775

@k8s-bot
Copy link

k8s-bot commented Feb 3, 2016

Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist")

If this message is too spammy, please complain to ixdy.

@k8s-bot
Copy link

k8s-bot commented Feb 3, 2016

Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist")

If this message is too spammy, please complain to ixdy.

@k8s-github-robot
Copy link

PR needs rebase

@k8s-github-robot
Copy link

Labelling this PR as size/L

@k8s-github-robot k8s-github-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 3, 2016
@bgrant0607
Copy link
Member

cc @erictune @Kargakis

@bgrant0607
Copy link
Member

cc @janetkuo

var replicationControllerColumns = []string{"CONTROLLER", "CONTAINER(S)", "IMAGE(S)", "SELECTOR", "REPLICAS", "AGE"}
var jobColumns = []string{"JOB", "CONTAINER(S)", "IMAGE(S)", "SELECTOR", "SUCCESSFUL"}
var serviceColumns = []string{"NAME", "CLUSTER_IP", "EXTERNAL_IP", "PORT(S)", "SELECTOR", "AGE"}
var replicationControllerColumns = []string{"CONTROLLER", "REPLICAS", "AGE"}
Copy link
Member

Choose a reason for hiding this comment

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

Please rebase. Deployment columns are now:

var deploymentColumns = []string{"NAME", "DESIRED", "CURRENT", "UP-TO-DATE", "AVAILABLE", "AGE"}

As suggested by @Kargakis, please display DESIRED and CURRENT rather than just REPLICAS for ReplicationController.

Copy link
Member

Choose a reason for hiding this comment

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

It could be done in a separate PR, but DESIRED and CURRENT would be nice to have for DaemonSet also.

Copy link
Author

Choose a reason for hiding this comment

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

Ok, I will open a separate PR to add DESIRED and CURRENT to ReplicationController and DaemonSet as soon as possible.

Copy link
Author

Choose a reason for hiding this comment

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

@bgrant0607 I will open a separate PR to add DESIRED and CURRENT to ReplicationController and DaemonSet later.

@adohe-zz
Copy link
Author

adohe-zz commented Feb 4, 2016

Ok, I will do it now

@adohe-zz adohe-zz force-pushed the kubectl_update_wide branch from ddac553 to 0377f4f Compare February 4, 2016 04:37
@k8s-github-robot k8s-github-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 4, 2016
@adohe-zz adohe-zz force-pushed the kubectl_update_wide branch from 034b786 to 8bb7b3d Compare February 4, 2016 06:14
var replicationControllerColumns = []string{"CONTROLLER", "CONTAINER(S)", "IMAGE(S)", "SELECTOR", "REPLICAS", "AGE"}
var jobColumns = []string{"JOB", "CONTAINER(S)", "IMAGE(S)", "SELECTOR", "SUCCESSFUL"}
var serviceColumns = []string{"NAME", "CLUSTER-IP", "EXTERNAL-IP", "PORT(S)", "SELECTOR", "AGE"}
var replicationControllerColumns = []string{"CONTROLLER", "REPLICAS", "AGE"}
Copy link
Contributor

Choose a reason for hiding this comment

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

While on this, can you rename REPLICAS to DESIRED and add CURRENT to show rc.status.replicas?

cc: @bgrant0607

Copy link
Member

Choose a reason for hiding this comment

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

We do want that change, but a separate PR is fine.

@bgrant0607 bgrant0607 closed this Feb 4, 2016
@bgrant0607 bgrant0607 reopened this Feb 4, 2016
@bgrant0607 bgrant0607 added lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-merge labels Feb 4, 2016
@bgrant0607 bgrant0607 assigned 0xmichalis and unassigned deads2k Feb 4, 2016
@k8s-github-robot
Copy link

@bgrant0607
You must link to the test flake issue which caused you to request this manual re-test.
Re-test requests should be in the form of: k8s-bot test this issue: #<number>
Here is the list of open test flakes.

1 similar comment
@k8s-github-robot
Copy link

@bgrant0607
You must link to the test flake issue which caused you to request this manual re-test.
Re-test requests should be in the form of: k8s-bot test this issue: #<number>
Here is the list of open test flakes.

@k8s-github-robot k8s-github-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 4, 2016
@k8s-bot
Copy link

k8s-bot commented Feb 4, 2016

GCE e2e build/test failed for commit 8bb7b3db1320466997f8a8f4753e95dc3dc8b100.

@adohe-zz
Copy link
Author

adohe-zz commented Feb 4, 2016

For log, this case failed:

FAIL    k8s.io/kubernetes/pkg/client/unversioned/remotecommand  300.059s

@k8s-bot
Copy link

k8s-bot commented Feb 4, 2016

Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist")

If this message is too spammy, please complain to ixdy.

@bgrant0607
Copy link
Member

add to whitelist

@bgrant0607
Copy link
Member

@adohe Please rebase. We'll try to get this merged.

@k8s-bot
Copy link

k8s-bot commented Feb 6, 2016

GCE e2e test build/test passed for commit 8bb7b3db1320466997f8a8f4753e95dc3dc8b100.

@bgrant0607
Copy link
Member

If #20886 merges first, we'll want to make the same change to ReplicaSet. Or, if this merges first, we'll update #20886.

cc @mqliang @madhusudancs

@adohe-zz
Copy link
Author

adohe-zz commented Feb 9, 2016

it's ok to update the ReplicaSet but I am afraid I have to update this three days later since I am on the new year holiday

@bgrant0607
Copy link
Member

ReplicaSet has merged.

@adohe-zz
Copy link
Author

@bgrant0607 I am still on the holiday and will update this the day after tomorrow sorry about the late.

@bgrant0607
Copy link
Member

@adohe No problem. I was just letting you know.

@adohe-zz adohe-zz force-pushed the kubectl_update_wide branch from 8bb7b3d to 53d4b15 Compare February 14, 2016 08:56
@k8s-github-robot k8s-github-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 14, 2016
@k8s-bot
Copy link

k8s-bot commented Feb 14, 2016

GCE e2e test build/test passed for commit 53d4b15.

@bgrant0607
Copy link
Member

LGTM, thanks!

@bgrant0607 bgrant0607 added lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/backlog Higher priority than priority/awaiting-more-evidence. labels Feb 14, 2016
@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Feb 14, 2016

GCE e2e test build/test passed for commit 53d4b15.

@adohe-zz
Copy link
Author

@bgrant0607 the Jenkins unit/integration just failed. I checked the build-log.txt, and just found hack/test-go.sh failed, but can't get more detailed info. So I rebase and re-run hack/test-go.sh on my CentOS(actually I did run hack/test-go.sh before I push to github), and just found this two errors:

--- FAIL: Test_ExternalID (0.17s)
    mesos_test.go:274: ExternalID should not be able to resolve "mesos3.internal.company.com"
FAIL
FAIL    k8s.io/kubernetes/pkg/cloudprovider/providers/mesos 0.185s

--- FAIL: TestReadConfigData (0.09s)
    helpers_test.go:266: unexpected non-error for http://some.non.existent.foobar
FAIL
FAIL    k8s.io/kubernetes/pkg/kubectl/cmd/util  0.185s

This just blocks this PR get merged.

@bgrant0607
Copy link
Member

@k8s-bot test this issue: #18708

@adohe The unit test failure on jenkins was caused by a flaky test. I just restarted it.

I haven't seen the test failures you posted before. It looks like DNS is resolving names it shouldn't?

@k8s-bot
Copy link

k8s-bot commented Feb 15, 2016

GCE e2e test build/test passed for commit 53d4b15.

@adohe-zz
Copy link
Author

@bgrant0607 yes, I just re-run the unit tests. First I ran hack/test-go.sh under network off, the unit tests will success. Then I ran hack/test-go.sh with network on, I just got an error, some test cases failed:

--- FAIL: Test_ExternalID (0.11s)
    mesos_test.go:274: ExternalID should not be able to resolve "mesos3.internal.company.com"
FAIL
FAIL    k8s.io/kubernetes/pkg/cloudprovider/providers/mesos 0.133s

--- FAIL: TestReadConfigData (0.14s)
    helpers_test.go:266: unexpected non-error for http://some.non.existent.foobar
FAIL
FAIL    k8s.io/kubernetes/pkg/kubectl/cmd/util  0.261s

I think both of these are related with DNS.

@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Feb 15, 2016

GCE e2e test build/test passed for commit 53d4b15.

@k8s-github-robot
Copy link

Automatic merge from submit-queue

k8s-github-robot pushed a commit that referenced this pull request Feb 15, 2016
@k8s-github-robot k8s-github-robot merged commit 94b3c95 into kubernetes:master Feb 15, 2016
@adohe-zz adohe-zz deleted the kubectl_update_wide branch February 17, 2016 13:23
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. priority/backlog Higher priority than priority/awaiting-more-evidence. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants