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.

Sign up for GitHub

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

Jump to bottom

for v2.0.0 branch - use-nfs-volume-services doesn't work with use-postgres #132

Open
thomasmitchell opened this issue May 12, 2020 · 1 comment
Open

for v2.0.0 branch - use-nfs-volume-services doesn't work with use-postgres #132

thomasmitchell opened this issue May 12, 2020 · 1 comment
Labels
PRIORITY: High Work-around problematic for core functionality, or no workaround for secondary functionality TRIAGE: Accepted Ticket has been accepted for work to proceed TYPE: Bug Defect in intended behaviour

Comments

@thomasmitchell
Copy link
Contributor

the ops file are incompatible. the nfs-volume-services ops file only knows how to add a database to mysql.

/tmp/MmyMA3q9bc/T3X9Np_Yzu/cf-deployment/operations/enable-nfs-volume-service.yml: Expected to find exactly one matching array item for path '/instance_groups/name=database/jobs/name=pxc-mysql' but found 0
@dennisjbell dennisjbell added PRIORITY: High Work-around problematic for core functionality, or no workaround for secondary functionality TRIAGE: Accepted Ticket has been accepted for work to proceed TYPE: Bug Defect in intended behaviour labels Feb 11, 2021
@dennisjbell
Copy link
Member

This should ultimately be fixed by providing postgres and external db versions of the enable-nfs-volume-service.yml op file (or ops files that operate on that file's result) and then updating hooks/blueprint to make use the the appropriate ops files. Should that be rejected, then those files can be instead added to this kit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
PRIORITY: High Work-around problematic for core functionality, or no workaround for secondary functionality TRIAGE: Accepted Ticket has been accepted for work to proceed TYPE: Bug Defect in intended behaviour
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dennisjbell @thomasmitchell