convergence: install blocker GONE; keystone Invalid vips is the known container-v6 gap
8/9 machines started, 6 units active, ZERO in error -- the first deploy had nine
at hook failed install from NO_PUBKEY, so the convergence proves packages install
through the proxy end to end.

Remaining blocked states are the expected early set except one real finding:
keystone/0 Invalid vips on the three GUA v6 VIPs. Measured cause: the keystone
LXD container has zero global IPv6 addresses, so the charm cannot place a v6 VIP
on a space the container has no global v6 on. This is the known-shape condition
from finding D3 (07-31): the nodes are dual-stacked, the API-charm containers are
not. Surfaced then as prefer-ipv6 fatals; with D-139 GUA VIPs it now surfaces as
Invalid vips. IPv6/dual-stack buildout, logged not fixed -- needs an operator
decision, not chased mid-convergence. The v4 VIPs in the same config are accepted.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HvCyrwvYTTcDYnRErfMsNf
1 parent 5a1cb35 commit bed5a1fcf48e0538a5f44802fac5bca7091d5eeb
@JANeumatrix JANeumatrix authored 17 hours ago
Showing 1 changed file
View
docs/CURRENT-STATE.md