-
Notifications
You must be signed in to change notification settings - Fork 115
Open
Description
I've deployed an environment with 1 CRC, 2 EDPM computes and 2 EDPM netwokers. Script to reproduce the environment:
git clone https://github.com/openstack-k8s-operators/install_yamls
cd ~/install_yamls/devsetup
make download_tools
PULL_SECRET=$HOME/pull-secret.txt CPUS=16 MEMORY=49152 DISK=200 make crc
eval $(crc oc-env)
oc login -u kubeadmin -p 12345678 https://api.crc.testing:6443
make crc_attach_default_interface
export EDPM_TOTAL_NODES=2
export EDPM_TOTAL_NETWORKERS=2
EDPM_COMPUTE_VCPUS=4 EDPM_COMPUTE_RAM=8 EDPM_COMPUTE_DISK_SIZE=75 make edpm_compute
EDPM_COMPUTE_VCPUS=4 EDPM_COMPUTE_RAM=8 EDPM_COMPUTE_DISK_SIZE=75 make edpm_networker
cd ..
PV_NUM=100 make crc_storage
make input
make openstack
make openstack_init
make openstack_deploy
At this point I deploy the computes and the networkers:
DATAPLANE_TOTAL_NODES=2 make edpm_wait_deploy
make edpm_nova_discover_hosts
DATAPLANE_TOTAL_NETWORKER_NODES=2 make edpm_deploy_networker
The last command (edpm_deploy_networker) fails the first time [1] and works the second time that is executed [2].
It is worth mentioning that the status of the osdpns after the deployment is:
$ oc get osdpns
NAME STATUS MESSAGE
openstack-edpm-ipam False NodeSet setup ready, waiting for OpenStackDataPlaneDeployment...
openstack-edpm-ipam-networker True NodeSet Ready
[1]https://paste.opendev.org/show/bfZ8Cj2eVT3KqHSVZJdW/
[2]https://paste.opendev.org/show/bRW5rzQU6CzLDI4ASrZv/
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels