Deployed Ceph fails when using custom network name
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
John Fulton |
Bug Description
Deployed Ceph fails when using custom network name
During deployment of Ceph the following error I seen:
2021-11-08 15:15:30.838746 | 244201c6-
2021-11-08 15:15:30.906178 | 244201c6-
"changed": false,
"msg": "Both Storage and StorageMgmt should be in ['StorageCloud0', 'StorageMgmtClo
}
In roles_data.yaml my ceph nodes had the following entry:
networks:
Storage:
subnet: storage_
StorageMgmt:
subnet: storage_
Which differs from the default:
networks:
Storage:
subnet: storage_subnet
StorageMgmt:
subnet: storage_mgmt_subnet
In the config-download directory my tripleo-
vars:
networks_all:
- StorageCloud0
- StorageMgmtCloud0
networks_lower:
StorageCl
StorageMg
ctlplane: ctlplane
role_networks:
- StorageCloud0
- ctlplane
- StorageMgmtCloud0
Later in the inventory each host has its own variable map:
CephAll:
hosts:
...
oc0-ceph-2:
...
storage_
storage_
storage_
storage_
As it's valid for a user to customize these parameters and the cusotmized
roles_data.yaml is passed when the command is run with --roles-data. The
playbook should be updated handle this and use the customized network name.
description: | updated |
Related fix proposed to branch: master /review. opendev. org/c/openstack /python- tripleoclient/ +/817131
Review: https:/