hasura / hasura/graphql-engine

Issue while running hasura scripts update-project-v2: error in removing up.yaml ... The process cannot access the file because it is being used by another process.

Open
#9,161 1 comment 0 reactions 0 assignees View on GitHub
k/bug
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Version Information

Server Version: 2.13.0
CLI Version (for CLI related issues): 2.13.0

### Environment

OSS

### What is the current behavior?

We recently updated our Hasura image from 1.3.3 to 2.13.0 - After updating we came to know that we should use migrate config v2 instead of the current V1. So, when migrating from config v1 to config v2 using the reference https://hasura.io/docs/latest/migrations-metadata-seeds/legacy-configs/config-v2/upgrade-v2/ .. getting the below error:

**hasura scripts update-project-v2**
time="2022-10-31T12:34:03+05:30" level=fatal msg=" error in removing up.yaml: remove C:\\Users\\xxxx\\xxx\\xx-service\\database\\migrations\\1561012873746_create_table_public_request_type.up.yaml: The process cannot access the file because it is being used by another process."**

### What is the expected behaviour?

successful migration to config v2.

### How to reproduce the issue?

1. Update an existing Hasura image from 1.3.3 to 2.13.0
2. Update the CLI version to 2.13.0
3. run **hasura scripts update-project-v2**

### Screenshots or Screencast

**ERROR on console**
time="2022-10-31T12:34:03+05:30" level=fatal msg=" error in removing xxxx.up.yaml: remove C:\\Users\\xxxx\\xxx\\xx-service\\database\\migrations\\1561012873746_create_table_public_request_type.up.yaml: The process cannot access the file because it is being used by another process."**

### Please provide any traces or logs that could help here.

No logs. Where can I locate it?

### Any possible solutions/workarounds you're aware of?

No

### Keywords

I did not find anything related to this issue.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.