[ https://ovirt-jira.atlassian.net/browse/OVIRT-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35345#comment-35345 ]

Barak Korren commented on OVIRT-1763:

[~ederevea] OST uses a simple check to determine if to run in RAM or not:

{code} # if above RAM_THRESHOLD KBs are available in /dev/shm, run there RAM_THRESHOLD=15000000

# …

get_run_path() {

local avail_shm
avail_shm=$(df --output=avail /dev/shm | sed 1d)
[[ "$avail_shm" -ge "$RAM_THRESHOLD" ]] && \
    mkdir -p "/dev/shm/ost" && \
    echo "/dev/shm/ost/deployment-$SUITE" || \
    echo "$PWD/deployment-$SUITE"

} {code}

This seems to be 15G so we need to figure out why wasn't this available when these lines ran (These lines are amount the very first things that run when an OST suit starts up, so its unlikely to be cause by anything the suit is doing)

Increase entropy for hosts

     Key: OVIRT-1763
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1763
 Project: oVirt - virtualization made easy
         Issue Type: Bug
Reporter: Dafna Ron
Assignee: infra

we had a failure in ost that was really hard to debug: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3795/ There are no failures in the logs and the test itself was terminated by a timeout. It took the vms a long time to download packages and install and didi seems to think that this is due to limited entropy on the physical host. we need to review this issue and increase the entropy on the hosts.

— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)