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 620725 - nm-dispatcher.action error in stage1
Summary: nm-dispatcher.action error in stage1
Keywords:
Status: CLOSED DUPLICATE of bug 611141
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: NetworkManager
Version: 6.0
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Dan Williams
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-03 10:31 UTC by Miroslav Vadkerti
Modified: 2010-08-03 21:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-03 21:39:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Error at installation in stage1 (13.41 KB, image/png)
2010-08-03 10:31 UTC, Miroslav Vadkerti
no flags Details
Anaconda logs from /tmp after start of stage2 (18.12 KB, application/x-gzip)
2010-08-03 11:16 UTC, Miroslav Vadkerti
no flags Details

Description Miroslav Vadkerti 2010-08-03 10:31:49 UTC
Created attachment 436240 [details]
Error at installation in stage1

Description of problem:
I can't install Snapshot-9 - RHEL6.0-20100730.5 on my virtual machine with virtio virtual network interface

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


How reproducible:
100%

Steps to Reproduce:
1. Try to install in KVM the tree with default settings (1GB RAM, 8GB HDD)
  
Actual results:
Installation fails to download install images in stage1

Expected results:
No fail

Additional info:
I tried only the default virtio virtual network interface - this worked before, I will try other in short time

Comment 1 Miroslav Vadkerti 2010-08-03 10:33:45 UTC
I'm using http installation

Comment 2 Miroslav Vadkerti 2010-08-03 10:35:14 UTC
Reproduced on x86_64 with
anaconda-13.21.66-1.el6.x86_64.rpm

Comment 3 Miroslav Vadkerti 2010-08-03 10:37:52 UTC
Reproduced also on i686

Comment 4 Miroslav Vadkerti 2010-08-03 10:42:09 UTC
I can reproduce this also with other Virtual Network Interfaces

Comment 6 Miroslav Vadkerti 2010-08-03 10:43:53 UTC
Deactivating IPv6 support doesn't affect this

Comment 7 Miroslav Vadkerti 2010-08-03 11:10:57 UTC
After restarting my host I still see this error appearing but I can continue the installation. Clearing blocker flag. I will attach the logs soon.

Comment 8 Miroslav Vadkerti 2010-08-03 11:16:43 UTC
Created attachment 436247 [details]
Anaconda logs from /tmp after start of stage2

Attached anaconda logs after start of stage2. The error can be seen in syslog.

Comment 9 Radek Vykydal 2010-08-03 12:13:01 UTC
The error message from your screenshot shouldn't cause install fail. I've been
seeing it im my tests too for some time. I believe the install with logs from
comment #8 would finish successfully. Are you reproducing (in comment #3,
comment #4) the message or the install fail? What is the traceback or error
message you are seeing when install fails?

The error message might be NetworkManager issue. Are you seeing it in
/var/log/messages after booting of installed system?

Comment 10 Miroslav Vadkerti 2010-08-03 13:12:28 UTC
After restarting my host I couldn't reproduce the installation blockage in my guests anymore. I will check the logs in /var/log/messages on installed system.

Comment 11 Miroslav Vadkerti 2010-08-03 13:18:24 UTC
I cannot find this error in any logs after booting installed system

Comment 12 Miroslav Vadkerti 2010-08-03 13:20:37 UTC
As this is caused by binary from NetworkManager, reassigning to NetworkManager and putting needinfo on

Comment 13 Dan Williams 2010-08-03 21:39:09 UTC

*** This bug has been marked as a duplicate of bug 611141 ***


Note You need to log in before you can comment on or make changes to this bug.