Re: 3.10.0-862.11.6.el7 breaks ipoib - failed to modify QP to RTR: -22

2018-08-21 Thread Akemi Yagi
On Sat, Aug 18, 2018 at 5:41 PM Akemi Yagi  wrote:
>
> On Sat, Aug 18, 2018 at 2:57 PM, Akemi Yagi  wrote:

> > And hopefully RH updates the bug status in their solution article at:
> >
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__access.redhat.com_solutions_3568891&d=DwIBaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=rJMdgZ0Kf_AH_lMllo2MzJnOwzhl84Oc3RhV39JtSb4&s=vcuLkDj0mL4CHeXUYPeYYyGndQGWmz0paMyxB51yCAg&e=
> > "Infiniband card fails to initialize after kernel update in RHEL 7.5"
> >
> > Akemi
>
> There is a bug report with patch candidates at bugs.centos.org :
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.centos.org_view.php-3Fid-3D15193&d=DwIBaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=rJMdgZ0Kf_AH_lMllo2MzJnOwzhl84Oc3RhV39JtSb4&s=3FuS_In9whmlhdZjbNN_oRe9MgHanG3v22atqqQJHaQ&e=
>
> Akemi

Amazingly this rather serious bug was caused by a "mishap" in the source code:

if (!rdma_is_port_valid_nospec(device, &ah_attr->port_num));
[Note the semicolon at the end]

You can find more details by looking for a patch file named
"omg.patch" in the above CentOS bug report. Or by going to the comment
section of the RH solution article referenced earlier.

Akemi


off line upgrade to 7.5 from 7 previous

2018-08-21 Thread Yasha Karant
During the upgrade of a SL 7 non-current system to SL 7 (via yum update 
as root from the Internet), the campus network "glitched" and the system 
hung.  The 7.5 partially installed system panics; it has not recovered. 
The 7 non-current will boot but no X (no GUI), only a scrolling text 
terminal, presumably from which yum can be executed.


I have downloaded Scientific-7.5-Install-Dual-Layer-DVD-x86_64.iso and 
then put this onto an USB flash "thumb" drive that I have confirmed is 
bootable and will start the installation steps.  I do not want to do a 
new install but rather an upgrade, not touching /home , /opt and the like.


I have found old upstream vendor instructions for a previous upstream 
vendor major release of the enterprise (not enthusiast) system; please 
see below.  How are these to
be modified for SL 7.5?  If I boot the Install ISO image (from the USB 
drive), is there a way to get to the old GUI upgrade option that seems 
no longer available?


Please reply to ykar...@gmail.com.  Any assistance would be appreciated.

Yasha Karant

https://urldefense.proofpoint.com/v2/url?u=https-3A__access.redhat.com_documentation_en-2Dus_red-5Fhat-5Fenterprise-5Flinux_5_html_deployment-5Fguide_s1-2Dyum-2Dupgrade-2Dsystem&d=DwICaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=VIBZAPLSw5i79APlbk9o7bb7-I8Ng0G_fvWaaH3Ayb0&s=_Mk6MJ3Ff8HTunQdaQhWLUrVysCAIcVDqWQc9u7T-DQ&e=

14.5. Upgrading the System Off-line with ISO and Yum
For systems that are disconnected from the Internet or Red Hat Network, 
using the yum update command with the Red Hat Enterprise Linux 
installation ISO image is an easy and quick way to upgrade systems to 
the latest minor version. The following steps illustrate the upgrading 
process:


Create a target directory to mount your ISO image. This directory 
is not automatically created when mounting, so create it before 
proceeding to the next step, as root, type:


mkdir mount_dir

Replace mount_dir with a path to the mount directory. Typicaly, 
users create it as a subdirectory in the /media/ directory.
Mount the Red Hat Enterprise Linux 5 installation ISO image to the 
previously created target directory. As root, type:


mount -o loop iso_name mount_dir

Replace iso_name with a path to your ISO image and mount_dir with a 
path to the target directory. Here, the -o loop option is required to 
mount the file as a block device.
Check the numeric value found on the first line of the .discinfo 
file from the mount directory:


head -n1 mount_dir/.discinfo

The output of this command is an identification number of the ISO 
image, you need to know it to perform the following step.
Create a new file in the /etc/yum.repos.d/ directory, named for 
instance new.repo, and add a content in the following form. Note that 
configuration files in this directory must have the .repo extension to 
function properly.


[repository]
mediaid=media_id
name=repository_name
baseurl=repository_url
gpgkey=gpg_key
enabled=1
gpgcheck=1

Replace media_id with the numeric value found in 
mount_dir/.discinfo. Set the repository name instead of repository_name, 
replace repository_url with a path to a repository directory in the 
mount point and gpg_key with a path to the GPG key.
For example, the repository settings for Red Hat Enterprise Linux 5 
Server ISO can look as follows:


[rhel5-Server]
mediaid=1354216429.587870
name=RHEL5-Server
baseurl=file:///media/rhel5/Server
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
enabled=1
gpgcheck=1

Update all yum repositories including /etc/yum.repos.d/new.repo 
created in previous steps. As root, type:


yum update

This upgrades your system to the version provided by the mounted 
ISO image.
After successful upgrade, you can unmount the ISO image, with the 
root privileges:


umount mount_dir

where mount_dir is a path to your mount directory. Also, you can 
remove the mount directory created in the first step. As root, type:


rmdir mount_dir

If you will not use the previously created configuration file for 
another installation or update, you can remove it. As root, type:


rm /etc/yum.repos.d/new.repo

Example 14.1. Upgrading from Red Hat Enterprise Linux 5.8 to 5.9
Imagine you need to upgrade your system without access to the Internet 
connection. To do so, you want to use an ISO image with the newer 
version of the system, called for instance 
RHEL5.9-Server-20121129.0-x86_64-DVD1.iso. You have crated a target 
directory /media/rhel5/. As root, change into the directory with your 
ISO image and type:


~]# mount -o loop RHEL5.9-Server-20121129.0-x86_64-DVD1.iso /media/rhel5/

To find the identification number of the mounted image, run:

~]# head -n1 /media/rhel5/.discinfo
1354216429.587870

You need this number to configure your mount point as a yum repository. 
Create the/et

Re: off line upgrade to 7.5 from 7 previous

2018-08-21 Thread Nico Kadel-Garcia
On Tue, Aug 21, 2018 at 5:53 PM Yasha Karant  wrote:
>
> During the upgrade of a SL 7 non-current system to SL 7 (via yum update
> as root from the Internet), the campus network "glitched" and the system
> hung.  The 7.5 partially installed system panics; it has not recovered.
> The 7 non-current will boot but no X (no GUI), only a scrolling text
> terminal, presumably from which yum can be executed.

If you want to keep this beastie alive, I urge you to:

* Boot from a live USB or DVD image with networking enabled
* Mount the old partitions at /mnt/sysimage, with subpartitions
appropriately under that
* chroot to /mnt/sysimage
* Run "rpm --rebuilddb", because it is probably corrupt
* Get the list of installed packages with "rpm -qa --qf '%{name}.%{arch}\n'"
* For every package, use "yum upgrade $name" and "yum reinstall $name"
* * yum reinstall may require enabling the obsolete repositories
* One or more are likely to balk due to two distinct versions of the
same package.  Resolve that balking package manually, downloading the
current version and using "rpm -U --replacepkgs $name"

> I have downloaded Scientific-7.5-Install-Dual-Layer-DVD-x86_64.iso and
> then put this onto an USB flash "thumb" drive that I have confirmed is
> bootable and will start the installation steps.  I do not want to do a
> new install but rather an upgrade, not touching /home , /opt and the like.
>
> I have found old upstream vendor instructions for a previous upstream
> vendor major release of the enterprise (not enthusiast) system; please
> see below.  How are these to
> be modified for SL 7.5?  If I boot the Install ISO image (from the USB
> drive), is there a way to get to the old GUI upgrade option that seems
> no longer available?

It's nearly impossible to tell which components got messed up in a
mass upgrade. Start from a cleaned up upgrade process, as described
above.

> Please reply to ykar...@gmail.com.  Any assistance would be appreciated.
>
> Yasha Karant