CLI client does not honor --is-public when working with glare
Bug #1584838 reported by
Kirill Zaitsev
This bug report is a duplicate of:
Bug #1585584: [Glare] Glare v0.1 is unable to create a public artifact draft.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-muranoclient |
Invalid
|
High
|
Valerii Kovalchuk | ||
| Mitaka |
Invalid
|
High
|
Valerii Kovalchuk | ||
| Newton |
Invalid
|
High
|
Valerii Kovalchuk | ||
Bug Description
To reproduce:
import any package, while specifying
murano --murano-
expected result: the packages imported are public.
actual result: the packages are left private.
| summary: |
- CLI client does not honors --is-public when working with glare + CLI client does not honor --is-public when working with glare |
Revision history for this message
| Valerii Kovalchuk (vakovalchuk) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to python-muranoclient (master) | #2 |
| Changed in python-muranoclient: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on python-muranoclient (master) | #3 |
Revision history for this message
| Valerii Kovalchuk (vakovalchuk) wrote | #4 |
To post a comment you must log in.
Looks like it is not the problem in muranoclient code. The difference is made here https:/
The input of this call to glanceclient is correct, and the result already contains visibility = private