Cloning environment using Qovery CLI results in runtime error

Questions and Answers
1

I have previously opened this topic but closed it once the issue had resolved itself. It has recently started to occur again. Any ideas why there would be an issue with cloning an environment from this project?

One additional note is that, I have also tried to upgrade the Qovery CLI to v0.94.14 but the issue still persists while running this command:

qovery environment clone --organization <organization> --project <project> --environment <environment> --environment-type <environment_type> --new-environment-name <new_environment_name> --cluster <cluster>
2

Hello @shsalam,

A fix is available in Qovery CLI version 0.94.16.
Please let me know if it does not solve the CLI crash.

Regards

4

Hello @Pierre_Gerbelot ,

I have upgraded my CLI version to 0.94.16 but I am experiencing the same behavior with a new error now:

Error: Post "https://api.qovery.com/environment/237b8f16-2321-486d-840a-26b36b71f8de/clone": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Please let me know if this might be related to a different issue.

Thanks

5

Hello @shsalam

The latest version of the CLI has fixed the crash, allowing us to see the root error. I am currently investigating this issue.

According to the audit log, it appears you attempted to clone the environment twice yesterday. Could you let me know if the CLI fails every time or if this is an intermittent issue?

Thank you

6

Hello @Pierre_Gerbelot ,

The CLI fails every time but only for that specific project. It seems like the CLI is successful in creating the new cloned environment but then immediately crashes.

It is strange because I have not had any issues with it in other projects or when cloning through the Qovery console.

Regards

7

Can you provide the output of the command with the --verbose mode?
This may help us understand the root cause.

Thank you

8

Hello @Pierre_Gerbelot,

I ran the following command using --verbose mode:

qovery environment clone --organization <organization> --project <project> --environment release-template --environment-type STAGING --new-environment-name example-env --cluster non-production --verbose

There is a lot of output with verbose mode and I have copied the part that fails:

POST /environment/237b8f16-2321-486d-840a-26b36b71f8de/clone HTTP/1.1
Host: api.qovery.com
User-Agent: Qovery CLI
Content-Length: 122
Accept: application/json
Authorization: Bearer <token>
Content-Type: application/json
Accept-Encoding: gzip

{"apply_deployment_rule":false,"cluster_id":"<cluster-id>","mode":"STAGING","name":"example-env"}

Error: Post "https://api.qovery.com/environment/237b8f16-2321-486d-840a-26b36b71f8de/clone": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

I have kept the cloned environment up in case it provides some value for debugging purposes.

Thanks

9

Hi @Pierre_Gerbelot ,

Just circling back if there was anything found related to this issue or if there is any additional information I can provide.

Thanks

10

Hello @shsalam

Can you try the latest version of the CLI, 0.95.3, and let me know if the problem is fixed?
The HTTP timeout has been increased in this version.

Thank you

1 Like
11

Hello @Pierre_Gerbelot,

The problem is fixed using v0.95.3 of the CLI.

Thanks

13

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.