-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support juju 3.4 #26
Support juju 3.4 #26
Conversation
Using master branch for zaza with TEST_JUJU3=1 [1] and dropping bootstack-actions for func in CI to be able to use specific lxd channel. --- [1]: openstack-charmers/zaza@af7eea9
19bd8e1
to
d716e62
Compare
c70fde3
to
f8686b3
Compare
f8686b3
to
1c12b2f
Compare
e977baf
to
dd52899
Compare
Converted to draft, to test zaza version. |
dd52899
to
a17ee2e
Compare
Fix requirements for install hook not to failed, drop series from metadata.yaml.
e833b26
to
53640c0
Compare
The 60-cloudimg-settings.conf exist on new LXD with "PasswordAuthentication no" so we need to define our own config file.
c6d0e7c
to
c7463d1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please check why is the CI fail.
It's due |
I did not use full path, so that was a problem. |
Using master branch for zaza with TEST_JUJU3=1 1 and dropping
bootstack-actions for func in CI to be able to use specific lxd
channel.
Changing to use of Juju 3.4 controller for testing instead of Juju 3.1, using TEST_JUJU3=1 1 for zaza to install proper libjuju version.
Simply sanitation of project and add workflow concurrency to avoid running multiple workflows on a single PR. Like this if new commit arrived the previous run will be canceled by new run.
blocked until #655 is not merged