No way to mention flavor details for KB proxy server

Bug #1766372 reported by chinasubbareddy mallavarapu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KloudBuster
Fix Released
Medium
chinasubbareddy mallavarapu

Bug Description

While setting kloudbuster for openstack with ceph as backend , we are having issues to launch KB proxy node as flavor says root disk as zero but image expects more than 3GB.

there is no way we can mention flavor details for KB proxy node hence running tests failing to launch KB proxy vm with below error .

Error: Failed to perform requested operation on instance "vm2", the instance has an error status: Please try again later [Error: Build of instance df6816d2-f39b-4ed3-9175-60dd9b075f69 aborted: Volume c2ea0d78-5cb3-4a61-ad4d-c155e1f5b0e6 did not finish being created even after we waited 12 seconds or 5 attempts. And its status is error.].

by default if flavor has zero as root disk , it will try to create 1GB volume and that will not be sufficient for KB proxy vm to launch.

Revision history for this message
Alec Hothan (ahothan) wrote :

The flavor for the proxy VM is hardcoded and set to

                proxy_flavor = {
                    "vcpus": 1,
                    "ram": 2048,
                    "disk": 0,
                    "ephemeral": 0
                }

This should be sufficient for the VM Image provided with kloudbuster (we never had any issue running this on multiple openstack pods).
A disk of zero means it will create a root disk with the default size specified by the image and sufficient for it s need (not necessarily 1GB),

Your log above seems to be related to a manual launch of the VM image?

Can you provide the exact/complete output when running kloudbuster?

Revision history for this message
chinasubbareddy mallavarapu (chinasubbareddy) wrote :

it would be helpful if we can make proxy vm flavor also configurable like server/client vms .

this problem comes when openstack(newton ) setup has bootable volumes enabled for boot from image option specially from horizon.

In the instance launcher, when selecting Image or Image snapshot as boot source, the Create volume option is set to yes by default and size of the volume will be 1GB, that is where vm launch gets failed with kloudbuster image(since it expects more than 1GB space ).

but this is the problem only from horizon not from CLI.

Here is the bug:

https://bugs.launchpad.net/horizon/+bug/1678109

Revision history for this message
Alec Hothan (ahothan) wrote :

This is possible and would require extending the kloudbuster configuration file.
You are welcome to contribute to this patch, otherwise will need that someone has the time to add it.

Revision history for this message
chinasubbareddy mallavarapu (chinasubbareddy) wrote :

most of the times when we try from kloudbuster, it will launch the vm but few times it will fail with above issue .

Alec Hothan (ahothan)
Changed in kloudbuster:
importance: Undecided → Medium
Changed in kloudbuster:
status: New → In Progress
assignee: nobody → chinasubbareddy mallavarapu (chinasubbareddy)
Revision history for this message
Alec Hothan (ahothan) wrote :

Thanks for picking this up, could you please tell me the timeframe of your commit as I am planning the next release (7.1.0) and it needs to go out soon (hopefully by end of this week at the latest).
If not ready I can always pull another release later (7.1.1).

Revision history for this message
chinasubbareddy mallavarapu (chinasubbareddy) wrote :

sine i am new , i may need some time here, i will push this by 7.1.1
thanks .

Revision history for this message
Alec Hothan (ahothan) wrote :

no problem, we will get it on the next release after it gets committed.
Please do not hesitate to ask questions and do not spend too much time on this, it should be straightforward solution (few lines of diffs)

Revision history for this message
chinasubbareddy mallavarapu (chinasubbareddy) wrote :
Revision history for this message
Alec Hothan (ahothan) wrote :

Thank you for your contribution.
Will release in 7.1.2

Changed in kloudbuster:
status: In Progress → Fix Committed
Revision history for this message
Alec Hothan (ahothan) wrote :

Released in 7.1.2

Changed in kloudbuster:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.