[glare] Update existing package via CLI causes error with 400 error code

[Anastasia Kuznetsova]

Steps to reproduce:
1. export MURANO_PACKAGES_SERVICE=glance if it is not exported
2. Upload package into glance artifact repository.
murano --debug package-import /var/cache/murano/meta/io.murano.zip
3. Try to update uploading package:
murano package-import --is-public /var/cache/murano/meta/io.murano.zip
Importing package io.murano
Importing package io.murano failed. Package with the same name/classes is already registered.
What do you want to do? (s)kip, (u)pdate, (a)bort
u
Error 400 Bad Request: The server could not comply with the request since it is either malformed or otherwise incorrect.: Unexpected filter property (HTTP 400) occurred while installing package io.murano

The same bug https://bugs.launchpad.net/mos/+bug/1539020 was fixed in MOS. Need to make fix in upstream client too.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/273970

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/273970
Committed: https://git.openstack.org/cgit/openstack/python-muranoclient/commit/?id=386f894879cc74e91ee88896a8d6b6be363d3a46
Submitter: Jenkins
Branch: master

commit 386f894879cc74e91ee88896a8d6b6be363d3a46
Author: Alexander Tivelkov <email address hidden>
Date: Thu Jan 28 13:55:52 2016 +0300

    Fix package delete on update when using Glare

    Since Glare is unable to filter artifacts by "owned' flag, it should
    not be passed as one of list query params.
    Such a call is made when cli shell attempts to delete the conflicting
    package during the package import process.

    Another issue was that durint the package conflict CLI was searching
    for confilicting package by its name only, ignoring version, thus it
    was unable to delete proper package.

    Change-Id: Idc7c7f552576f0c242e90d30cfc1a3f65c581e6d
    Closes-Bug: #1539031