Bug 1124762

Saggie, do we have an ioprocess build available on EL7?

There is an available package for ioprocess for EL7,
This should be handled by storage group , moving back to storage.

BTW the initial error is "No such file or directory" ...

Is this an engine running on a RHEL7 VM, or an engine running on any VM operating system, but the *host* is running RHEL7?

I'm pretty sure you meant the host, but I want to be sure.

Reporter is Sandro so the best way it ask him, but how I understand host is EL7.
Also hard to understand when it happen, on what stage, on deployment of hosted engine or when hosted-engine deployment already finished, Sandro can you give a little more details about the flow, when exception appear, what actions preceded.

This is ovirt-hosted-engine-setup running on EL7 for creating a VM where it would have been installed EL 6.5 + RHEV-M 3.5 (but it failed before creating the VM)

It failed at Volume creation stage, after having created the storage domain:

2014-07-30 11:09:28 DEBUG otopi.context context._executeMethod:152 method exception
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in _executeMethod
    method['method']()
  File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/sanlock/lockspace.py", line 163, in _misc
    lockspace + '.metadata': md_size,
  File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 336, in create
    service_size=size)
  File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 268, in create_volume
    raise RuntimeError(response["status"]["message"])
RuntimeError: [Errno 2] No such file or directory

There are full logs of the setup execution and corresponding vdsm logs in the attached archive.

I'm not able to reproduce the issue using upstream rpms,maybe we should move this to QE as test-only so it can be checked on next downstream build?

(In reply to Sandro Bonazzola from comment #9)
> I'm not able to reproduce the issue using upstream rpms,maybe we should move
> this to QE as test-only so it can be checked on next downstream build?
Agreed.

I finish deployment for vt4 and not encounter this kind of exception, but all vdsm logs full of:
Thread-20::ERROR::2014-10-05 17:23:10,961::sampling::475::vm.Vm::(collect) vmId=`f4675766-a472-4c49-bde7-ad68db30e77c`::Stats function failed: <AdvancedStatsFunction _sampleCpu at 0x2adf1b0>
Traceback (most recent call last):
  File "/usr/share/vdsm/virt/sampling.py", line 471, in collect
    statsFunction()
  File "/usr/share/vdsm/virt/sampling.py", line 346, in __call__
    retValue = self._function(*args, **kwargs)
  File "/usr/share/vdsm/virt/vm.py", line 313, in _sampleCpu
    cpuStats = self._vm._dom.getCPUStats(True, 0)
  File "/usr/share/vdsm/virt/vm.py", line 670, in f
    ret = attr(*args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/vdsm/libvirtconnection.py", line 111, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2016, in getCPUStats
    if ret is None: raise libvirtError ('virDomainGetCPUStats() failed', dom=self)
libvirtError: Requested operation is not valid: cgroup CPUACCT controller is not mounted
Thread-20::DEBUG::2014-10-05 17:23:10,964::libvirtconnection::143::root::(wrapper) Unknown libvirterror: ecode: 55 edom: 10 level: 2 message: Requested operation is not valid: cgroup CPU controller is not mounted

So I can reassign this bug or just open one new, what you prefer?

Created attachment 944045 [details]
vdsm.log

(In reply to Artyom from comment #11)
> So I can reassign this bug or just open one new, what you prefer?
The two issues seem unrelated - please open a new BZ.

Verified on vdsm-4.16.5-2.el7.x86_64 and ovirt-hosted-engine-setup-1.2.0-1.el7.noarch