Skip to content

cinder segmentation fault issue  #23

@StanOnix

Description

@StanOnix

hi guys, I've an issue concerning cinder on line 458. I can't figure out the solution for this. Anyone can help ?
`
==> default: + is_service_enabled c-api
==> default: ++ set +o
==> default: ++ grep xtrace
==> default: + local 'xtrace=set -o xtrace'
==> default: + set +o xtrace
==> default: + return 0
==> default: + is_service_enabled tls-proxy
==> default: ++ grep xtrace
==> default: ++ set +o
==> default: + local 'xtrace=set -o xtrace'
==> default: + set +o xtrace
==> default: + return 1
==> default: + create_volume_types
==> default: + is_service_enabled c-api
==> default: ++ set +o
==> default: ++ grep xtrace
==> default: + local 'xtrace=set -o xtrace'
==> default: + set +o xtrace
==> default: + return 0
==> default: + [[ -n lvm:lvmdriver-1 ]]
==> default: + local be be_name be_type
==> default: + for be in '${CINDER_ENABLED_BACKENDS//,/ }'
==> default: + be_type=lvm
==> default: + be_name=lvmdriver-1
==> default: + cinder type-create lvmdriver-1
==> default: /home/vagrant/devstack/lib/cinder: line 458: 20727 Segmentation fault (core dumped) cinder type-create ${be_name}
==> default: ++ err_trap
==> default: ++ local r=139
==> default: ++ set +o xtrace
==> default: Error on exit
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

`

Thank you in advance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions