Mirantis OpenStack

updating associations fails in horizon (Metadata Definitions)

  1. Series 10.0.x
  2. Bug #1541573
Bug #1541573 reported by Alexander Petrov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Status tracked in 10.0.x
10.0.x
Confirmed
Low
Alexander Petrov
Mirantis OpenStack 10.0
8.0.x
Won't Fix
Low
MOS Horizon
Mirantis OpenStack 8.0
9.x
Invalid
Low
Alexander Petrov
Mirantis OpenStack 9.0

Bug Description

MOS 8.0 ISO 512

Steps to reproduce:

Update Associations: Note can only be done when namespace is not protected
- Choose a metadata definition
- Chose Update associations action
- Associate with all resource types and add a prefix
- Save
- Open and ensure all resource types are selected and have the prefix

Actual result:
Error: Error updating resource types for namespace OS::Compute::CPUPinning.

See original description
Alexander Petrov (apetrov-n)
Changed in mos:
milestone: none → 8.0
Roman Podoliaka (rpodolyaka)
tags: added: area-horizon
Changed in mos:
status: New → Won't Fix
importance: Undecided → Low
assignee: nobody → MOS Horizon (mos-horizon)
Revision history for this message
Sergei Chipiga (schipiga) wrote :

[Alexander Petrov]
Could you please describe steps a bit clearly? In current I can't understand how to reproduce the problem.

Revision history for this message
Alexander Petrov (apetrov-n) wrote :

to Sergei Chipiga (schipiga)

Open Metadata Definition page in Horison and perform Import Namespaces.
The make direct input the next text:

{
    "namespace": "1A_TestNamespace",
    "display_name": "1A_TestNamespace",
    "description": "Description for TestNamespace",
    "resource_type_associations": [
        {
            "name": "OS::Nova::Flavor"
        },
        {
            "name": "OS::Glance::Image"
        }
    ],
    "properties": {
        "prop1": {
            "default": "20",
            "type": "integer",
            "description": "More info here",
            "title": "My property1"
        }
    }
}

after that follow Steps to reproduce.

By the way, I have tried on MOS9 #188 and it is not reproduced.
So I am setting the issue status for mos9 as INVALID.

description: updated
Revision history for this message
Dina Belova (dbelova) wrote :

Added move-to-10.0 tag due to the fact bug was transferred from 9.0 to 10.0

tags: added: move-to-10.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.