Error manage volume

[Sergei Chipiga]

Env:
- mos9.0#278
- Ceph RBD for volumes (Cinder)
- Ceph RadosGW for objects (Swift API)
- Ceph RBD for ephemeral volumes (Nova)
- Ceph RBD for images (Glance)

horizon url: http://172.16.57.68/

Preconditions:
- There is one volume in openstack, that is available via horizon dashboard

Steps:
- Login as admin
- Go to Admin -> Volumes
- Select volume via checkbox
- Click button "Manage volume"
- Fill required fields
- Click button "Manage"

Expected result:
New managed volume is present at volumes page

Actual result:
New managed volume is present but has status "Error" and size 0GiB

And it's not possible to delete such error volume if in managing form host was set to invalid value, like "test", "proba".

[Timur Nurlygayanov (tnurlygayanov)]

It looks like Cinder issue, not just Horizon, Cinder team, could you please take a look?

[Roman Podoliaka (rpodolyaka)]

Cinder team, please take a look at this one.

[Sergei Chipiga (schipiga)]

I suppose it's cinder bug, because I reproduce that with cli client:

root@node-1:/var/log/horizon# cinder manage node-1.test.domain.local#RBD-backend schipiga-volume
+--------------------------------+--------------------------------------+
| Property | Value |
+--------------------------------+--------------------------------------+
| attachments | [] |
| availability_zone | nova |
| bootable | false |
| consistencygroup_id | None |
| created_at | 2016-05-06T15:19:21.000000 |
| description | None |
| encrypted | False |
| id | b6c34d9c-c79f-4d1f-8390-220022565a7d |
| metadata | {} |
| migration_status | None |
| multiattach | False |
| name | None |
| os-vol-host-attr:host | node-1.test.domain.local#RBD-backend |
| os-vol-mig-status-attr:migstat | None |
| os-vol-mig-status-attr:name_id | None |
| os-vol-tenant-attr:tenant_id | 25998cc47a094b4984eafb88a35ecd49 |
| replication_status | None |
| size | 0 |
| snapshot_id | None |
| source_volid | None |
| status | creating |
| updated_at | None |
| user_id | 136b15c91f54413e888297ac9d0afdd5 |
| volume_type | None |
+--------------------------------+--------------------------------------+
root@node-1:/var/log/horizon# cinder show b6c34d9c-c79f-4d1f-8390-220022565a7d
+--------------------------------+--------------------------------------+
| Property | Value |
+--------------------------------+--------------------------------------+
| attachments | [] |
| availability_zone | nova |
| bootable | false |
| consistencygroup_id | None |
| created_at | 2016-05-06T15:19:21.000000 |
| description | None |
| encrypted | False |
| id | b6c34d9c-c79f-4d1f-8390-220022565a7d |
| metadata | {} ...

[Sergei Chipiga (schipiga)]

seems it's because of cinder service-list shows:
cinder-scheduler | node-1.test.domain.local | nova | enabled | down | 2016-05-06T15:23:06.000000

It can be a result of bug https://bugs.launchpad.net/fuel/+bug/1568803

[Ivan Kolodyazhny (e0ne)]

Bug #1568803 is not related to this issue

[Yuriy Nesenenko (ynesenenko)]

The case for CLI is a completely different story, because you specified an existing host. And after you got the volume with status "error" you can simply delete it. This is a normal Cinder behavior.
http://paste.openstack.org/show/496358/
Unlike the previous story with actions through Horizon, where you entered invalid host name, volume with invalid host can create though UI but can not be done through CLI.
root@node-1:~# cinder manage proba e0a353b2-8460-4e29-8fdd-d3b97d97fa4e
ERROR: Service not found. (HTTP 404) (Request-ID: req-7f30dbb1-d34f-483f-ad90-2bdafa48737c)

[Fuel Devops McRobotson (fuel-devops-robot)]

Fix proposed to branch: 9.0/mitaka
Change author: Yuriy Nesenenko <email address hidden>
Review: https://review.fuel-infra.org/20437

[Fuel Devops McRobotson (fuel-devops-robot)]

Reviewed: https://review.fuel-infra.org/20437
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka

Commit: 79ece74113527103a6d17d84ae1e9a6a4dc1bc86
Author: Yuriy Nesenenko <email address hidden>
Date: Tue May 10 09:45:06 2016

Manage existing volume with invalid host

A volume with invalid host is created when manage existing
volume with actions via Horizon dashboard, where it's entered
invalid host name. This patch fixes it, that is, it's not allow
to create a volume with invalid host.

Change-Id: Idd32f06c2f6c14813e21c83fde8671c41eb03653
Closes-Bug: #1578647

[Oleksiy Butenko (obutenko)]

verified on:
cat /etc/fuel_build_id:
 404
cat /etc/fuel_build_number:
 404
cat /etc/fuel_release:
 9.0
cat /etc/fuel_openstack_version:
 mitaka-9.0
rpm -qa | egrep 'fuel|astute|network-checker|nailgun|packetary|shotgun':
 fuel-release-9.0.0-1.mos6347.noarch
 fuel-bootstrap-cli-9.0.0-1.mos283.noarch
 fuel-migrate-9.0.0-1.mos8391.noarch
 rubygem-astute-9.0.0-1.mos746.noarch
 fuel-provisioning-scripts-9.0.0-1.mos8709.noarch
 network-checker-9.0.0-1.mos72.x86_64
 fuel-mirror-9.0.0-1.mos136.noarch
 fuel-openstack-metadata-9.0.0-1.mos8709.noarch
 fuel-notify-9.0.0-1.mos8391.noarch
 nailgun-mcagents-9.0.0-1.mos746.noarch
 python-fuelclient-9.0.0-1.mos316.noarch
 fuelmenu-9.0.0-1.mos270.noarch
 fuel-9.0.0-1.mos6347.noarch
 fuel-utils-9.0.0-1.mos8391.noarch
 fuel-setup-9.0.0-1.mos6347.noarch
 fuel-library9.0-9.0.0-1.mos8391.noarch
 shotgun-9.0.0-1.mos90.noarch
 fuel-agent-9.0.0-1.mos283.noarch
 fuel-ui-9.0.0-1.mos2702.noarch
 fuel-ostf-9.0.0-1.mos934.noarch
 fuel-misc-9.0.0-1.mos8391.noarch
 python-packetary-9.0.0-1.mos136.noarch
 fuel-nailgun-9.0.0-1.mos8709.noarch
[root@nailgun ~]#