Bug 1296255

Summary:	could not lock client with self-hosted LTS
Product:	Red Hat Certification Program	Reporter:	Brian Brock <bbrock>
Component:	redhat-certification-hardware	Assignee:	brose
Status:	CLOSED WONTFIX	QA Contact:	Brian Brock <bbrock>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.0	CC:	gnichols, lennyb, moshele, ymorkovn
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-04-19 02:05:51 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:
Embargoed:

Description Brian Brock 2016-01-06 17:55:47 UTC

Description of problem:
When running hardware certification tests, if a system is both results server and test system, an error about locking is printed.

Version-Release number of selected component (if applicable):
redhat-certification-2.1-20151221.el7.noarch
redhat-certification-hardware-1.7.1-20151218.el7.noarch


How reproducible:
still checking for workarounds or another cause of the same symptoms.  Seen several times, it seems like there may be an additional condition.

Steps to Reproduce:
1. create a hardware certification from packages on the server, without registering any systems.
2. an error message is printed, explaining that the user must register a system before being able to select it for a cert
3. add the system itself as a test system 
 

Actual results:
The results screen that is loaded next shows an error message immediately below the new hostname:

Error: could not lock client	


Expected results:
no complaint about locking 

Additional info:
Going to the page to launch tests (a single results file), there are no tests listed.

Comment 2 Yaroslav Morkovnikov 2016-05-10 13:39:22 UTC

got the same error, is it possible to overcome?

Comment 3 Yaroslav Morkovnikov 2016-05-10 13:39:36 UTC

got the same error, is it possible to overcome?

Comment 5 Lenny Verkhovsky 2016-07-19 08:19:36 UTC

Got the same error, is it possible to overcome?

Comment 6 brose 2016-07-19 13:31:56 UTC

Please, on the client, try:
$rhcertd stop
$rhcert-backend print (answer yes if it asks to override locks)
$rhcertd start

Comment 7 Lenny Verkhovsky 2016-07-19 13:39:54 UTC

#rhcertd stop

Starting RedHatCertDaemon at 2016-07-19 13:37:13
The rhcert daemon is not running
The rhcert listener is not running
[root@r-dcs81 ~]# rhcert-backend print
No test results or plan to print
[root@r-dcs81 ~]# rhcertd start

Starting RedHatCertDaemon at 2016-07-19 13:37:35
Starting rhcert daemon
Starting rhcert listener

#rhcertd status

Starting RedHatCertDaemon at 2016-07-19 13:39:31
The rhcert daemon is running
The rhcert listener is running


Nothing happens, and I cant open UI.
This site can’t be reached
r-dcs81 took too long to respond.

How can I debug/reinstall rhcert?

Comment 8 Greg Nichols 2016-07-19 14:20:03 UTC

Is httpd running?   Try:
$systemctl restart httpd

Comment 9 Lenny Verkhovsky 2016-07-20 08:09:26 UTC

systemctl start  iptables.service  solved the issue

Comment 10 Lenny Verkhovsky 2016-10-09 07:16:13 UTC

p.s. I've seen same error.

After I've stopped #rhcertd stop 
the lock file remained /var/lock/subsys/rhcert
After I had deleted /var/lock/subsys/rhcert, the issue has gone.