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

Output of kubectl describe pod formats incorrectly #112621

Closed
barrettj12 opened this issue Sep 21, 2022 · 11 comments
Closed

Output of kubectl describe pod formats incorrectly #112621

barrettj12 opened this issue Sep 21, 2022 · 11 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.

Comments

@barrettj12
Copy link

What happened:
Output of kubectl describe pod formats incorrectly.

$ microk8s kubectl describe pod -n controller-c2 controller-0
...
Events:
  Type     Reason            Age   From               Message
  ----     ------            ----  ----               -------
  Warning  FailedScheduling  79s   default-scheduler  running PreFilter plugin "VolumeBinding": %!!(MISSING)w(<nil>)
$

Probably a bug in the formatting code.

What you expected to happen:
Display the output more nicely, e.g.

running PreFilter plugin "VolumeBinding": nil

How to reproduce it (as minimally and precisely as possible):

TBD

Anything else we need to know?:

Environment:

  • Kubernetes client and server versions (use kubectl version):
    $ microk8s kubectl version
    WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  
    Use --output=yaml|json to get the full version.
    Client Version: version.Info{Major:"1", Minor:"24+", GitVersion:"v1.24.4-2+2f38f78fa07274", 
    GitCommit:"2f38f78fa07274a290eb3b5802e82b1de6f70fa4", GitTreeState:"clean", BuildDate:"2022-08-22T10:27:57Z", GoVersion:"go1.18.5", Compiler:"gc", Platform:"linux/amd64"}
    Kustomize Version: v4.5.4
    Server Version: version.Info{Major:"1", Minor:"24+", GitVersion:"v1.24.4-2+2f38f78fa07274", 
    GitCommit:"2f38f78fa07274a290eb3b5802e82b1de6f70fa4", GitTreeState:"clean", BuildDate:"2022-08-22T10:25:23Z", GoVersion:"go1.18.5", Compiler:"gc", Platform:"linux/amd64"}
  • Cloud provider or hardware configuration: running microk8s on local machine
  • OS (e.g: cat /etc/os-release):
    $ cat /etc/os-release
    NAME="Ubuntu"
    VERSION="20.04.4 LTS (Focal Fossa)"
    ID=ubuntu
    ID_LIKE=debian
    PRETTY_NAME="Ubuntu 20.04.4 LTS"
    VERSION_ID="20.04"
    HOME_URL="https://www.ubuntu.com/"
    SUPPORT_URL="https://help.ubuntu.com/"
    BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
    PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
    VERSION_CODENAME=focal
    UBUNTU_CODENAME=focal
@barrettj12 barrettj12 added the kind/bug Categorizes issue or PR as related to a bug. label Sep 21, 2022
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Sep 21, 2022
@k8s-ci-robot
Copy link
Contributor

@barrettj12: This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ardaguclu
Copy link
Member

kubectl describe lists events gotten from apiserver and it seems that message has a problem.

I think that is because of this line

return nil, framework.AsStatus(fmt.Errorf("running PreFilter plugin %q: %w", pl.Name(), s.AsError())).WithFailedPlugin(pl.Name())
does not handle empty cases.

/transfer kubernetes
/sig scheduler

@k8s-ci-robot
Copy link
Contributor

@ardaguclu: The label(s) sig/scheduler cannot be applied, because the repository doesn't have them.

In response to this:

kubectl describe lists events gotten from apiserver and it seems that message has a problem.

I think that is because of this line

return nil, framework.AsStatus(fmt.Errorf("running PreFilter plugin %q: %w", pl.Name(), s.AsError())).WithFailedPlugin(pl.Name())
does not handle empty cases.

/transfer kubernetes
/sig scheduler

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot transferred this issue from kubernetes/kubectl Sep 21, 2022
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Sep 21, 2022
@ardaguclu
Copy link
Member

/sig scheduler

@k8s-ci-robot
Copy link
Contributor

@ardaguclu: The label(s) sig/scheduler cannot be applied, because the repository doesn't have them.

In response to this:

/sig scheduler

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ardaguclu
Copy link
Member

/sig scheduling

@k8s-ci-robot k8s-ci-robot added sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Sep 21, 2022
@HirazawaUi
Copy link
Contributor

I think I fixed the bug, waiting for the reviewer to review the PR, hope it helps you

@sanposhiho
Copy link
Member

I believe this bug has been already fixed in #112029.

@HirazawaUi
Copy link
Contributor

I believe this bug has been already fixed in #112029.

Thanks for the reminder, I have closed my PR

@kerthcet
Copy link
Member

Since it's not a critical bug just some outputs, no need to cherry pick, close then.
/close

@k8s-ci-robot
Copy link
Contributor

@kerthcet: Closing this issue.

In response to this:

Since it's not a critical bug just some outputs, no need to cherry pick, close then.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants