[TestImpact]Creating multiple snapshots fails
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Mirantis OpenStack | Status tracked in 10.0.x | |||||
10.0.x |
Confirmed
|
Medium
|
Unassigned | |||
9.x |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
[root@fuel ~]# fuel --fuel-version
DEPRECATION WARNING: /etc/fuel/
api: '1.0'
astute_sha: 04ebab96d57b0e8
auth_required: true
build_id: 2015-04-29_07-55-19
build_number: '361'
feature_groups:
- mirantis
fuel-library_sha: 0e5b82d24853304
fuel-ostf_sha: b38602c841deaa0
fuelmain_sha: ee112acfdd0f901
nailgun_sha: e660b1c09d7d4d0
openstack_version: 2014.2.2-6.1
production: docker
python-
release: '6.1'
release_versions:
2014.2.2-6.1:
VERSION:
api: '1.0'
astute_sha: 04ebab96d57b0e8
build_id: 2015-04-29_07-55-19
build_number: '361'
feature_
- mirantis
fuel-
fuel-
fuelmain_sha: ee112acfdd0f901
nailgun_sha: e660b1c09d7d4d0
openstack
production: docker
python-
release: '6.1'
Instance "11 Evgeny Sikachev MOS 6.1 ISO #361, HA, CentOS, Neutron GRE, Swift for volumes and images" in QA week spreadsheet.
1. Create a volume
2. Create 70 snapshots for it (using cli)
3. Go to Horizon, select them all and delete
4. (not sure that this step is needed) create 50 more snapshots using cli.
5. Create even more snapshots (I used "for x in `seq 1 20`; do cinder snapshot-create 62e84ae6-
Result: Snapshots never get created
tags: | removed: keystone |
Changed in mos: | |
assignee: | nobody → MOS Cinder (mos-cinder) |
summary: |
- Creating multiple snapshow fails with HTTP 413 + Creating multiple snapshow fails |
summary: |
- Creating multiple snapshow fails + Creating multiple snapshots fails |
summary: |
- Creating multiple snapshot fails with HTTP 413 + Creating multiple snapshot fails |
summary: |
- Creating multiple snapshot fails + Creating multiple snapshots fails |
Changed in mos: | |
status: | Confirmed → Fix Committed |
milestone: | 8.0 → 7.0 |
status: | Fix Committed → Fix Released |
tags: | added: area-mos |
Changed in mos: | |
status: | Confirmed → Won't Fix |
I've removed mention of http 413, because I'll open another bug about it and it was i related.