Felipe Reyes dad6a14e1a Add configure_keystone_openidc to configure stage.
The configure_keystone_openidc function takes care of configuring the
keystone-openidc charm, at the moment that function set the
oidc-client-id, oidc-client-secret and oidc-provider-metadata-url , this
information comes from the openidc-test-fixture charm.
2022-09-08 23:26:44 -04:00

53 lines
1.7 KiB
YAML

charm_name: keystone-openidc
smoke_bundles:
- focal-yoga
gate_bundles:
- focal-xena
- focal-yoga
- jammy-yoga
dev_bundles:
- jammy-yoga
configure:
- zaza.openstack.charm_tests.vault.setup.auto_initialize
- zaza.openstack.charm_tests.keystone.setup.add_demo_user
- zaza.openstack.charm_tests.glance.setup.add_lts_image
- zaza.openstack.charm_tests.nova.setup.create_flavors
- zaza.openstack.charm_tests.nova.setup.manage_ssh_key
- zaza.openstack.charm_tests.neutron.setup.basic_overcloud_network
- zaza.openstack.charm_tests.openidc.setup.configure_keystone_openidc
- zaza.openstack.charm_tests.openidc.setup.keystone_federation_setup_site1
tests:
- zaza.openstack.charm_tests.keystone.tests.AuthenticationAuthorizationTest
target_deploy_status:
keystone-openidc:
# NOTE: at first we deploy a bundle in which this subordinate charm isn't
# related to anything, so it has no unit. It will become related and
# receive units later as part of the setup stage.
num-expected-units: 0
workload-status: waiting
openidc-test-fixture:
workload-status-message-prefix: 'ready'
vault:
workload-status: blocked
workload-status-message-prefix: Vault needs to be initialized
ntp:
workload-status: active
workload-status-message-prefix: 'chrony: Ready'
ovn-central:
workload-status: waiting
workload-status-message-prefix: "'ovsdb-peer' incomplete, 'certificates' awaiting server certificate data"
ovn-chassis:
workload-status: waiting
workload-status-message-prefix: "'certificates' awaiting server certificate data"
neutron-api-plugin-ovn:
workload-status: waiting
workload-status-message-prefix: "'certificates' awaiting server certificate data, 'ovsdb-cms' incomplete"
tests_options:
force_deploy: []