Skip to content
This repository was archived by the owner on Mar 19, 2021. It is now read-only.
This repository was archived by the owner on Mar 19, 2021. It is now read-only.

Command 'status job=cutejob returns error' #9

@IvanBayan

Description

@IvanBayan

Looks like i found another bug, there is output from bconsole:

*status job=oracle_weekly_ow-backup03
Job "oracle_weekly_ow-backup03" is not running.

Python:

In [136]: console.call("status job=oracle_weekly_ow-backup03")
Out[136]: 
{u'error': {u'code': 1,
  u'data': {u'messages': {u'error': [u'Job "oracle_weekly_ow-backup03" is not running.\n']},
   u'result': {}},
  u'message': u'failed'},
 u'id': None,
 u'jsonrpc': u'2.0'}

Am i wrong and it's expected behavior?

PS
I found another strange behavior, bconsole:

*.status dir current
1000 OK .status

Python:

In [137]: console.call(".status dir current")
Out[137]: {}

Should i open another one issue for that?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions