Bug 3861 - Install from a 6.0 NFS server SEGVs
Install from a 6.0 NFS server SEGVs
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-07-01 15:58 EDT by cwg-redhat
Modified: 2015-07-29 19:15 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-08 07:23:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description cwg-redhat 1999-07-01 15:58:26 EDT
I'm trying to do a network install off of a RedHat 6.0 box I
just built.  It plain and simple doesn't work.  Shortly
after NFS mounting the partition, I get this:

install exited abnormally -- received signal 11
sending termination signals...done
sending kill signals...done
...etc...

virtual terminal 3 shows the last several lines as:

...
* writing network information to /tmp/ifcfg-eth0
* state saved to /tmp
* second stage install running (version 6.0 build Apr 19
1999 16:17:22)
* extra log messages are enabled

The exact same directory structure on my netwinder works
just fine, but I'm trying to get it out of my build
process.  The netwinder is running 2.0.35.  I can access the
directory via NFS from other systems, and in fact, I could
access it from this same system when booted off the older
redhat5.2 system (which is no longer in a bootable state).
Comment 1 Jay Turner 2000-02-08 07:23:59 EST
Spring cleaning  . . . please reopen this bug if you are still having the noted
trouble.
Comment 2 openshift-github-bot 2015-07-29 19:15:43 EDT
Commit pushed to master at https://github.com/openshift/origin

https://github.com/openshift/origin/commit/8a4de128e22b389da8d9f3f26ee2506ab394789e
Add rolling update strategy for router with -10% update percentage - fixes issue #3861

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