reverted out of scope doc changes

stackhpc · Jan 17, 2025 · f191051 · f191051
1 parent ce6c532
commit f191051
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/doc/source/contributor/testing-ci-automation.rst b/doc/source/contributor/testing-ci-automation.rst
@@ -123,7 +123,7 @@ The workflow performs the following high-level steps:
 #. If this is an upgrade job, upgrade the cloud under test to the target
    release.
 #. Run Tempest and `StackHPC OpenStack Tests
-   <https://github.com/stackhpc/stackhpc-cloud-tests>`_ to test the cloud.
+   <https://github.com/stackhpc/stackhpc-openstack-tests>`_ to test the cloud.
 #. Collect diagnostic information.
 #. Upload results as an artifact.
 #. Destroy the VM using Terraform.
@@ -346,11 +346,11 @@ The workflow performs the following high-level steps:
 #. Register test resources in the cloud under test (images, flavors, networks,
    subnets, routers, etc.).
 #. Run Tempest and `StackHPC OpenStack Tests
-   <https://github.com/stackhpc/stackhpc-cloud-tests>`__ to test the cloud.
+   <https://github.com/stackhpc/stackhpc-openstack-tests>`__ to test the cloud.
 #. If this is an upgrade job, upgrade the cloud under test to the target
    release.
 #. Run Tempest and `StackHPC OpenStack Tests
-   <https://github.com/stackhpc/stackhpc-cloud-tests>`__ to test the cloud.
+   <https://github.com/stackhpc/stackhpc-openstack-tests>`__ to test the cloud.
 #. Collect diagnostic information.
 #. Upload results as an artifact.
 #. Destroy the VMs using Terraform.

diff --git a/releasenotes/notes/stackhpc-openstack-tests-0224908453ae72cc.yaml b/releasenotes/notes/stackhpc-openstack-tests-0224908453ae72cc.yaml
@@ -3,6 +3,6 @@ features:
   - |
     Adds a new ``stackhpc-openstack-tests.yml`` playbook that executes tests in
     the `StackHPC OpenStack Tests
-    <https://github.com/stackhpc/stackhpc-cloud-tests>`__ repository. Both
+    <https://github.com/stackhpc/stackhpc-openstack-tests>`__ repository. Both
     the playbook and tests are currently experimental, and are currently
     targeting only an all-in-one CI use case.