Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1396054

Summary:	autofs: state.c:627: assertion failed: ap->state == ST_READY \|\| ap->state == ST_EXPIRE
Product:	Red Hat Enterprise Linux 6	Reporter:	xiaoli feng <xifeng>
Component:	autofs	Assignee:	Ian Kent <ikent>
Status:	CLOSED CURRENTRELEASE	QA Contact:	xiaoli feng <xifeng>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.9	CC:	eguan, ikent, xifeng
Target Milestone:	rc	Keywords:	Regression, Reproducer
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-16 09:17:52 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 xiaoli feng 2016-11-17 11:06:08 UTC

Description of problem:
Test autofs hosts map, happen this error:

ls: cannot access /net/hp-dl380pgen8-02-vm-7.lab.bos.redhat.com/tmp: No such file or directory

The debug log:

Nov 17 05:35:33 hp-dl380pgen8-02-vm-7 automount[13638]: state.c:627: assertion failed: ap->state == ST_READY || ap->state == ST_EXPIRE
Nov 17 05:35:33 hp-dl380pgen8-02-vm-7 automount[13638]: nextstate:85: write failed Bad file descriptor
Nov 17 05:35:33 hp-dl380pgen8-02-vm-7 automount[13638]: state.c:627: assertion failed: ap->state == ST_READY || ap->state == ST_EXPIRE
Nov 17 05:35:33 hp-dl380pgen8-02-vm-7 automount[13638]: nextstate:85: write failed Bad file descriptor
Nov 17 05:36:48 hp-dl380pgen8-02-vm-7 rpc.mountd[13565]: Caught signal 15, un-registering and exiting.

Version-Release number of selected component (if applicable):
2.6.32-671.el6.x86_64

How reproducible:
100%, but only first time boot from installing system can reproduce.

Steps to Reproduce:
1. reproducer script:
echo "/ *(rw,insecure,async)" >/etc/exports
echo "/tmp *(rw,insecure,async)" >> /etc/exports
echo "/net  -hosts" > /etc/auto.master
service   autofs start
service nfs start
ls /net/$HOSTNAME/tmp
service autofs stop
service nfs stop


Actual results:

auto mount nfs fail

Expected results:

auto mount nfs successfully

Additional info:

Comment 1 xiaoli feng 2016-11-17 11:15:12 UTC

Sorry, Version-Release number of selected component is
autofs-5.0.5-126.el6

Comment 2 Ian Kent 2016-11-17 11:23:56 UTC

I'll try and reproduce this and see if I can see what's going on.

But rpc.mountd getting a SIGTERM and exiting, likely in middle
of servicing a request from automount(8) is a bit suspicious.

Comment 5 Ian Kent 2016-11-18 00:44:07 UTC

(In reply to xiaoli feng from comment #0)
> Description of problem:
> Test autofs hosts map, happen this error:
> 
> ls: cannot access /net/hp-dl380pgen8-02-vm-7.lab.bos.redhat.com/tmp: No such
> file or directory
> 
> The debug log:
> 
> Nov 17 05:35:33 hp-dl380pgen8-02-vm-7 automount[13638]: state.c:627:
> assertion failed: ap->state == ST_READY || ap->state == ST_EXPIRE
> Nov 17 05:35:33 hp-dl380pgen8-02-vm-7 automount[13638]: nextstate:85: write
> failed Bad file descriptor
> Nov 17 05:35:33 hp-dl380pgen8-02-vm-7 automount[13638]: state.c:627:
> assertion failed: ap->state == ST_READY || ap->state == ST_EXPIRE
> Nov 17 05:35:33 hp-dl380pgen8-02-vm-7 automount[13638]: nextstate:85: write
> failed Bad file descriptor
> Nov 17 05:36:48 hp-dl380pgen8-02-vm-7 rpc.mountd[13565]: Caught signal 15,
> un-registering and exiting.

This looks like it is being done on the same host.
Is that correct?

Can you re-run this test and post the autofs debug log please?

Ian

Comment 6 xiaoli feng 2016-11-18 02:42:02 UTC

(In reply to Ian Kent from comment #5)
> (In reply to xiaoli feng from comment #0)
> > Description of problem:
> > Test autofs hosts map, happen this error:
> > 
> > ls: cannot access /net/hp-dl380pgen8-02-vm-7.lab.bos.redhat.com/tmp: No such
> > file or directory
> > 
> > The debug log:
> > 
> > Nov 17 05:35:33 hp-dl380pgen8-02-vm-7 automount[13638]: state.c:627:
> > assertion failed: ap->state == ST_READY || ap->state == ST_EXPIRE
> > Nov 17 05:35:33 hp-dl380pgen8-02-vm-7 automount[13638]: nextstate:85: write
> > failed Bad file descriptor
> > Nov 17 05:35:33 hp-dl380pgen8-02-vm-7 automount[13638]: state.c:627:
> > assertion failed: ap->state == ST_READY || ap->state == ST_EXPIRE
> > Nov 17 05:35:33 hp-dl380pgen8-02-vm-7 automount[13638]: nextstate:85: write
> > failed Bad file descriptor
> > Nov 17 05:36:48 hp-dl380pgen8-02-vm-7 rpc.mountd[13565]: Caught signal 15,
> > un-registering and exiting.
> 
> This looks like it is being done on the same host.
> Is that correct?

Yes, on the same host. This test only use one host.

> 
> Can you re-run this test and post the autofs debug log please?
> 
> Ian