Fuel for OpenStack

[Murano][OSTF] Misconfiguration in test settings for Murano can lead to tests failure

Bug #1467478 reported by Victor Ryzhenkin on 2015-06-22

This bug affects 4 people

	Status	Importance	Assigned to	Milestone
Fuel for OpenStack	Fix Released	High	Timur Nurlygayanov	Fuel for OpenStack 7.0
6.1.x	Won't Fix	High	MOS Maintenance	Fuel for OpenStack 6.1-updates
7.0.x	Fix Released	High	Timur Nurlygayanov	Fuel for OpenStack 7.0

Bug Description

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "6.1"
  openstack_version: "2014.2.2-6.1"
  api: "1.0"
  build_number: "525"
  build_id: "2015-06-19_13-02-31"
  nailgun_sha: "dbd54158812033dd8cfd7e60c3f6650f18013a37"
  python-fuelclient_sha: "4fc55db0265bbf39c369df398b9dc7d6469ba13b"
  astute_sha: "1ea8017fe8889413706d543a5b9f557f5414beae"
  fuel-library_sha: "2e7a08ad9792c700ebf08ce87f4867df36aa9fab"
  fuel-ostf_sha: "8fefcf7c4649370f00847cc309c24f0b62de718d"
  fuelmain_sha: "a3998372183468f56019c8ce21aa8bb81fee0c2f"

Looking deeper to code of tests, we can find next:

flavor = self.compute_client.flavors.create(
self.flavor_name, disk=60, ram=self.min_required_ram_mb, vcpus=1)

In case if we set in config self.min_required_ram_mb = 4096 we can encounter insufficient resources for spawn 2 VM's running test for WordPress deployment because we will hold at least 8192 Mb.
Also we need to up VCPU to 2 for speedup spawned VM's

Tags: