Revision history [back]

The LIS team managed to repro the issue on an updated vanilla RHEL / CentOS 7.3 and confirmed that it's a bug with the latest RHEL / CentOS kernel update that just rolled out. While this is being taken care of on the LIS side, the fastest workaround is to revert to the previous kernel at the end of "install-rdo.sh", before v-magine installs LIS. Updates will follow as soon as we finish testing the workaround.

Updated LIS (Linux Integration Services) components are needed as the ones that come with the RHEL / CentOS kernel don't fully support Windows Server 2016 / Windows 10.

The LIS team managed to repro reproduce the issue on an updated vanilla RHEL / CentOS 7.3 and confirmed that it's a bug with the latest RHEL / CentOS kernel update that just rolled out. out (see issue: https://github.com/LIS/lis-next/issues/296). While this is being taken care of on the LIS side, the fastest workaround is to revert to the previous kernel at the end of "install-rdo.sh", before v-magine installs LIS. Updates will follow as soon as we finish testing the workaround.

Updated LIS (Linux Integration Services) components are needed as the ones that come with the RHEL / CentOS kernel don't fully support Windows Server 2016 / Windows 10.

The LIS team managed to reproduce the issue on an updated vanilla RHEL / CentOS 7.3 and confirmed that it's a bug with the latest RHEL / CentOS kernel update that just rolled out (see issue: https://github.com/LIS/lis-next/issues/296). While this is being taken care of on the LIS side, the fastest workaround is to revert to the previous kernel at the end of "install-rdo.sh", before v-magine installs LIS. Updates will follow as soon as we finish testing the workaround.

Updated LIS (Linux Integration Services) components are needed as the ones that come with the RHEL / CentOS kernel don't fully support Windows Server 2016 / Windows 10.

# This is needed due to a bug in LIS with kernel-3.10.0-514.10.2.el7
exec_with_retry 5 0 /usr/bin/yum install -y kernel-3.10.0-514.6.2.el7

The LIS team managed to reproduce the issue on an updated vanilla RHEL / CentOS 7.3 and confirmed that it's a bug with the latest RHEL / CentOS kernel update that just rolled out (see issue: https://github.com/LIS/lis-next/issues/296). While this is being taken care of on the LIS side, the fastest workaround is to revert to the previous kernel at the end of "install-rdo.sh", before v-magine installs LIS. Updates will follow as soon as we finish testing the workaround.

Updated LIS (Linux Integration Services) components are needed as the ones that come with the RHEL / CentOS kernel don't fully support Windows Server 2016 / Windows 10.

Update:

Reverting to the previous kernel solves the issue. This can be done by adding the following at the end of resources/install-rdo.sh :

# This is needed due to a bug in LIS with kernel-3.10.0-514.10.2.el7
exec_with_retry 5 0 /usr/bin/yum install -y kernel-3.10.0-514.6.2.el7

An updated v-magine.zip package with this workaround will be released as soon as tests are done.

The LIS team managed to reproduce the issue on an updated vanilla RHEL / CentOS 7.3 and confirmed that it's a bug with the latest RHEL / CentOS kernel update that just rolled out (see issue: https://github.com/LIS/lis-next/issues/296). While this is being taken care of on the LIS side, the fastest workaround is to revert to the previous kernel at the end of "install-rdo.sh", before v-magine installs LIS. Updates will follow as soon as we finish testing the workaround.

Updated LIS (Linux Integration Services) components are needed as the ones that come with the RHEL / CentOS kernel don't fully support Windows Server 2016 / Windows 10.

Update:

Reverting to the previous kernel solves the issue. This can be done by adding the following at the end of resources/install-rdo.sh :

# This is needed due to a bug in LIS with kernel-3.10.0-514.10.2.el7
exec_with_retry 5 0 /usr/bin/yum install -y kernel-3.10.0-514.6.2.el7

An updated v-magine.zip package with this workaround will be released as soon as tests are done.

The updated kernel that broke LIS was released yesterday (March 6th 2017) on CentOS: https://lists.centos.org/pipermail/centos-announce/2017-March/022324.html