Skip to content
This repository has been archived by the owner on Feb 11, 2020. It is now read-only.

Azure file storage is not used when configured #349

Open
gondoi opened this issue Jul 18, 2018 · 2 comments
Open

Azure file storage is not used when configured #349

gondoi opened this issue Jul 18, 2018 · 2 comments

Comments

@gondoi
Copy link

gondoi commented Jul 18, 2018

Issue

When using install-pcf on Azure from the master branch, defining azure_storage_account_name as suggested in the params comments, does not actually configure the PAS tile to use Azure storage and defaults to internal (NFS).
This is with both 2.1 and 2.2 that I have tested.

Context

Defining this gives the expectation that the storage accounts created will be configured and used. Although, NFS is created and used and if this storage option is used, blobstore migration will have to be performed in order to switch.

Expected result

Use the storage type defined.

Current result

The option is ignored and internal storage is used.

Steps to Reproduce

Define, run pipeline, and review settings in PAS for file storage.

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

@gondoi
Copy link
Author

gondoi commented Jul 18, 2018

I found that internal storage is hard coded in the task, so providing a value in the params file does nothing:

https://github.com/pivotal-cf/pcf-pipelines/blob/master/tasks/config-ert/task.sh#L170-L173

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants