Non-fleet admin user gets page not found after creating new floating IP

[askfongjojo]

Logged in as a non-fleet admin user, navigated to a project and created a new floating IP (in my case, I didn't specify an IP pool and just used the default). I got a response that the floating IP was created successfully. But the UI also threw a "Page not found" error:

Navigating back to the Floating IP list, I saw the new floating IP in the list.

Looking at the browser debugging console, the error in question was:

{
  "request_id": "27698aa1-8628-4389-b7b9-a17cd165ccd7",
  "error_code": "ObjectNotFound",
  "message": "not found: ip-pool with id \"2d552cb7-c413-4f1b-9f1c-c2bed64a6ce9\""
}

The ip-pool id referenced is the default IP pool for the current silo, the pool from which the floating IP was created.

[david-crespo]

API issue, moved to oxidecomputer/omicron#5883. Reloading works because we are sneakily pre-populating the individual IP pool fetches with data from the list view in the loader, and the list endpoint does not have the permission issue that causes the 404. But I suspect that when you create the floating IP, that causes the individual IP pool view API call to actually run, which hits the 404 and blows up.

console/app/pages/project/floating-ips/FloatingIpsPage.tsx

Lines 65 to 75 in e7d7d95

	apiQueryClient
	.fetchQuery('projectIpPoolList', { query: { limit: 1000 } })
	.then((pools) => {
	for (const pool of pools.items) {
	apiQueryClient.setQueryData(
	'projectIpPoolView',
	{ path: { pool: pool.id } },
	pool
	)
	}
	}),