I tried to create a new compute environment with FSx, which I had done successfully in the past with Tower.
After a while in CREATING mode, it entered ERRORED mode with this error:
Unable to reach available status for fsx=io.seqera.tower.service.platform.aws.$AwsClientFactoryDefinition$Intercepted@3caa7f83
But I could see in my AWS console that the file system was created successfully.
When I deleted the Compute Environment in Tower, it didn't delete the FSx filesystem in AWS, so I had to delete that manually. Leaving these expensive resources dangling could be problematic.
When I tried again to create the compute environment with the same parameters it had the same error. Then I tried a third time, but this time using the existing FSx filesystem from the second try, and that worked.
I tried to create a new compute environment with FSx, which I had done successfully in the past with Tower.
After a while in CREATING mode, it entered ERRORED mode with this error:
Unable to reach available status for fsx=io.seqera.tower.service.platform.aws.$AwsClientFactoryDefinition$Intercepted@3caa7f83
But I could see in my AWS console that the file system was created successfully.
When I deleted the Compute Environment in Tower, it didn't delete the FSx filesystem in AWS, so I had to delete that manually. Leaving these expensive resources dangling could be problematic.
When I tried again to create the compute environment with the same parameters it had the same error. Then I tried a third time, but this time using the existing FSx filesystem from the second try, and that worked.