| 2017-08-21 05:51:22 |
SU, HAO-CHEN |
bug |
|
|
added bug |
| 2017-08-21 06:55:12 |
SU, HAO-CHEN |
description |
Problems:
Listing event using filter such as 'start_timestamp':
$ openstack event list --filter start_timestamp='2017-08-15 00:00:00'
raises exception:
Operator eq is not supported. Only `ge' operator is available for field
start_timestamp (HTTP 400) (Request-ID: ...
Examination:
The code responsible for this should be 'utils.py'. Around line 32:
url = "q.field=%s&q.op=eq&q.value=%s" % (k, v)
(https://github.com/openstack/python-pankoclient/blob/master/pankoclient/utils.py#L32)
The code sends query with operator 'eq' no matter what the field is.
On the other hand, ceilometer client behaves correctly with commands like:
$ ceilometer event-list -q 'start_timestamp>=2017-08-15 00:00:00'
Possible solution:
Make this part of code that when some specific filter field is given, the operator in
the url query would be the one that matches.
Or we can, on the other hand, change how panko's api server behaves: when the field is a
specific value such as 'start_timestamp', the operator given is ignored and the default
one is forced to be used.
Other issues:
Problems like this related to operator in the filter are somewhat troublesome, since the
format of filter in openstack client must be: <key>=<value>.
And it seems to me that all the clients such as ceilometer-client are going to be removed
except openstack-client. These problems should be resolved after all. |
Version: stable/pike
Problems:
Listing event using filter such as 'start_timestamp':
$ openstack event list --filter start_timestamp='2017-08-15 00:00:00'
raises exception:
Operator eq is not supported. Only `ge' operator is available for field
start_timestamp (HTTP 400) (Request-ID: ...
Examination:
The code responsible for this should be 'utils.py'. Around line 32:
url = "q.field=%s&q.op=eq&q.value=%s" % (k, v)
(https://github.com/openstack/python-pankoclient/blob/master/pankoclient/utils.py#L32)
The code sends query with operator 'eq' no matter what the field is.
On the other hand, ceilometer client behaves correctly with commands like:
$ ceilometer event-list -q 'start_timestamp>=2017-08-15 00:00:00'
Possible solution:
Make this part of code that when some specific filter field is given, the
operator in the url query would be the one that matches.
Or we can, on the other hand, change how panko's api server behaves: when the
field is a specific value such as 'start_timestamp', the operator given is
ignored and the default one is forced to be used.
Other issues:
Problems like this related to operator in the filter are somewhat troublesome,
since the format of filter in openstack client must be: <key>=<value>. And it
seems to me that all the clients such as ceilometer-client are going to be
removed except openstack-client. These problems should be resolved after all. |
|
| 2017-08-21 07:27:03 |
SU, HAO-CHEN |
description |
Version: stable/pike
Problems:
Listing event using filter such as 'start_timestamp':
$ openstack event list --filter start_timestamp='2017-08-15 00:00:00'
raises exception:
Operator eq is not supported. Only `ge' operator is available for field
start_timestamp (HTTP 400) (Request-ID: ...
Examination:
The code responsible for this should be 'utils.py'. Around line 32:
url = "q.field=%s&q.op=eq&q.value=%s" % (k, v)
(https://github.com/openstack/python-pankoclient/blob/master/pankoclient/utils.py#L32)
The code sends query with operator 'eq' no matter what the field is.
On the other hand, ceilometer client behaves correctly with commands like:
$ ceilometer event-list -q 'start_timestamp>=2017-08-15 00:00:00'
Possible solution:
Make this part of code that when some specific filter field is given, the
operator in the url query would be the one that matches.
Or we can, on the other hand, change how panko's api server behaves: when the
field is a specific value such as 'start_timestamp', the operator given is
ignored and the default one is forced to be used.
Other issues:
Problems like this related to operator in the filter are somewhat troublesome,
since the format of filter in openstack client must be: <key>=<value>. And it
seems to me that all the clients such as ceilometer-client are going to be
removed except openstack-client. These problems should be resolved after all. |
Problems:
Listing event using filter such as 'start_timestamp':
$ openstack event list --filter start_timestamp='2017-08-15 00:00:00'
raises exception:
Operator eq is not supported. Only `ge' operator is available for field
start_timestamp (HTTP 400) (Request-ID: ...
Examination:
The code responsible for this should be 'utils.py'. Around line 32:
url = "q.field=%s&q.op=eq&q.value=%s" % (k, v)
(https://github.com/openstack/python-pankoclient/blob/master/pankoclient/utils.py#L32)
The code sends query with operator 'eq' no matter what the field is.
On the other hand, ceilometer client behaves correctly with commands like:
$ ceilometer event-list -q 'start_timestamp>=2017-08-15 00:00:00'
Possible solution:
Make this part of code that when some specific filter field is given, the
operator in the url query would be the one that matches.
Or we can, on the other hand, change how panko's api server behaves: when the
field is a specific value such as 'start_timestamp', the operator given is
ignored and the default one is forced to be used.
Other issues:
Problems like this related to operator in the filter are somewhat troublesome,
since the format of filter in openstack client must be: <key>=<value>. And it
seems to me that all the clients such as ceilometer-client are going to be
removed except openstack-client. These problems should be resolved after all. |
|
| 2018-03-15 13:47:43 |
Vadym Markov |
python-pankoclient: status |
New |
Fix Released |
|
