RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 836230 - Test case failure: /CoreOS/ypserv/singlehost
Summary: Test case failure: /CoreOS/ypserv/singlehost
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rpcbind
Version: 7.0
Hardware: Unspecified
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-28 12:40 UTC by Karel Volný
Modified: 2012-11-14 15:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-14 15:19:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Karel Volný 2012-06-28 12:40:03 UTC 
Filed from caserun https://tcms.engineering.redhat.com/run/41363/#caserun_1236697

Version-Release number of selected component (if applicable):
RHEL-7.0-20120614.n.1

Steps to Reproduce: 
run the test

Actual results: 
rpcbind.service - RPC bind service
	  Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; enabled)
	  Active: active (running) since Sat, 16 Jun 2012 07:31:44 -0400; 14h ago
	Main PID: 977 (rpcbind)
	  CGroup: name=systemd:/system/rpcbind.service
		  └ 977 /sbin/rpcbind -w


Warning: Unit file changed on disk, 'systemctl --system daemon-reload' recommended.
Warning: Unit file of created job changed on disk, 'systemctl --system daemon-reload' recommended.
Warning: Unit file of created job changed on disk, 'systemctl --system daemon-reload' recommended.
Job failed. See system journal and 'systemctl status' for details.
:: [21:38:10] :: [ ERROR   ] :: rlServiceStart: Starting service rpcbind failed

Expected results:
(no errors starting the service)

Additional information:
this seems to happen only in the beaker run - trying service start manually on an ITP system works without any problem
Comment 1 Honza Horak 2012-07-11 07:44:03 UTC 
I don't think there is any problem in ypserv, since *rpcbind* is the service not starting, so re-assigning to rpcbind.

Just a note: it shouldn't be necessary to explicitly start rpcbind in the test, because it should be done by systemd, according to requirements set in ypbind/ypserv unit files. However, this failure probably means some issues in rpcbind.
Comment 2 Honza Horak 2012-07-11 08:24:52 UTC 
It's weird, that another test (/CoreOS/ypserv/Sanity/initscipts-ypserv), which includes the same command "rlServiceStart rpcbind" succeeds. I'd say something has to be different in test case environment.
Comment 3 Karel Volný 2012-07-11 13:17:57 UTC 
(In reply to comment #1)
> I don't think there is any problem in ypserv, since *rpcbind* is the service
> not starting, so re-assigning to rpcbind.

oops, sorry, it got pre-filled by TCMS

> Just a note: it shouldn't be necessary to explicitly start rpcbind in the
> test, because it should be done by systemd, according to requirements set in
> ypbind/ypserv unit files. However, this failure probably means some issues
> in rpcbind.

thanks for the info, I've updated the test

http://pkgs.devel.redhat.com/cgit/tests/ypserv/commit/?id=3a5776654b0bc05b619c745347f93fd28e997d87

(In reply to comment #2)
> It's weird, that another test (/CoreOS/ypserv/Sanity/initscipts-ypserv),
> which includes the same command "rlServiceStart rpcbind" succeeds. I'd say
> something has to be different in test case environment.

I'd say ... let's wait and see if this could be reproduced in the next RHEL7 tier run ...
Comment 6 Karel Volný 2012-11-14 15:19:47 UTC 
seems the problem is gone ...
https://tcms.engineering.redhat.com/run/50413/#caserun_1767556
Note You need to log in before you can comment on or make changes to this bug.