Bug 1304104
Summary: | Packstack Provides Nova Flavor ID that is Not Big Enough for Service Image | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Dustin Schoenbrun <dschoenb> |
Component: | openstack-packstack | Assignee: | Ivan Chavero <ichavero> |
Status: | CLOSED ERRATA | QA Contact: | yeylon <yeylon> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.0 (Liberty) | CC: | aortega, dschoenb, srevivo, tbarron, yeylon |
Target Milestone: | ga | ||
Target Release: | 8.0 (Liberty) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-packstack-7.0.0-0.13.dev1702.g490e674.el7ost | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-04-07 21:27:28 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
Dustin Schoenbrun
2016-02-02 21:54:49 UTC
If you change the flavor manually the share creation works? If that's so, this does not looks like a bug. Yes, if you update the service_instance_flavor_id value in /etc/manila/manila.conf and then restart the Manila services the share creation will succeed due to the new Nova flavor specified. The issue is more of the fact that the default values provided by Packstack do not work out of the box. If we want to say that this is fine as is, but just requires a configuration change on the part of the user, then we need to be sure we document that somewhere, though I don't think that's the correct solution. One possible solution is to create a new Nova flavor specifically for the Manila Service Instance. The following command will create one equivalent to the Nova Flavor that Devstack uses: nova flavor-create manila_service_flavor 100 128 0 1 Where "manila_service_flavor" is the name of the flavor, 100 is the ID of the flavor, 128 is the amount to RAM to give the instance in MB, 0 is the size of the root disk, which is a special cases where the flavor will use the native base image size as the size of the ephemeral root volume. Essentially it will make the size of the image as big as it needs to be, and 1 is the number of vCPUs to assign to the instance. Hope this helps! Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-0603.html |