Steps to test:
- Setup model-default to always include the ppa
cat << EOF > model-config.yaml #cloud-config apt: sources: lp2023211: source: 'ppa:freyes/lp2023211' EOF juju model-default cloudinit-userdata=@./model-config.yaml
- Clone c-o-t:
git clone https://github.com/openstack-charmers/charmed-openstack-tester.git
- Create a new model:
juju add-model jammy-yoga
- Verify the cloudinit-userdata was set correctly:
juju model-config cloudinit-userdata
- Load env variables:
source ~/novarc
- Create the
func-target
env runningtox -e func-target -- --help
- Activate the created environment:
source ./.func-target/bin/activate
- Cd into the distro-regression directory:
cd ./tests/distro-regression/
- Start the deployment:
functest-deploy -m jammy-yoga -b ./tests/bundles/jammy-yoga.yaml
- Check that the PPA was used to do the deployment:
juju run -a nova-cloud-controller "apt policy nova-common" juju run -a nova-compute "apt policy nova-common"
- Configure the cloud:
functest-configure -m keystone_v3_smoke_focal:jammy-yoga
- Run tempest:
functest-test -m keystone_v3_smoke_focal:jammy-yoga 2>&1 | tee tempest-ppa.log
- Downgrade the nova packages:
juju ssh nova-cloud-controller/0 sudo apt-get install nova-common=3:25.2.0-0ubuntu1 juju ssh nova-compute/N sudo apt-get install nova-common=3:25.2.0-0ubuntu1
- Toggle
debug
to force the restart of servicesjuju config nova-cloud-controller debug=true juju config nova-compute debug=true
- Re-run tempest:
functest-test -m keystone_v3_smoke_focal:jammy-yoga 2>&1 | tee tempest-downgraded.log
In step 9 when I tried to run
functest-deploy -m keystone_v3_smoke_focal:jammy-yoga -b ./tests/bundles/jammy-yoga.yaml
, I got the following errors:The command then failed. I tried again with
functest-deploy -m jammy-yoga -b ./tests/bundles/jammy-yoga.yaml
- so dropping thekeystone_v3_smoke_focal
part in the model argument, and that seems to be working so far. I have a deployment running using thejammy-yoga.yaml
bundle. It will probably take a bit to run. I will report back probably tomorrow on what happens with the deployment.