[Horizon] Deletion of pseudo-folder with nested object

Bug #1461877 reported by Kyrylo Romanenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Invalid
Medium
MOS Horizon

Bug Description

Deletion of pseudo-folder with nested object performs wrong behavior.

1. Login to Horizon as admin
2. Navigate to Project -> Object Store -> Containers
3. Create Container (Private or Public).
4. Open this Container.
5. Create Pseudo-folder by name "folder".
6. Go into folder.
7. Upload Object (some file).
Now i see properties of container in Containers table:

Object Count: 2
Size: 127.1 KB
Access: Private

That means that 1 object is pseudo-folder and 1 is file in it.

8. Go up from folder.
9. Click "Delete Object" button of pseudo-folder.

Actual:
I see green Pop-Up "Success: Deleted Object: folder"
Also i see changed properties of container in Containers table:

Object Count: 1
Size: 127.1 KB
Access: Private

But folder and nested object both remained available.

Expected:
To see red pop-up "Error: Unable to delete object: folder"

And some additional details:
10. Go back into survived pseudo-folder.
11. Delete nested object.

Result: Nested object and containing pseudo-folder are removed both.

Juno on Ubuntu 14.04.1
Neutron VLAN
1 Cinder with LVM over iSCSI
1 Controller
1 Compute

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "6.1"
  openstack_version: "2014.2.2-6.1"
  api: "1.0"
  build_number: "500"
  build_id: "2015-06-03_04-06-47"
  nailgun_sha: "3830bdcb28ec050eed399fe782cc3dd5fbf31bde"
  python-fuelclient_sha: "4fc55db0265bbf39c369df398b9dc7d6469ba13b"
  astute_sha: "cbae24e9904be2ff8d1d49c0c48d1bdc33574228"
  fuel-library_sha: "938f033a5da90aca0c24c89c995cf01707d746d2"
  fuel-ostf_sha: "f899e16c4ce9a60f94e7128ecde1324ea41d09d4"
  fuelmain_sha: "bcc909ffc5dd5156ba54cae348b6a07c1b607b24"

Tags: horizon
Changed in mos:
importance: High → Medium
milestone: 6.1 → 7.0
Changed in mos:
status: New → Confirmed
Revision history for this message
Vlad Okhrimenko (vokhrimenko) wrote :

I can't reproduce on MOS 7.0

Changed in mos:
status: Confirmed → Invalid
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.