Bug 1394496

Summary:	iscsistart -b fails to authenticate on boot
Product:	[Fedora] Fedora	Reporter:	Richard Harman <redhat>
Component:	iscsi-initiator-utils	Assignee:	Chris Leech <cleech>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	agrover, cleech, hdegoede
Target Milestone:	---
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:	2017-12-12 10:34:38 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 Richard Harman 2016-11-12 17:45:14 UTC

Description of problem:

In a release of iscsi-initiator-utils after 6.2.0.873-29 (the last version I had on my F23 box), which includes the current release of iscsi-initiator-utils in F24 and F25 (iscsi-initiator-utils-6.2.0.873-34.git4c1f2d9.fc25.x86_64), iscsistart -b tries to perform CHAP auth against an iscsi target and somehow manages to cause an auth failure.

I verified the auth failure with a tcpdump of the ISCSI exchange, and extracted iscsistart from my F23 initrd, and placed it on a USB thumb drive.  When I wan iscsistart -b off the USB thumb drive in the dracut rescue console, my ISCSI volume mounted.

If I pull the src rpm from F23 of iscsi-initiator-utils 6.2.0.873-29 and compile that, and rebuild my initrd, everything works again.

Version-Release number of selected component (if applicable):

iscsi-initiator-utils after 6.2.0.873-29

How reproducible:

100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Fedora End Of Life 2017-11-16 19:22:00 UTC

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-12-12 10:34:38 UTC

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.