Repository: getmoto/moto

I have access to a python code repository in the directory /testbed . You can explore and modify files using the available tools. Consider the following issue description:

<issue_description>
ECS list_services ClusterNotFoundException Not raised
## Reporting Bugs

Resource/Client:
**ECS**

Method:
**list_services**

When calling the `ecs` `list_services` with a cluster that does not exist (in moto) the API returns an empty list response.

Expected behavior:
It should raise `ClusterNotFoundException` if cluster_name is invalid.

Moto version: 4.1.0
Python: 3.9
</issue_description>

Can you help me implement the necessary changes to the repository so that the requirements specified in the <issue_description> are met?
I've already taken care of all changes to any of the test files described in the <issue_description>. This means you DON'T have to modify the testing logic or any of the tests in any way!
Also the development Python environment is already set up for you (i.e., all dependencies already installed), so you don't need to install other packages.
Your task is to make the minimal changes to non-test files in the /testbed directory to ensure the <issue_description> is satisfied.

Follow these phases to resolve the issue:

Phase 1. READING: read the problem and reword it in clearer terms
   1.1 If there are code or config snippets. Express in words any best practices or conventions in them.
   1.2 Hightlight message errors, method names, variables, file names, stack traces, and technical details.
   1.3 Explain the problem in clear terms.
   1.4 Enumerate the steps to reproduce the problem.
   1.5 Hightlight any best practices to take into account when testing and fixing the issue

Phase 2. RUNNING: install and run the tests on the repository
   2.1 Activate the environment by running  
       ./opt/miniconda3/etc/profile.d/conda.sh ; conda activate testbed
   2.2 Follow the readme
   2.3 Install the environment and anything needed
   2.4 Iterate and figure out how to run the tests

Phase 3. EXPLORATION: find the files that are related to the problem and possible solutions
   3.1 Use `grep` to search for relevant methods, classes, keywords and error messages.
   3.2 Identify all files related to the problem statement.
   3.3 Propose the methods and files to fix the issue and explain why.
   3.4 From the possible file locations, select the most likely location to fix the issue.

Phase 4. TEST CREATION: before implementing any fix, create a script to reproduce and verify the issue.
   4.1 Look at existing test files in the repository to understand the test format/structure.
   4.2 Create a minimal reproduction script that reproduces the located issue.
   4.3 Run the reproduction script to confirm you are reproducing the issue.
   4.4 Adjust the reproduction script as necessary.

Phase 5. FIX ANALYSIS: state clearly the problem and how to fix it
   5.1 State clearly what the problem is.
   5.2 State clearly where the problem is located.
   5.3 State clearly how the test reproduces the issue.
   5.4 State clearly the best practices to take into account in the fix.
   5.5 State clearly how to fix the problem.

Phase 6. FIX IMPLEMENTATION: Edit the source code to implement your chosen solution.
   6.1 Make minimal, focused changes to fix the issue.

Phase 7. VERIFICATION: Test your implementation thoroughly.
   7.1 Run your reproduction script to verify the fix works.
   7.2 Add edge cases to your test script to ensure comprehensive coverage.
   7.3 Run existing tests related to the modified code to ensure you haven't broken anything.

8. FINAL REVIEW: Carefully re-read the problem description and compare your changes with the base commit 90e63c1cb5178acaa49cfc301b2688dcaba12115.
   8.1 Ensure you've fully addressed all requirements.
   8.2 Run any tests in the repository related to:
     8.2.1 The issue you are fixing
     8.2.2 The files you modified
     8.2.3 The functions you changed
   8.3 If any tests fail, revise your implementation until all tests pass

Be thorough in your exploration, testing, and reasoning. It's fine if your thinking process is lengthy - quality and completeness are more important than brevity.

Gold patch:
diff --git a/moto/ecs/models.py b/moto/ecs/models.py
--- a/moto/ecs/models.py
+++ b/moto/ecs/models.py
@@ -808,7 +808,7 @@ def default_vpc_endpoint_service(service_region, zones):
             service_region, zones, "ecs"
         )
 
-    def _get_cluster(self, name):
+    def _get_cluster(self, name: str) -> Cluster:
         # short name or full ARN of the cluster
         cluster_name = name.split("/")[-1]
 
@@ -1333,10 +1333,10 @@ def create_service(
         return service
 
     def list_services(self, cluster_str, scheduling_strategy=None, launch_type=None):
-        cluster_name = cluster_str.split("/")[-1]
+        cluster = self._get_cluster(cluster_str)
         service_arns = []
         for key, service in self.services.items():
-            if cluster_name + ":" not in key:
+            if cluster.name + ":" not in key:
                 continue
 
             if (


Test patch:
diff --git a/tests/test_ecs/test_ecs_boto3.py b/tests/test_ecs/test_ecs_boto3.py
--- a/tests/test_ecs/test_ecs_boto3.py
+++ b/tests/test_ecs/test_ecs_boto3.py
@@ -701,6 +701,17 @@ def test_list_services():
     cluster1_fargate_services["serviceArns"][0].should.equal(test_ecs_service2_arn)
 
 
+@mock_ecs
+@pytest.mark.parametrize("args", [{}, {"cluster": "foo"}], ids=["no args", "unknown"])
+def test_list_unknown_service(args):
+    client = boto3.client("ecs", region_name="us-east-1")
+    with pytest.raises(ClientError) as exc:
+        client.list_services(**args)
+    err = exc.value.response["Error"]
+    err["Code"].should.equal("ClusterNotFoundException")
+    err["Message"].should.equal("Cluster not found.")
+
+
 @mock_ecs
 def test_describe_services():
     client = boto3.client("ecs", region_name="us-east-1")