[01:21:10] Is ToolsDB accessible outside of cloud services servers? [03:13:22] you should just say what you want to do. from the public internet or from where? for interactive use or a remote web app or? (re @wmtelegram_bot: Is ToolsDB accessible outside of cloud services servers?) [12:52:59] !log paws moved all notebooks with Android binaries to /srv/paws/files-to-remove/ [12:53:02] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Paws/SAL [15:58:33] Hi, I'm trying to configure access using CIDR addresses, but I get the following validation error: [15:58:33] Validation error: instance['access']['allowed_cidrs'][0] '2001:db8::/32' does not match '^([0-9]{1,3}\.){3}[0-9]{1,3}(\/([0-9]|[1-2][0-9]|3[0-2]))?$'; [15:58:33] instance['access']['allowed_cidrs'][1] '2001:db8:abcd::1/64' does not match... [15:58:33] According to the field description, allowed_cidrs is supposed to accept a comma-separated list of IPv4, IPv6, or mixed CIDRs (e.g., 0.0.0.0/0, 2001:db8::/64), which is exactly what I'm trying to do. [15:58:34] However, the current validation pattern still seems to only accept IPv4 ranges. [15:58:35] It looks like someone forgot to update the regular expression to support IPv6 CIDRs when IPv6 support was implemented. [15:58:35] Is there a workaround, a separate field like allowed_ipv6_cidrs, or can this be fixed in the frontend/backend validator to properly accept IPv6 ranges? [15:59:36] Hi, I'm trying to configure access using CIDR addresses, but I get the following validation error: [15:59:36] Validation error: instance['access']['allowed_cidrs'][0] '2001:db8::/32' does not match '^([0-9]{1,3}\.){3}[0-9]{1,3}(\/([0-9]|[1-2][0-9]|3[0-2]))?$'; [15:59:37] instance['access']['allowed_cidrs'][1] '2001:db8:abcd::1/64' does not match... [15:59:37] According to the field description, allowed_cidrs is supposed to accept a comma-separated list of IPv4, IPv6, or mixed CIDRs (e.g., 0.0.0.0/0, 2001:db8::/64), which is exactly what I'm trying to do. [15:59:38] However, the current validation pattern still seems to only accept IPv4 ranges. [15:59:38] It looks like someone forgot to update the regular expression to support IPv6 CIDRs when IPv6 support was implemented. [15:59:39] Is there a workaround, a separate field like allowed_ipv6_cidrs, or can this be fixed in the frontend/backend validator to properly accept IPv6 ranges? [15:59:56] configure what where exactly? [16:00:28] creating a database instance [16:02:36] sounds like you are hitting a known issue, T393760, then? [16:02:37] T393760: trove: Unable to create user with IPv6 address as host - https://phabricator.wikimedia.org/T393760 [16:02:57] note that the database service itself seems to be stuck as v4-only now (T398189) unfortunately [16:02:57] T398189: Trove managed instances should be dual stack - https://phabricator.wikimedia.org/T398189 [16:09:37] lol