Bug 1504207 - Deployments with ceph: public_network and cluster_network don't accept LIST.
Summary: Deployments with ceph: public_network and cluster_network don't accept LIST.
Keywords:
Status: CLOSED DUPLICATE of bug 1503838
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ga
: 12.0 (Pike)
Assignee: Giulio Fidente
QA Contact: Gurenko Alex
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-19 17:19 UTC by Alexander Chuzhoy
Modified: 2017-10-24 11:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-24 11:35:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alexander Chuzhoy 2017-10-19 17:19:02 UTC
Deployments with ceph:  public_network and cluster_network don't accept LIST. 

Environment:
ceph-ansible-3.0.2-1.el7cp.noarch
openstack-tripleo-heat-templates-7.0.2-0.20171007062244.el7ost.noarch
puppet-ceph-2.4.2-0.20170927195215.718a5ff.el7ost.noarch
instack-undercloud-7.4.2-0.20171006021856.el7ost.noarch

Testing a deployment with composable networks, where we have a segregated storage and storagemgmt network for each OSD node -  found that the ceph.conf has only one public/cluster network in it.

[root@overcloud-cephstorage3-0 ~]# cat /etc/ceph/ceph.conf |grep -e network
cluster network = 172.120.4.0/24
public network = 172.120.3.0/24

And these are the subnets defined for StorageMgmt and Storage networks respectively.

The OSD fails to start on storage nodes in this case - it doesn't have an IP in the right subnet.


We need to support a list of subnets. The "working" ceph.conf would list all defined storage and storagemgmt subnets:
[root@overcloud-cephstorage3-0 ~]# cat /etc/ceph/ceph.conf |grep -e network
cluster network = 172.120.4.0/24,172.117.4.0/24,172.118.4.0/24,172.119.4.0/24
public network = 172.120.3.0/24,172.117.3.0/24,172.118.3.0/24,172.119.3.0/24

Comment 2 Giulio Fidente 2017-10-24 11:35:40 UTC
Looks like a duplicate of

*** This bug has been marked as a duplicate of bug 1503838 ***


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