-
Notifications
You must be signed in to change notification settings - Fork 547
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
[sunbeam][tests] Add product tests for sunbeam #3837
base: main
Are you sure you want to change the base?
Conversation
This is an initial preview of the work on new stageone tests for sunbeam, Canonical's new OpenStack Need to add some more stuff, but wanted to fer an initial pass from everyone |
Congratulations! One of the builds has completed. 🍾 You can install the built RPMs by following these steps:
Please note that the RPMs should be used only in a testing environment. |
362a3f7
to
0a746f3
Compare
The failure is known, I forgot to bring that fix back onto my system, from my test system. All in all working ok, I think; I'll crack on to add other tests that we need, and close to a final update next week.
|
0a746f3
to
f1b9359
Compare
# ] | ||
# | ||
# for the_cmd in cmds_to_check: | ||
# self.assertFileCollected(f'sos_commands/juju/{the_cmd}') |
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.
I have left this here, as we need to add this to functional tests. We need to now figure out what happened in my previous PR on adding these commands, as we should be capturing this.
Once that is resolved, we can enable this section.
Bringing this back as draft, as new Canonical K8s is going to be used, and I don't want future runs to start suddenly failing |
f1b9359
to
3281003
Compare
hmm, took more than 1200 seconds to get a sos report. In my lab it took <900 seconds (see below), maybe I need to increase the size of the VM on GCE to get better performance 🤷🏽
|
3281003
to
1b82d01
Compare
Cirrus + gce is too unstable for openstack to be mocked. I'm ditching this. |
After speaking to Engineering, it seems like a part of the product changed that could be causing failures. 2 changes were made, one to go to LTS of juju, and the Canonical k8s, so once this stabilises, I'll try this again |
5845498
to
b33703a
Compare
* Move the juju tests now to sunbeam, now that we deploy using juju here, no need to mock the configuration files. * Include plugins that are associated here - kubernetes - ovn_host - juju * Allow the product test for sunbeam to be allowed to fail, as the sucecss rate is not that high with all the components that will be shipped with the product, the moving parts and the time taken to run the tests. Related: sosreport#3622 Signed-off-by: Arif Ali <arif.ali@canonical.com>
b33703a
to
d9c3222
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.
Sounds good to me.
need to mock the configuration files.
is not that high with all the components that will be shipped with the
product, the moving parts and the time taken to run the tests.
Related: #3622
Please place an 'X' inside each '[]' to confirm you adhere to our Contributor Guidelines