Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1304224 - rhel-osp-director: 7.3 + 3 ceph nodes - the glance images, vms, cinder volumes are not created on the ceph nodes.
rhel-osp-director: 7.3 + 3 ceph nodes - the glance images, vms, cinder volum...
Status: CLOSED NOTABUG
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
high Severity unspecified
: y3
: 7.0 (Kilo)
Assigned To: Giulio Fidente
yeylon@redhat.com
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-03 00:08 EST by Alexander Chuzhoy
Modified: 2016-04-18 03:00 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-02-03 10:38:12 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Alexander Chuzhoy 2016-02-03 00:08:27 EST
rhel-osp-director: 7.3 (with ipv6 and ssl) + 3 ceph nodes - the glance images, vms, cinder volumes are not created on the ceph nodes.

Environment:
instack-undercloud-2.1.2-37.el7ost.noarch
openstack-tripleo-heat-templates-0.8.6-112.el7ost.noarch
openstack-cinder-2015.1.2-5.el7ost.noarch
openstack-puppet-modules-2015.1.8-45.el7ost.noarch
openstack-nova-common-2015.1.2-13.el7ost.noarch

Steps to reproduce:
1. Deploy 7.3 HA overcloud with ipv6 and ssl 
2. create cinder volumes, glance images, launch an instance.

Result:
The respective ceph  volumes (volumes, images, vms) aren't populated.
The instance use non-shared storage.
Cinder volumes are created on controllers and it's not possible to attach cinder volumes to instances.


Expected results:
The glance images,cinder volumes and vms storage should be created on the ceph nodes.
Comment 1 Jaromir Coufal 2016-02-03 05:12:06 EST
Sasha, can you provide more information for investigation (logs, etc)? Thanks
Comment 3 Giulio Fidente 2016-02-03 10:38:12 EST
The configuration looks correct when the storage-environment.yaml file is passed.

Note You need to log in before you can comment on or make changes to this bug.