Bug 1123280 - Host status set to non-operational, because /dev/random source
Summary: Host status set to non-operational, because /dev/random source
Keywords:
Status: CLOSED DUPLICATE of bug 1123385
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-hosted-engine-setup
Version: 3.5
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
: 3.5.0
Assignee: Sandro Bonazzola
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-25 08:39 UTC by Artyom
Modified: 2014-07-27 07:24 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-27 05:09:48 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
logs (253.98 KB, application/zip)
2014-07-25 08:39 UTC, Artyom
no flags Details

Description Artyom 2014-07-25 08:39:39 UTC
Created attachment 920907 [details]
logs

Description of problem:
Host status set to non-operational on time of deployment process when added to 'Default' cluster, with warning message:
"Host hosted_engine_1 does not comply with the cluster Default Random Number Generator sources. The Hosts supported sources are: Non interactive user; and the cluster requirements are: RANDOM"

Version-Release number of selected component (if applicable):
engine vm - ovirt-engine-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch
host vdsm - vdsm-4.16.0-42.git3bfad86.el6.x86_64
hoste hosted-engine-setup - ovirt-hosted-engine-setup-1.2.0-0.1.master.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Run hosted-engine --deploy until:
[ INFO  ] Engine replied: DB Up!Welcome to Health Status!
          Enter the name of the cluster to which you want to add the host (Default) [Default]: 
[ INFO  ] Waiting for the host to become operational in the engine. This may take several minutes...
[ INFO  ] Still waiting for VDSM host to become operational...
[ INFO  ] Still waiting for VDSM host to become operational...
2. Enter your engine
3.

Actual results:
Host non-operational, and engine show warning message

Expected results:
Host active without any error messages

Additional info:
It's happening because 'Default' cluster have checked option '/dev/random source' under 'Required Random Number Generator sources', if I uncheck this option, host successfully activated

Comment 1 Sandro Bonazzola 2014-07-25 13:37:24 UTC
I'm not really sure this is a hosted engine issue.
Only anomaly I see in vdsm.log is:

Thread-29::ERROR::2014-07-25 11:31:01,010::task::866::Storage.TaskManager.Task::(_setError) Task=`a8296555-a82c-4d87-94d9-f315b25e296a`::Unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/task.py", line 873, in _run
    return fn(*args, **kargs)
  File "/usr/share/vdsm/logUtils.py", line 45, in wrapper
    res = f(*args, **kwargs)
  File "/usr/share/vdsm/storage/hsm.py", line 1822, in imageSyncVolumeChain
    curChain = img.getChain(sdUUID, imgUUID, volUUID)
  File "/usr/share/vdsm/storage/image.py", line 169, in getChain
    srcVol = volclass(self.repoPath, sdUUID, imgUUID, volUUID)
  File "/usr/share/vdsm/storage/fileVolume.py", line 58, in __init__
    volume.Volume.__init__(self, repoPath, sdUUID, imgUUID, volUUID)
  File "/usr/share/vdsm/storage/volume.py", line 144, in __init__
    self.validate()
  File "/usr/share/vdsm/storage/volume.py", line 156, in validate
    self.validateImagePath()
  File "/usr/share/vdsm/storage/fileVolume.py", line 488, in validateImagePath
    raise se.ImagePathError(imageDir)
ImagePathError: Image path does not exist or cannot be accessed/created: ('/rhev/data-center/2f72a175-b820-41b0-87ed-4006c56a0d22/194013ee-8933-4d17-b5d3-450675a76873/images/08fcf471-ed4c-4ac8-849c-0c2d5ff038b2',)

I need also engine logs and host-deploy logs to understand what happened.
Can you provide them?

Comment 2 Oved Ourfali 2014-07-27 05:09:48 UTC

*** This bug has been marked as a duplicate of bug 1123385 ***

Comment 3 Artyom 2014-07-27 07:24:07 UTC
I see that is duplicate and also virt bug, so hosted-engine logs not necessary


Note You need to log in before you can comment on or make changes to this bug.