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

TypeError: list_namespaced_deployment() missing 1 required positional argument: 'self' #2162

Open
ramveluru opened this issue Dec 18, 2023 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@ramveluru
Copy link

What happened (please include outputs or screenshots):

Apps = deployments.list_namespaced_deployment(self, namespace="foo")
Traceback (most recent call last):
File "", line 1, in
NameError: name 'self' is not defined

Apps = deployments.list_namespaced_deployment(name="foo*", namespace="bar")
Traceback (most recent call last):
File "", line 1, in
TypeError: list_namespaced_deployment() missing 1 required positional argument: 'self'

@ramveluru ramveluru added the kind/bug Categorizes issue or PR as related to a bug. label Dec 18, 2023
@ghost
Copy link

ghost commented Dec 18, 2023

Can you please explain how to reproduce the bug

Is this code from your application. Shouldn't you call self.deployments.list_namespaced_deployment(namespace = "foo")

@roycaihw
Copy link
Member

/assign @ghost

@k8s-ci-robot
Copy link
Contributor

@roycaihw: GitHub didn't allow me to assign the following users: ghost.

Note that only kubernetes-client members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @ghost

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-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 12, 2024
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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants