| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Parsing of /proc/scsi/scsi updated to work with latest zFCP.
Matching SCSI ID correctly with all of zFCP device, WWPN, and LUN.
Synchronization with udev_settle.
Error case is handled gracefully and reports user readable error message.
|
| |
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| | |
mdmon application is needed to switch imsm md array to read/write mode.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Write out NM_CONTROLLED=no for NICs used for FCoE, note that unlike with
iSCSI we do not blindly write out NM_CONTROLLED=no for all NICs, but just
for the NIC which is used for FCoE.
The iSCSI behaviour is undesirable, but the whole writing of NM_CONTROLLED=no
for iSCSI will go away as soon as NetworkManager is fixed to not down
devices when it takes over control, which should be fixed soon.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Reverse most of commit 9e4d2e76713c9c71dcdaf22767211c13be9b3668, because it
currently is not working and MD containers can for 99.9 % be treated as
regular mdarrays. The next patch from this set instead makes the necessary
changes to use the regular mdarray handling code, reducing the amount
of code.
|
| |
| |
| |
| |
| |
| |
| |
| | |
While testing isw bios raid using mdraid, I hit a backtrace caused
by all udev_is-foo() checks failing. This patch logs an error and
ignores the device instead of backtracing. I believe this may work
around quite a few "'NoneType' object has no attribute Name" bugs we
have open at the moment.
|
| |
| |
| |
| |
| |
| |
| | |
We are currently not calling blkid when a block device is not an
mdraid set or a device mapper device, resulting in us not identifying
mdraid members as such. This probably worked when still using vol_id
because some other rules file was doing an import vol_id before our rules.
|
| | |
|
| |
| |
| |
| | |
Add an command to activate FCoE attached SAN's from kickstart
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This should fix up a majority, if not all, of the 'cannot commit to disk
after 5 attempts' errors. I was hitting this today. The cause I found
to be active logical volumes still around when the storage code wanted
to commit changes to the disk. When a logical volume is active,
libparted is getting EBUSY when it tries to commit changes to the disk
and tell the kernel to reread the partition table. If the LV is active,
we need to deactivate it and the volume group before we start committing
changes to disk.
Adding a status() property to LVMLogicalVolumeDevice that looks at the
lv_attr field for an 'a' fixes the problem for me on F-11. All of the
code to down LVM devices is there, we just weren't checking the LV
status correctly.
|
| |
| |
| |
| |
| | |
Include the lv_attr field in the lvm.lvs() hash table returned. Needed
to tell if the logical volume is active or not.
|
|/
|
|
| |
Adjust memory requirements.
|
|
|
|
|
| |
'sparc' and 's390' are what are returned by iutil.getArch; however, we don't
actually support 31/32-bit installs on those machines.
|
| |
|
|
|
|
|
| |
Just use rpmUtils's definition of multilib arches, and we no longer
set ppc64iseries/ppc64pseries.
|
|
|
|
|
| |
Note: Compared to writing out of our own /etc/hosts which was removed in
bug 491808, we do not write line for host's IP address.
|
|
|
|
|
|
|
|
| |
libisys and loader lacked handling for the LAYER2 and PORTNO settings
present on s390x systems.
Also include the fix for #468755 to write layer2=1 rather than layer=2
to the ifcfg-DEVICE file.
|
| |
|
|
|
|
| |
These configure arguments are of the format --enable-X, not --with-X.
|
|
|
|
|
| |
Create /etc/dhcp in the initrd image and make sure loader writes
dhclient configuration files to /etc/dhcp.
|
|
|
|
|
|
|
|
|
| |
automation (#509881)
Anaconda appends "rhgb quiet" to the bootloader's kernel arguments.
On s390x, there is not graphical console. A console of type line mode is most
common. Even more so, it's not uncommon to do system automation based on the
guest OS's console output. Therefore, allow full output of kernel boot messages on the console.
|
|
|
|
|
|
|
|
| |
Replaces previous post with fixed patch.
Assuming anaconda.id.bootloader.device is always a disk device
(not a partition) and it always contains the device /boot and hence the
zipl bootloader is located on, this fixes the back trace.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Add FCoE disks to the devicetree with a type of FcoeDiskDevice instead
of DiskDevice
|
| |
|
|
|
|
|
|
| |
Add the ability to identify if a disk is an FCoE device and to
get the identifier of the disk and the name of the NIC used to
connect to an FCoE disk
|
|
|
|
|
| |
Write out an /etc/fcoe/cfg-eth# file for each nic used to connect to
an FCoE SAN during the install.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds support for using FCoE during the installation. This patch
merely lays the initial ground work, there is more work todo:
- The system will not boot without manual help after the install, as
dracut / mkinitrd do not support FCoE yet
- If FCoE is not used for / but for example for /srv, then information
about the nic used for FCoE needs to be written in a to be defined
config file in the system, and rc.sysinit needs to be thought to read
this file and bring up FCoE SAN's / Fabrics not used for /
- kickstart support for FCoE still needs to be done
|
| |
|
| |
|