[Bug 1571561] Re: cio_ignore blacklist is no longer active after installation

bugproxy bugproxy at us.ibm.com
Wed Dec 14 13:20:17 UTC 2016


------- Comment From heinz-werner_seeck at de.ibm.com 2016-12-14 08:13 EDT-------
Changed target to 17.04 after discussion with Canonical

** Tags removed: targetmilestone-inin16041
** Tags added: targetmilestone-inin1704

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to zipl-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1571561

Title:
  cio_ignore blacklist is no longer active after installation

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Triaged
Status in zipl-installer package in Ubuntu:
  Triaged

Bug description:
  Problem Description
  =======================
  I am installing in a LPAR environment with access to many devices. I want to restrict the access with a cio_ignore device blacklist and provide such a list via the parmfile.

  While the blacklist is active during the installation itself, it is
  not propagated to the installation target: After IPLing the freshly
  installed system, it has full access to all devices of the LPAR as no
  cio_ignore blacklist is active.

  == Comment: #3 - Thorsten Diehl <thorsten.diehl at de.ibm.com> - 2016-04-15 09:14:43 ==
  Dimitri, when fixing things for Bug 139866 - LP 1564475 and Bug 140369 - LP1570775, please consider also this issue here. Install.log will follow.

  == Comment: #4 - Christoph Arenz <arenz at de.ibm.com> - 2016-04-15 10:15:22 ==
  I currently don't have a test LPAR at hand, so I provide data from a z/VM guest, but the symptoms are the same.
  I blacklisted devices explicitely, like so: cio_ignore=100-5ff
  However, after IPLing the installed system, these DASDs are visible and no cio_ignore list is active.

  I am not sure where the 'installation log' can be found, but suspect you mean the file /var/log/installer/syslog.
  If you want another file attached, please let me know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1571561/+subscriptions



More information about the foundations-bugs mailing list