K8SSAND-1409 ⁃ Test dump does not output all objects #312
Assignees
Labels
enhancement
New feature or request
Comments
This was referenced Apr 1, 2022
burmanm
added a commit
to burmanm/cass-operator
that referenced
this issue
Apr 1, 2022
sync-by-unito
bot
changed the title
burmanm
added a commit
that referenced
this issue
Apr 5, 2022
* Another try * Update upgrade_operator to 3 nodes, 3 racks and modify some timeouts in tests to avoid flakiness * Dump CassandraDatacenter and CassandraTask yaml to the build output also, Fixes #312 * Fix Completed() requeue logic in the cleanup task creation, modify scale_up test logic to ensure ScalingUp is set to False. Fixes #311 * Add missing CHANGELOG * Decrease config_change to 2 -> 4 nodes setup with 2 racks instead of 3 -> 6 * Ignore get -o errors, operator_upgrade 1.8.0 has no CassandraTask * Remove commented out lines * Increase timeouts in the tests to avoid flakiness. It seems increasing node count in certain tests caused the first check to pass while the cluster was not really ready and this caused the test to fail. Also, the kubectl outputs to the build directory missed the namespace * Modify config_change to use 1 rack for the testing * config_change cluster and dcName to variables * Missing dcName substitution
burmanm
added a commit
that referenced
this issue
Apr 5, 2022
* Another try * Update upgrade_operator to 3 nodes, 3 racks and modify some timeouts in tests to avoid flakiness * Dump CassandraDatacenter and CassandraTask yaml to the build output also, Fixes #312 * Fix Completed() requeue logic in the cleanup task creation, modify scale_up test logic to ensure ScalingUp is set to False. Fixes #311 * Add missing CHANGELOG * Decrease config_change to 2 -> 4 nodes setup with 2 racks instead of 3 -> 6 * Ignore get -o errors, operator_upgrade 1.8.0 has no CassandraTask * Remove commented out lines * Increase timeouts in the tests to avoid flakiness. It seems increasing node count in certain tests caused the first check to pass while the cluster was not really ready and this caused the test to fail. Also, the kubectl outputs to the build directory missed the namespace * Modify config_change to use 1 rack for the testing * config_change cluster and dcName to variables * Missing dcName substitution (cherry picked from commit f406df8)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is missing?
After running the test, the build directory has information such as operator logs, pod logs and some objects. However, we miss all our CRD statuses and that makes it difficult to track last status of an object, or which objects were actually created and how they looked.
Why do we need it?
To improve debug of test runs.
Environment
Cass Operator version:
**Anything else we need to know?**:Insert image tag or Git SHA here┆Issue is synchronized with this Jira Task by Unito
┆friendlyId: K8SSAND-1409
┆priority: Medium
The text was updated successfully, but these errors were encountered: