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 1245990 - iSCSI iBFT installation gets stuck on "Performing post-installation setup tasks"
Summary: iSCSI iBFT installation gets stuck on "Performing post-installation setup tasks"
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1077291
TreeView+ depends on / blocked
 
Reported: 2015-07-23 09:14 UTC by Bruno Goncalves
Modified: 2021-08-19 03:34 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-26 14:02:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1245463 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 1245463

Description Bruno Goncalves 2015-07-23 09:14:13 UTC 
Description of problem:
Trying to provision a server with iBFT it gets stuck on "Performing post-installation setup tasks"

Version-Release number of selected component (if applicable):
anaconda 21.48.22.21-1
dracut-033-284.el7


How reproducible:
Seems very often on specific server

Steps to Reproduce:
1.Start RHEL-7.2 provision
2.installation will not complete
3.

Actual results:
It seems there is some connection error at post-installation script:

03:25:32,705 ERR NetworkManager: <error> [1437621932.705391] [devices/nm-device.c:2590] activation_source_schedule(): (ibft0): activation stage already scheduled
03:25:32,706 ERR NetworkManager: <error> [1437621932.705985] [devices/nm-device.c:2590] activation_source_schedule(): (enp4s0f0): activation stage already scheduled
03:27:02,975 ERR NetworkManager: <error> [1437622022.975837] [devices/nm-device.c:2590] activation_source_schedule(): (ibft0): activation stage already scheduled
03:27:02,976 ERR NetworkManager: <error> [1437622022.976061] [devices/nm-device.c:2590] activation_source_schedule(): (enp4s0f0): activation stage already scheduled
03:29:56,769 ERR kernel:[  834.169549]  connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4295483680, last ping 4295488688, now 4295493696
03:29:56,769 INFO kernel:[  834.169595]  connection1:0: detected conn error (1022)
03:29:57,102 WARNING iscsid: Kernel reported iSCSI connection 1:0 error (1022 - Invalid or unknown error code) state (3)
03:30:38,108 WARNING iscsid: connection1:0 is operational after recovery (2 attempts)
Comment 11 Radek Vykydal 2015-07-23 10:23:10 UTC 
Could you please try to reproduce with this updates image which turns NM debug logging on and attach syslog?

https://rvykydal.fedorapeople.org/updates.nmdebug.img
Comment 14 Radek Vykydal 2015-08-12 07:54:31 UTC 
If it is really the same issue as bug 1245463, it could be worth trying with some newer compose (eg http://download.englab.brq.redhat.com/nightly/RHEL-7.2-20150810.n.0/) with newer NetworkManager build with a MTU fix (https://brewweb.devel.redhat.com/buildinfo?buildID=450625) which could perhaps address bug 1245463.

Also, we might want to ask iscsi people what problem this error messages could indicate:

09:11:56,939 ERR kernel:[  400.496413]  connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4295049859, last ping 4295054860, now 4295059872
09:11:56,939 INFO kernel:[  400.496462]  connection1:0: detected conn error (1022)
09:11:57,199 WARNING iscsid: Kernel reported iSCSI connection 1:0 error (1022 - Invalid or unknown error code) state (3)
09:12:13,201 WARNING iscsid: connection1:0 is operational after recovery (1 attempts)
Comment 15 Radek Vykydal 2015-08-12 07:58:31 UTC 
> Also, we might want to ask iscsi people what problem this error messages
> could indicate:
> 
> 09:11:56,939 ERR kernel:[  400.496413]  connection1:0: ping timeout of 5
> secs expired, recv timeout 5, last rx 4295049859, last ping 4295054860, now
> 4295059872
> 09:11:56,939 INFO kernel:[  400.496462]  connection1:0: detected conn error
> (1022)
> 09:11:57,199 WARNING iscsid: Kernel reported iSCSI connection 1:0 error
> (1022 - Invalid or unknown error code) state (3)
> 09:12:13,201 WARNING iscsid: connection1:0 is operational after recovery (1
> attempts)

Chris, does it give any hint of where the problem could be?

The whole syslog comes from failing case of comment #12:
beaker-archive.app.eng.bos.redhat.com/beaker-logs/2015/07/10241/1024113/2100376/sys.log
Comment 16 Martin Hoyer 2015-08-12 11:54:02 UTC 
All installations of RHEL-7.2, including older versions which previously got stuck, are now successful, although we are not aware of any change.
Comment 17 Martin Hoyer 2015-08-13 11:01:42 UTC 
We are not able to reproduce it on RHEL-7.2 however problem still persist when RHEL-7.1 is used
Comment 19 David Cantrell 2015-08-26 14:02:27 UTC 
Closing this as NEXTRELEASE per comment #18.  If this problem reappears, please reopen the bug and attach new log files and steps to reproduce the problem.
Note You need to log in before you can comment on or make changes to this bug.