-
Notifications
You must be signed in to change notification settings - Fork 47
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
approved_message_prefixes should include empty messages #436
Comments
This probably needs to be done in the tests.yaml - see here - to solve the problem on an as needed basis. Setting it to allow '' by default might be too permissive for the library, so I'm -1 on this idea. Other thoughts welcome. |
Hi, I think that Thanks. |
Add NRPE check tests for Designate
This changes are mostly working on the test codes to make sure they are passing for the upcoming jammy support. In addition to that, it removes some old workarounds that are not needed anymore. There's still one open issue about the functional tests. See below. Since this is a big change, here is a summary of changes. Makefile: - remove workaround for the closed issue[0] where symlinks breaking charm push - introduce standard rename.sh tests/unit: - mock a bunch of stuff that were trying to modify system files/dirs tests/functional: - remove workaround for the closed issue[1] where zaza was not respecting local_overlay_enabled key - fix the issue where zaza waits for ubuntu charms indefinitely due to empty message[2] - add missing required config key in iscsi test - charmstore -> charmhub src: - get rid of commented code in production - add missing quotes to a config.yaml default key --- Currently open issues: tests/functional: - focal-fc bundle is not running, probably needs special hardware judging by the constraint given in the bundle file. However it is not listed in gate or smoke bundles, so it is not blocking the release. [0] canonical/charmcraft#109 [1] openstack-charmers/zaza#379 [2] openstack-charmers/zaza#436 Signed-off-by: Mert Kırpıcı <[email protected]>
The
cs:ubuntu
charm no longer displays a messages ('ready', 'Ready', or 'Unit is ready').Its stable state is now 'active' / ''.
This makes zaza wait for ever, until it times out. zaza expects:
This fixes it:
The text was updated successfully, but these errors were encountered: