You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've found that osp_public_subnet is being defined when conditions are met in ansible/roles-infra/infra-osp-project-create/tasks/main.yml
Lines: 20 - 40
- when: >-
osp_project_create | bool
or osp_project_id is not defined
or osp_create_sandbox | bool
......
block:
- name: Get public subnet to use
shell: |
openstack ip availability show external -f json | jq -r '.subnet_ip_availability | min_by(.used_ips) | .subnet_id'
register: r_floating_subnet
- name: Set fact for public subnet
set_fact:
osp_public_subnet: "{{ r_floating_subnet.stdout }}"
From the above when we are deploying on sandbox environments the osp_public_subnet variable will never be automatically defined due to the conditionals.
Is there a work around for sandboxes that I am missing?
I was thinking of hard coding that value as an environment variable but it seems in the environment I cannot pull it in the same way.
openstack ip availability show external -f json --os-cloud=amaya
No NetworkIPAvailability found for f14eb667-03b3-4d97-a2e0-f4a54abe4174
To Reproduce
Steps to reproduce the behavior, ex:
Deploy a OSP sandbox environment
Attempt to deploy any config to that environment
See error
Expected behavior
We should be able to deploy onto sandboxes.
Verions (please complete the following information):
'osp_public_subnet' can not be hard coded, it specifically comes from the command "openstack ip availability show external -f json | jq -r '.subnet_ip_availability | min_by(.used_ips) | .subnet_id'" and is used to identify subnets which have sufficient ip addresses available to avoid a particular bug within OVN that manifests when a floating ip is assigned from a different subnet (on the external network) than the router's external interface.
Typically that command is only available to administrators, however we opened it up to admins or owners, that is possibly why your command failed. What were your openstack credentials set to when you manually executed the command? When sandbox accounts are generated, the user provided to the learner's should have owner privileges within that project.
I will order a sandbox and re-create the issue to troubleshoot.
Describe the bug
Originally from this pull:
ee748d2
I believe this is causing an issue when deploying to sandbox environments because osp_public_subnet is undefined.
I've found that osp_public_subnet is being defined when conditions are met in ansible/roles-infra/infra-osp-project-create/tasks/main.yml
Lines: 20 - 40
From the above when we are deploying on sandbox environments the osp_public_subnet variable will never be automatically defined due to the conditionals.
Is there a work around for sandboxes that I am missing?
I was thinking of hard coding that value as an environment variable but it seems in the environment I cannot pull it in the same way.
To Reproduce
Steps to reproduce the behavior, ex:
Expected behavior
We should be able to deploy onto sandboxes.
Verions (please complete the following information):
git log --pretty=oneline -2
)ansible --version
) 2.9.15Additional context
This is an issue for our agnosticD training efforts as we are providing sandboxes to students. They will need to be able to deploy.
The text was updated successfully, but these errors were encountered: