Unable to create or delete images in glance after application of last maintenance update on MOS 5.1.1

Bug #1585213 reported by Sergii Rizvan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Won't Fix
High
MOS Maintenance

Bug Description

Detailed bug description:
 After application of last maintenance update on MOS 5.1.1 there is unable to create or delete images in glance:
CLI glance image-create: http://paste.openstack.org/show/498604/
CLI glance image-delete: http://paste.openstack.org/show/498605/
(Glance use Swift backend)

Steps to reproduce:
 1. Deploy MOS 5.1.1 environment
 2. Apply maintenance update using this manual: https://docs.mirantis.com/openstack/fuel/fuel-5.1/release-notes.html#how-to-update-the-product
 3. Login on Controller node and download some qcow2 image, for example:
    wget https://download.fedoraproject.org/pub/fedora/linux/releases/23/Cloud/x86_64/Images/Fedora-Cloud-Base-23-20151030.x86_64.qcow2
 4. Execute glance image-create command:
    glance --debug image-create --name fedora --file Fedora-Cloud-Base-23-20151030.x86_64.qcow2 --disk-format qcow2 --container-format bare --progress
  Now you may see 500 error from API.
 5. Execute glance image-delete command:
    glance --debug image-delete TestVM
  Now you may see 500 error from API.

Expected results:
 After application of maintenance update we can succsessfully create and delete glance images.

Actual result:
 Creating or deleting glance images ends up with 500 error from the API.

Reproducibility:
 100% reproducibility

Description of the environment:
- Operation system: Ubuntu 12.04
- Versions of components: MOS 5.1.1
- Reference architecture: 1 controller node, 2 compute nodes
- Network model: Neutron with VLAN segmentation
- Related projects installed: Glance with Swift backend

Revision history for this message
Sergii Rizvan (srizvan) wrote :
description: updated
Revision history for this message
Sergii Rizvan (srizvan) wrote :
Changed in mos:
status: New → Confirmed
Changed in mos:
milestone: 5.1.1-mu-3 → 5.1.1-updates
Revision history for this message
Alexey Stupnikov (astupnikov) wrote :

MOS 5.1.1 is no longer supported, moving to Won't Fix.

Changed in mos:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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