Bug 1013563

Summary: Error while monitoring engine: Could not start sanlock because of wrong service path in sudoers file
Product: Red Hat Enterprise Virtualization Manager Reporter: Leonid Natapov <lnatapov>
Component: ovirt-hosted-engine-haAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED ERRATA QA Contact: Leonid Natapov <lnatapov>
Severity: urgent Docs Contact:
Priority: urgent    
Version: unspecifiedCC: dfediuck, gpadgett, iheim, oourfali, sbonazzo, scohen
Target Milestone: ---Keywords: Reopened
Target Release: 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: ovirt-hosted-engine-ha-0.1.0-0.3.1.beta1.el6ev Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-21 16:50:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Leonid Natapov 2013-09-30 10:47:04 UTC
/etc/sudoers.d/60_ovirt-ha had /usr/sbin/service as hardcoded path and the path is different on different OS.

For example it's fin for Fedora but I have RHEL 6.5 and it's in  /sbin/service not /usr/sbin/services 
---------------
MainThread::ERROR::2013-09-30 12:20:50,461::hosted_engine::326::HostedEngine::(_cond_start_service) Starting sanlock
MainThread::WARNING::2013-09-30 12:20:56,014::hosted_engine::238::HostedEngine::(start_monitoring) Error while monitoring engine: Could not start sanlock: sudo: no tty present and no askpass program specified

MainThread::WARNING::2013-09-30 12:20:56,015::hosted_engine::241::HostedEngine::(start_monitoring) Unexpected error
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 228, in start_monitoring
    self._initialize_sanlock()
  File "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 351, in _initialize_sanlock
    self._cond_start_service('sanlock')
  File "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 335, in _cond_start_service
    .format(service_name, res[1]))
Exception: Could not start sanlock: sudo: no tty present and no askpass program specified

Comment 1 Doron Fediuck 2013-09-30 13:57:16 UTC
Sandro is this handled by the setup?
Please check if related to RHEL 6.5.

Comment 3 Sandro Bonazzola 2013-10-01 09:42:25 UTC
(In reply to Doron Fediuck from comment #1)
> Sandro is this handled by the setup?
> Please check if related to RHEL 6.5.

No it's not handled by setup, it's provided by ha package.
It's a packaging issue: the configure script should detect `service` path and configure the sudoers file accordingly to that path.

Comment 4 Sandro Bonazzola 2013-10-01 09:44:40 UTC
Reassigning to Greg.
Greg if you have more urgent issues to fix, I can take care of it tomorrow.

Comment 6 Sandro Bonazzola 2013-10-04 07:09:57 UTC
patch merged upstream master

Comment 8 Sandro Bonazzola 2013-10-14 09:18:48 UTC
It seems that built package still have this issue. Need to figure out why.

Comment 9 Sandro Bonazzola 2013-10-14 09:19:51 UTC
*** Bug 1018706 has been marked as a duplicate of this bug. ***

Comment 10 Greg Padgett 2013-10-14 15:09:28 UTC
Merged Change-Id: I1e069cefbd55a4aa7a85abd48beded57846ce78f

Comment 11 Leonid Natapov 2013-11-04 08:40:08 UTC
fixed.

Comment 12 Charlie 2013-11-28 01:42:00 UTC
This bug is currently attached to errata RHEA-2013:15591. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to 
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.

Comment 13 Sandro Bonazzola 2013-12-05 10:57:58 UTC
hosted engine is a new package, does not need errata for specific bugs during its development.

Comment 14 errata-xmlrpc 2014-01-21 16:50:13 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-0080.html