A second install produced the same result. The first two installs used refresh-installer: {update: yes}.
A third install used refresh-installer: {update: no} and behave correctly.
Dennis observed the following:
> in subiquity-server-debug.log.3845 from your logs I see
> 2024-04-22 14:41:41,983 INFO root:38 start: subiquity/Meta/status_GET:
> which is not followed by a subiquity/Meta/status_GET: SUCCESS: 200 ...
> possibly what causes the broken state in the UI
A second install produced the same result. The first two installs used refresh-installer: {update: yes}.
A third install used refresh-installer: {update: no} and behave correctly.
Dennis observed the following: server- debug.log. 3845 from your logs I see Meta/status_ GET: Meta/status_ GET: SUCCESS: 200 ...
> in subiquity-
> 2024-04-22 14:41:41,983 INFO root:38 start: subiquity/
> which is not followed by a subiquity/
> possibly what causes the broken state in the UI