Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

database subnet should not be required for a pbs deployment #1906

Open
egmsft opened this issue May 8, 2024 · 0 comments
Open

database subnet should not be required for a pbs deployment #1906

egmsft opened this issue May 8, 2024 · 0 comments
Labels
kind/bug Something isn't working

Comments

@egmsft
Copy link
Collaborator

egmsft commented May 8, 2024

Version

Please provide the azhop version used, this one is located in the bottom right of the homepage, or the version you checkout from.
1.0.42

In what area(s)?

/area administration
/area ansible
/area autoscaling
/area configuration
/area cyclecloud
/area documentation
/area image
/area job-scheduling
/area monitoring
/area ood
/area remote-visualization
/area user-management

Expected Behavior

When deploying azhop with pbs and an existing vnet, a database subnet should not be required since it is only used for the MySql Flexible Server for slurm job accounting.

Actual Behavior

When deploying azhop with pbs, and an existing vnet, the deployment fails because azhop is trying to look for a database subnet to create an instance of MySql Flexible server.

Steps to Reproduce the Problem

Set the following attribute in your config file:
deploy with terraform using:
queue_manager: openpbs

an existing vnet with the following subnets:
frontend
admin
netapp
ad
compute

@egmsft egmsft added the kind/bug Something isn't working label May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant