[Bug 1075313] Re: no reliable way to boot from iscsi root
Scott Moser
smoser at ubuntu.com
Thu Jan 31 21:08:09 UTC 2013
For some context wrt maas. We hit an issue when were were booting the
ephemeral environment to do installation (or commissioning) but the
system had previously been booted and installed into a cloud image.
Thus, local disk and iscsi both had LABEL=cloudimg-rootfs.
** Changed in: maas
Status: New => Confirmed
** Changed in: maas
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to open-iscsi in Ubuntu.
https://bugs.launchpad.net/bugs/1075313
Title:
no reliable way to boot from iscsi root
Status in MAAS:
Confirmed
Status in “open-iscsi” package in Ubuntu:
Triaged
Bug description:
In order to boot from iscsi root via kernel parameters, the user would provide kernel parameters something like:
iscsi_target_name=some-iscsi-target-name iscsi_target_port=3260 iscsi_target_ip=some.host root=LABEL=SOME_LABEL
or potentially the same above but with root=UUID=SOME_UUID.
The issue here is that this both LABEL and UUID could collide with a
local filesystem. Perhaps a previous install left a filesystem
labeled "rootfs" that happened to match the filesystem of the
iscsi_target_name and now using "root=LABEL=rootfs". The same is
possible with UUID.
There needs to be some way to specify explicitly:
root=iscsi_target_name=some-iscsi-target-name that would make the iscsi initialization code guaranteed to boot with the appropriate root device independent of whatever local filesystems might have.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: open-iscsi 2.0.873-3ubuntu5
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Mon Nov 5 15:25:48 2012
MarkForUpload: True
ProcEnviron:
LANGUAGE=en_US:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: open-iscsi
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1075313/+subscriptions
More information about the foundations-bugs
mailing list