Can't stop environments

Summary

I can't stop environments due to changed URLs

Steps to reproduce

Create an environment with a valid url and delete the DNS record afterwards and try to stop the environment.

What is the current bug behavior?

Error stopping environment, in the gitlab-rails logs:

StateMachines::InvalidTransition: Cannot transition state via :stop from :available (Reason(s): External url is blocked: Host cannot be resolved or invalid)

Unfortunately, we do not have access to the DNS server and the domain was removed on purpose without any previous notice

What is the expected correct behavior?

A stopped environment or maybe a question asking to force environment

Results of GitLab environment info

Expand for output related to GitLab environment info

System information System: Ubuntu 18.04 Current User: git Using RVM: no Ruby Version: 2.6.3p62 Gem Version: 2.7.9 Bundler Version:1.17.3 Rake Version: 12.3.2 Redis Version: 3.2.12 Git Version: 2.22.0 Sidekiq Version:5.2.7 Go Version: unknown

GitLab information Version: 12.2.5 Revision: 09f8edbc29a Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 10.9 URL: https://xxx HTTP Clone URL: https://xxx/some-group/some-project.git SSH Clone URL: git@xxx:some-group/some-project.git Using LDAP: no Using Omniauth: yes Omniauth Providers: crowd

GitLab Shell Version: 9.3.0 Repository storage paths:

  • default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git

Related issues

  • #31885 (closed)

This one is similar but this one is not related to an outage

Assignee Loading
Time tracking Loading