| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Change-Id: Ia7a65a4f83798cb80ca7470d475c2c2d8c9fb6ea
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
The following tests fail on armband because the VM cannot boot.
tempest.api.compute.servers.test_server_actions.
ServerActionsTestJSON.test_reboot_server_hard
tempest.scenario.test_network_basic_ops.
TestNetworkBasicOps.test_network_basic_ops
tempest.scenario.test_volume_boot_pattern.
TestVolumeBootPattern.test_volume_boot_pattern
tempest.scenario.test_volume_boot_pattern.
TestVolumeBootPatternV2.test_volume_boot_pattern
The reason for the failure is that the 128 ram is insufficient for the
image to boot. The fix consists in increasing the ram to 256
JIRA: ARMBAND-61
Change-Id: I5be1a44a8038b4952cca100511e8d08b7a37681c
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
In order to run functest on an aarch64 POD, some custom configuration
is needed. Up until now that custom configuration was put on the arm
jenkins slave. With this commit it is integrated in functest project.
1. In order to identify if the POD is aarch64 or x86 function
get_arch() from https://gerrit.opnfv.org/gerrit/#/c/29099
is used
2. Changes to config_functest.yaml are made via a new patch file
config_aarch64_patch.yaml which is applied for all scenarios.
Function patch_config_file() is modified to be more generic. It
now receives a file as parameter and merges any type of patch file
3. The aarch64 cirros images are downloaded into the data directory.
Functest can be run from both an aarch64 or a x86 jenkins slave
in order to test an aarch64 POD. So the images are downloded in both
dockerfiles
4. Other custom config needs to be added to /etc/rally/rally.conf
in the docker. The custom config is set in rally_aarch64_patch.conf
and inserted in the needed file before the rally environment is
set up
JIRA: ARMBAND-60
Change-Id: I8e460cdf02d297c259cbbd9c05e7983367fd2bb9
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
Delia Popescu
Cristina Pauna