openshift/openshift-client-python

Error error: invalid resource name \"pod/xxxx\": [may not contain '/']

Closed this issue · 6 comments

tiokouBrice commented

Hello,
i find and Error when using the follow command:

  • oc.selector('pod/mypodname').object().execute(xxx)

i have the error:
"err": "error: invalid resource name "pod/xxxx": [may not contain '/']\n",

when looking the reason:
i find an error in the openshift/apiobject.py
in the fonction : def execute(.....)

you have to change the parameter qname() to name()

have a nice day..

bradmwilliams commented

@tiokouBrice Can you check which version you are running?

I am using version 1.0.17 and do not see a problem with this logic:

#!/usr/bin/env python

import openshift as oc

if __name__ == '__main__':
    with oc.client_host():
        with oc.timeout(60 * 30):
            with oc.project("my-project"):
                result = oc.selector('pod/chatterbox').object().execute(['echo', 'hello world!'])
                print(result.out())
                exit(0)
bradmwilliams commented

Can you provide a more complete example of the logic that's producing this failure?

openshift-bot commented

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

openshift-bot commented

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci commented

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/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.