Deploy failing due to `lease not found`

Questions / Help
1

Updating existing machines in ‘goblins’ with bluegreen strategy

Verifying if app can be safely deployed

Creating green machines
Created machine 7811ee0b214428 [app]
Created machine 3d8dd735a0e298 [app]
Created machine 4d890d67a26458 [app]
Created machine 784e2eeae41368 [app]
Created machine e28676e2a67578 [app]
Created machine 6e82547ef3e558 [app]
Created machine 17815674fe5338 [app]

Rolling back failed deployment
Deleted machine 7811ee0b214428 [app]
Deleted machine 3d8dd735a0e298 [app]
Deleted machine 4d890d67a26458 [app]
Deleted machine 784e2eeae41368 [app]
Deleted machine e28676e2a67578 [app]
Deleted machine 6e82547ef3e558 [app]
Deleted machine 17815674fe5338 [app]
Deployment failed after error: failed to launch VM: read tcp [fdaa::3]:4280->[fdaa:0:33:a7b:cb:ed2b:c548:2]:34878: i/o timeout
failed to create green machines
WARN failed to release lease for machine 2865991b637e18: lease not found

WARN failed to release lease: lease not found

WARN failed to release lease for machine d8d9799a123068: lease not found

WARN failed to release lease: lease not found

WARN failed to release lease for machine 7811ee7a2763d8: lease not found

WARN failed to release lease: lease not found

Error: failed to launch VM: read tcp [fdaa::3]:4280->[fdaa:0:33:a7b:cb:ed2b:c548:2]:34878: i/o timeout
failed to create green machines (Request ID: 01J5R70W9Q038ZK10ABDDTV1QR-ewr) (Trace ID: cdb424515bf3f3b0aabe8e3909287b41)

2

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