Bug 1259354
Summary: | When pre-creating a vg of cinder-volumes packstack fails with an error | ||
---|---|---|---|
Product: | [Community] RDO | Reporter: | Phill. Whiteside <phillw> |
Component: | openstack-packstack | Assignee: | Ivan Chavero <ichavero> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | yeylon <yeylon> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | Kilo | CC: | aortega, derekh, eharney, ichavero, phillw, srevivo, yeylon |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | Kilo | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-30 23:09:09 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Phill. Whiteside
2015-09-02 12:50:27 UTC
asked for log file... as unsure, have uploaded everything from /var/tmp/packstack to http://phillw.net/20150902-154340-iMzKI_/ As asked, I reinstalled the server and created a VG cinder-volumes and then an answer.txt file. I altered CONFIG_CINDER_VOLUMES_CREATE --cinder-volumes-create y to n as requested and the install using the command [root@localhost ~]# packstack --answer-file=./answers.txt did not error out. creating a new volume of 100 GB worked okay, so the initial limit of 20GB has been resolved. Tested --allinone with packstack from source and didn't reproduce the problem, i'm gonna test using current kilo package: openstack-packstack-2015.1-0.11.dev1616.g5526c38.fc23 If the problem persists you can set CONFIG_CINDER_VOLUMES_CREATE=n so you can create manually the volume withouht any problem. is this a desired solution? Sorry i missed to mention that in comment 2 the OP talks about this solution so i closing this bug. The bug is not fixed, what we have is a workaround. If you do not know of this link, you cannot pass the 20GB limit. The release notes need editing, or the bug still needs fixing. Fixing the bug is always the preferred way as we know people do not read the release notes :D |