-
Notifications
You must be signed in to change notification settings - Fork 163
udiskslinuxmdraid: Add uevent triggers #1429
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
Conversation
|
Cockpit tests failed for commit a6f17e4. @martinpitt, @jelly, @mvollmer please check. |
|
@mvollmer This actually breaks something in TestStorageLvm2.testDegradation. Could you please have a look and check more closely what's wrong? |
|
This may have changed the order D-Bus objects are (dis)appearing, interfaces are updated and signals sent. Depends on how sensitive your tests are. Hopefully the order didn't break other things. |
|
@mvollmer have you had chance to take a look what was the cause of the failure? |
Upps, missed this, sorry. Checking now. |
|
Note that "fedora-43:revdeps" and "fedora-rawhide:revdeps" have passed. Also, the failing test is about raid in lvm2 and this PR only touches the mdraid code pathes. (Both mdraid and lvm2 ultimately use the same kernel raid code, but I don't think the failing test even triggers the code that has been added here to udisks.) So, hmm.... |
|
The navigation to the page for the logical volume seems to have failed in the test. |
|
I think the COPR rpms have disappeared in the mean time. @tbzatek, could you trigger the TF test again? |
|
/packit test |
|
/packit build |
|
(FYI the |
|
Jenkins, test this please. |
Targets for the revdeps tests are so this now means only rawhide and F43: |
|
The |
vojtechtrefny
left a comment
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.
| create.extend(self.md_legs) | ||
| self.assertEqual(subprocess.call(create), 0) | ||
| self.sync() | ||
| time.sleep(2) # FIXME: find a better way |
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 doubt there is a better way when we are calling mdadm --create outside udisks here.
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.
There are several places in the code with # TODO or an arbitrary sleep(5). There is a better way to watch out for objects on the bus, but not trivial to implement.
IOW, are you saying the comment should be removed?
Trigger uevents sync on the raid devices and their members when available. This appears to fix some random test failures.
Integration tests are missing synchronization mechanisms and waiting
for an object to appear on the bus. Thus for now, add a nasty sleep.
======================================================================
FAIL: test_md_raid_methods (__main__.MDRaid.test_md_raid_methods)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/tbzatek/devel/udisks/src/tests/integration-test", line 1855, in test_md_raid_methods
self.assertIsNotNone(block)
~~~~~~~~~~~~~~~~~~~~^^^^^^^
AssertionError: unexpectedly None
a6f17e4 to
e988f9a
Compare
|
Cockpit tests failed for commit e988f9a. @martinpitt, @jelly, @mvollmer please check. |
Infrastructure problems it seems |
Trigger uevents sync on the raid devices and their members when available.
This appears to fix some random test failures.