Cancel Schedule - AuctionAdmin results on BadOrigin

[SBalaguer]

Recently Referendum 56 passed on Polkadot, intending to cancel the previously scheduled auctions with the wrong origins for OpenGov and also scheduling new ones with the right auction origin. Scheduling of the new auctions worked just fine, however the canceling of the previously scheduled auctions failed with BadOrigin, as stated here: https://polkadot.subscan.io/block/16477742?tab=event.

Both canceling and scheduling have been done through a batch call with the same origin, AuctionAdmin. The call can be found on the submission linked before.

On Polkadot, scheduler has as a defined origin of EitherOf<EnsureRoot<AccountId>, AuctionAdmin>;, therefore the expected result is for the cancellation to work. On top of this, I couldn't see anything special on the cancel_named extrinsic, that might override the origin.

Right now, the expected behaviour to happen on Polkadot is that the scheduling of an auction will fail, and the scheduling of the same auction under the new origin will work. This does not seem like a huge risk for the network, however it would be better to cancel the wrongly schedule auctions.

[bkchr]

This is not a bug, more the system preventing an origin (the AuctionAdmin) to cancel a scheduled item that was scheduled by an origin (RootOrigin) with higher privileges. The scheduler is using the following code to decide on which origin has higher privileges:

polkadot/runtime/polkadot/src/lib.rs

Lines 193 to 208 in 903cef2

	pub struct OriginPrivilegeCmp;
	impl PrivilegeCmp<OriginCaller> for OriginPrivilegeCmp {
	fn cmp_privilege(left: &OriginCaller, right: &OriginCaller) -> Option<Ordering> {
	if left == right {
	return Some(Ordering::Equal)
	}
	match (left, right) {
	// Root is greater than anything.
	(OriginCaller::system(frame_system::RawOrigin::Root), _) => Some(Ordering::Greater),
	// For every other origin we don't care, as they are not used for `ScheduleOrigin`.
	_ => None,
	}
	}
	}

I would not want to change this to make AuctionAdmin have the same privilege as root.

I propose that we do a whitelisted call by the fellowship to cancel them. The whitelisted call will use root and that will be able to cancel the scheduled item.

Given that this works as expected, I would close this issue.

[SBalaguer]

Ref 130 is up for vote following the suggestion: https://polkadot.polkassembly.io/referenda/130.