-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(mostly) iSCSI iBFT fixes #1158
Conversation
Jenkins, test this please. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
@@ -374,3 +374,56 @@ def test_login_noauth_badauth(self): | |||
udisks = self.get_object('') | |||
objects = udisks.GetManagedObjects(dbus_interface='org.freedesktop.DBus.ObjectManager') | |||
self.assertNotIn(dbus_path, objects.keys()) | |||
|
|||
def test_ibft(self): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should tag this test as UNSAFE
, just to be sure we won't try to login to some ibft iscsi when running in some random environment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, good idea. I don't expect these tests to be ever used except of very isolated cases of specific testing environments.
No D-Bus reply was sent when asking for loading a module while disabled by a commandline switch.
There's currently no way to distinguish between force-no-auth and use-fw-discovered-auth-info scenarios from the D-Bus API so let's assume that the caller wants to retain the firmware-discovered auth info unless overriden with specific CHAP credentials.
Module objects are responsible for claiming and tracking one or more devices (sysfs paths) that represent a given object purpose. For iSCSI sessions there may be multiple udev devices (LUNs) involved and needs to be tracked to realize when the session object is no longer needed.
Makes no sense to create a new phantom object whose uevent update would fail anyway.
In case the ACPI iBFT table is present in the system, do a simple test and try connecting to everything discovered.
Not every drive object is a valid target for the LSM plugin.
365bca5
to
1100034
Compare
A couple more other fixes that I found along the way.