Deployment on three node cluster using oVirt HCI wizard. I think this is a bug where it needs to do either a pre-flight name length validation, or increase valid field length.
I avoid using /dev/sd# as those can change. And the wizard allows for this change to a more explicit devices Ex: /dev/mapper/Samsung_SSD_850_PRO_512GB_S250NXAGA15787L Error: TASK [gluster.infra/roles/backend_setup : Create a LV thinpool for similar device types] *** task path: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/thin_pool_create.yml:239 failed: [thorst.penguinpages.local] (item={'vgname': 'gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L', 'thinpoolname': 'gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L', 'poolmetadatasize': '3G'}) => {"ansible_loop_var": "item", "changed": false, "err": " Full LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tdata\" is too long.\n Full LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tdata\" is too long.\n Full LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tdata\" is too long.\n Full LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tdata\" is too long.\n Full LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tdata\" is too long.\n Full LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tmeta\" is too long.\n Internal error: LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tmeta\" length 130 is not supported.\n Internal error: LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tdata\" length 130 is not supported.\n Internal error: LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tmeta\" length 130 is not supported.\n Internal error: LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tdata\" length 130 is not supported.\n", "item": {"poolmetadatasize": "3G", "thinpoolname": "gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L", "vgname": "gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L"}, "msg": "Creating logical volume 'None' failed", "rc": 5} failed: [medusast.penguinpages.local] (item={'vgname': 'gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306', 'thinpoolname': 'gluster_thinpool_gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306', 'poolmetadatasize': '3G'}) => {"ansible_loop_var": "item", "changed": false, "err": " Internal error: LV name \"gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306/gluster_thinpool_gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306\" length 130 is not supported.\n", "item": {"poolmetadatasize": "3G", "thinpoolname": "gluster_thinpool_gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306", "vgname": "gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306"}, "msg": "Creating logical volume 'None' failed", "rc": 5} changed: [odinst.penguinpages.local] => (item={'vgname': 'gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137', 'thinpoolname': 'gluster_thinpool_gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137', 'poolmetadatasize': '3G'}) => {"ansible_loop_var": "item", "changed": true, "item": {"poolmetadatasize": "3G", "thinpoolname": "gluster_thinpool_gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137", "vgname": "gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137"}, "msg": ""} I will revert back to /dev/sd# for now... but this should be cleaned up. Attached is YAML file for deployment of cluster -- p <jeremey.w...@gmail.com>enguinpages
hc_nodes: hosts: thorst.penguinpages.local: gluster_infra_volume_groups: - vgname: gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L pvname: /dev/mapper/vdo_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L gluster_infra_mount_devices: - path: /gluster_bricks/engine lvname: gluster_lv_engine vgname: gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L - path: /gluster_bricks/data lvname: gluster_lv_data vgname: gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L - path: /gluster_bricks/vmstore lvname: gluster_lv_vmstore vgname: gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L gluster_infra_vdo: - name: vdo_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L device: /dev/mapper/Samsung_SSD_850_PRO_512GB_S250NXAGA15787L slabsize: 32G logicalsize: 11000G blockmapcachesize: 128M emulate512: 'off' writepolicy: auto maxDiscardSize: 16M gluster_infra_thick_lvs: - vgname: gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L lvname: gluster_lv_engine size: 1000G gluster_infra_thinpools: - vgname: gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L thinpoolname: >- gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L poolmetadatasize: 3G gluster_infra_lv_logicalvols: - vgname: gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L thinpool: >- gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L lvname: gluster_lv_data lvsize: 5000G - vgname: gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L thinpool: >- gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L lvname: gluster_lv_vmstore lvsize: 5000G odinst.penguinpages.local: gluster_infra_volume_groups: - vgname: gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137 pvname: /dev/mapper/vdo_Micron_1100_MTFDDAV512TBN_17401F699137 gluster_infra_mount_devices: - path: /gluster_bricks/engine lvname: gluster_lv_engine vgname: gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137 - path: /gluster_bricks/data lvname: gluster_lv_data vgname: gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137 - path: /gluster_bricks/vmstore lvname: gluster_lv_vmstore vgname: gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137 gluster_infra_vdo: - name: vdo_Micron_1100_MTFDDAV512TBN_17401F699137 device: /dev/mapper/Micron_1100_MTFDDAV512TBN_17401F699137 slabsize: 32G logicalsize: 11000G blockmapcachesize: 128M emulate512: 'off' writepolicy: auto maxDiscardSize: 16M gluster_infra_thick_lvs: - vgname: gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137 lvname: gluster_lv_engine size: 1000G gluster_infra_thinpools: - vgname: gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137 thinpoolname: >- gluster_thinpool_gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137 poolmetadatasize: 3G gluster_infra_lv_logicalvols: - vgname: gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137 thinpool: >- gluster_thinpool_gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137 lvname: gluster_lv_data lvsize: 5000G - vgname: gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137 thinpool: >- gluster_thinpool_gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137 lvname: gluster_lv_vmstore lvsize: 5000G medusast.penguinpages.local: gluster_infra_volume_groups: - vgname: gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 pvname: /dev/mapper/vdo_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 gluster_infra_mount_devices: - path: /gluster_bricks/engine lvname: gluster_lv_engine vgname: gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 - path: /gluster_bricks/data lvname: gluster_lv_data vgname: gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 - path: /gluster_bricks/vmstore lvname: gluster_lv_vmstore vgname: gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 gluster_infra_vdo: - name: vdo_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 device: /dev/mapper/SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 slabsize: 32G logicalsize: 11000G blockmapcachesize: 128M emulate512: 'off' writepolicy: auto maxDiscardSize: 16M gluster_infra_thick_lvs: - vgname: gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 lvname: gluster_lv_engine size: 1000G gluster_infra_thinpools: - vgname: gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 thinpoolname: >- gluster_thinpool_gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 poolmetadatasize: 3G gluster_infra_lv_logicalvols: - vgname: gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 thinpool: >- gluster_thinpool_gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 lvname: gluster_lv_data lvsize: 5000G - vgname: gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 thinpool: >- gluster_thinpool_gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 lvname: gluster_lv_vmstore lvsize: 5000G vars: gluster_infra_disktype: JBOD gluster_set_selinux_labels: true gluster_infra_fw_ports: - 2049/tcp - 54321/tcp - 5900/tcp - 5900-6923/tcp - 5666/tcp - 16514/tcp gluster_infra_fw_permanent: true gluster_infra_fw_state: enabled gluster_infra_fw_zone: public gluster_infra_fw_services: - glusterfs gluster_features_force_varlogsizecheck: false cluster_nodes: - thorst.penguinpages.local - odinst.penguinpages.local - medusast.penguinpages.local gluster_features_hci_cluster: '{{ cluster_nodes }}' gluster_features_hci_volumes: - volname: engine brick: /gluster_bricks/engine/engine arbiter: 0 - volname: data brick: /gluster_bricks/data/data arbiter: 0 - volname: vmstore brick: /gluster_bricks/vmstore/vmstore arbiter: 0
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: