> > So that means we have this sequence of events: > > a.) growpart change partition table > > b.) growpart call partx > > c.) udev created and events being processed
> That is not true. whilst sfdisk is deleting, creating, finishing > partition table (a) and partx is called (b), udev events are already fired > and running in parallel and may complete against deleted, partially new, > completely new partition table, with or without partx completed. You're correct... I left out some 'events created and handled' after 'a'. But that doesn't change anything. The problem we're seeing here is *not* that 'b' had any issue. > > No amount of settling for events will fix the fact that events were run > against racy state of the partition table _during_ sfdisk and partx calls. complete non-sense. I dont care about any racy state *during* anything. I call 'udevadm settle'. That means "block until stuff is done." I think you're saying that I cannot: 1.) do something that causes udev events 2.) wait until all udev events caused by that something are finished if that is the case, then nothing ever can fix this, and we might as well go find jobs on a farm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
