opendev/system-config
Code Issues Proposed changes

letsencrypt test : update to jammy

Browse Source 
Update this test to use Jammy nodes.  Also add a bit more of a comment
about what's going on.

Change-Id: Ia0c5b922ba70b4ef6c670081f8957fadbd8b3399
This commit is contained in:
Ian Wienand 2023-04-18 11:38:10 +10:00
parent 0f997fc004
commit 07d453d4e6
No known key found for this signature in database
1 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
zuul.d/system-config-run.yaml
View File

@ -225,16 +225,24 @@
name: system-config-run-letsencrypt name: system-config-run-letsencrypt
parent: system-config-run parent: system-config-run
description: | description: |
Run the playbook for letsencrypt key acquisition Run the playbook for letsencrypt key acquisition.
nodeset: nodeset:
nodes: nodes:
- <<: *bridge_node_x86 - <<: *bridge_node_x86
# The other tests run the letsencrypt.yaml playbook to create
# self-signed certificates but do not exercise any of the DNS
# path because they don't have DNS servers in the inventory.
# By adding them for this test, the letsencrypt.yaml playbook
# will make a request to LE staging and get TXT records, which
# it will populate to the test DNS servers. LE won't actually
# authenticate those records, but we are validating the path
# of at least creating and collecting them here.
- name: adns-letsencrypt.opendev.org - name: adns-letsencrypt.opendev.org
label: ubuntu-bionic label: ubuntu-jammy
- name: letsencrypt01.opendev.org - name: letsencrypt01.opendev.org
label: ubuntu-bionic label: ubuntu-jammy
- name: letsencrypt02.opendev.org - name: letsencrypt02.opendev.org
label: ubuntu-bionic label: ubuntu-jammy
groups: groups:
- <<: *bastion_group - <<: *bastion_group
vars: vars: