1. What kops version are you running? The command kops version, will display
this information.
Version 1.19.0-alpha.3 (git-04b9f41daa)

2. What Kubernetes version are you running? kubectl version will print the
version if a cluster is running or provide the Kubernetes version specified as
a kops flag.
v1.19.1

3. What cloud provider are you using?
openstack

4. What commands did you run? What is the simplest way to reproduce this issue?
export KOPS_STATE_STORE=swift://ois

kops create cluster --cloud openstack
--name my-cluster.k8s.local
--state ${KOPS_STATE_STORE}
--zones nova
--network-cidr 192.168.0.0/24
--image Ubuntu-20.04-focal
--master-count=1
--node-count=1
--node-size 8124120
--master-size 8124120
--topology private
--bastion
--networking calico
--api-loadbalancer-type public
--ssh-public-key ~/sshkey.pub
--os-ext-net ext-net-vlan52
--os-kubelet-ignore-az=true

5. What happened after the commands executed?
The creation of the cluster failed. The container was created on the openstack cluster. However, the container is empty.

6. What did you expect to happen?
The k8s cluster state gets created on the openstack container.

7. Please provide your cluster manifest. Execute
kops get --name my.example.com -o yaml to display your cluster manifest.
You may want to remove your cluster name and other sensitive information.

8. Please run the commands with most verbose logging by adding the -v 10 flag.
Paste the logs into this report, or in a gist and provide the gist link here.

I0913 15:58:54.225023    1573 context.go:283] hit maximum retries 5 with error error writing swift://ois/my-cluster.k8s.local/config: Resource not found

error writing updated configuration: error writing Cluster "my-cluster.k8s.local": error writing configuration file swift://ois/my-cluster.k8s.local/config: error writing swift://ois/my-cluster.k8s.local/config: Resource not found

9. Anything else do we need to know?
I am in the process of testing out the fix addressed by #9893 locally. However, this issue is blocking my testing and validation of that issue.
Creating the cluster state was not an issue with the current official release Version 1.18.0 (git-698bf974d8). I am seeing it with the current top of the tree Version 1.19.0-alpha.3 (git-04b9f41daa).