Parsl is grabbing all pre-existing EC2 instances in an AWS account on startup, causing a KeyError in self.resources
in AWSProvider().status()
#3764
Labels
self.resources
in AWSProvider().status()
#3764
Describe the bug
When the AWSProvider goes to check and update the status of tracked jobs in
self.resources
with an emptyjob_ids
list (happened on initial submission), the boto client methoddescribe_instances
returns all InstanceIds in that account. There could be running EC2 instances in general. This causes a KeyError at this line https://github.com/Parsl/parsl/blob/master/parsl/providers/aws/aws.py#L624.To Reproduce
Steps to reproduce the behavior, for e.g:
1.3.0-dev
with Python 3.11 on cluster, laptop, ec2but with
credentials.json
where EC2 instances are already running.3. Let run for a few seconds
4. See error. The error always contained the same KeyError, and this was because it was an existing EC2 id.
Expected behavior
Parsl should only track the EC2 instances it submits.
Environment
Distributed Environment
The text was updated successfully, but these errors were encountered: