Skip to content

Add stackviz integration for tempest test results #3617

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.

Sign up for GitHub

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

Jump to bottom
Closed
sauragar wants to merge 3 commits into from
Closed

Add stackviz integration for tempest test results #3617

sauragar wants to merge 3 commits into from

Conversation

@sauragar
Copy link

@sauragar sauragar commented Jan 22, 2026

This commit adds automatic stackviz HTML report generation for tempest test results in the test_operator role.

Changes:

  • Add generate-stackviz.yml task file to handle stackviz generation
  • Integrate stackviz generation into run-test-operator-job.yml
  • Add cifmw_test_operator_generate_stackviz config variable
  • Add STACKVIZ_INTEGRATION.md documentation

The integration automatically:

  1. Finds tempest_results.subunit.gz in collected logs
  2. Decompresses the subunit file
  3. Runs stackviz-export to generate interactive HTML
  4. Stores output in <artifacts_basedir>/stackviz/html/

Users can disable this feature by setting:
cifmw_test_operator_generate_stackviz: false

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 22, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign pojadhav for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@softwarefactory-project-zuul
Copy link

softwarefactory-project-zuul bot commented Jan 22, 2026

Merge Failed.

This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset.
Warning:
Error merging github.com/openstack-k8s-operators/ci-framework for 3617,d4f80341202e7fb0f8edeedb7318937835e0eaa3

@sauragar @claude
Add stackviz integration for tempest test results
112ec6b 
This commit adds automatic stackviz HTML report generation for
tempest test results in the test_operator role.

Changes:
- Add generate-stackviz.yml task file to handle stackviz generation
- Integrate stackviz generation into run-test-operator-job.yml
- Add cifmw_test_operator_generate_stackviz config variable
- Add STACKVIZ_INTEGRATION.md documentation

The integration automatically:
1. Finds tempest_results.subunit.gz in collected logs
2. Decompresses the subunit file
3. Runs stackviz-export to generate interactive HTML
4. Stores output in <artifacts_basedir>/stackviz/html/

Users can disable this feature by setting:
cifmw_test_operator_generate_stackviz: false

Signed-off-by: Saurabh Agarwal <sauragar@redhat.com>
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@sauragar sauragar force-pushed the feature/stackviz-integration branch from d4f8034 to 112ec6b Compare January 23, 2026 07:59
michburk
michburk requested changes Jan 23, 2026
View reviewed changes
Copy link
Contributor

@michburk michburk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd be interested in seeing what the stackviz report looks like. Have you run these changes and generated an example report? If you need to include a link to somewhere downstream, please share the link via a comment on a jira ticket. Be sure to mark that comment as Restricted to Red Hat Employee, then share the jira link here.

Additionally, please include [test_operator] at the beginning of the commit title.

Thanks!

roles/test_operator/defaults/main.yml
cifmw_test_operator_delete_logs_pod: false
cifmw_test_operator_privileged: true
cifmw_test_operator_selinux_level: "s0:c478,c978"
cifmw_test_operator_generate_stackviz: true
Copy link
Contributor

@michburk michburk Jan 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[blocking] Missing a new entry in roles/test_operator/README.md describing this var

roles/test_operator/tasks/STACKVIZ_INTEGRATION.md
@@ -0,0 +1,120 @@
# Stackviz Integration for Tempest Results
Copy link
Contributor

@michburk michburk Jan 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[blocking] Don't put this markdown file in the tasks directory. Additionally, I think a lot of the information in this file is unnecessary/irrelevant. Maybe include a bit about stackviz in roles/test_operator/README.md instead?

roles/test_operator/tasks/generate-stackviz.yml Outdated
state: directory
mode: "0755"

- name: Check if stackviz is installed
Copy link
Contributor

@michburk michburk Jan 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[non-blocking] This isn't necessary, you can move the pip + stackviz installation outside of the block and remove this check.

roles/test_operator/tasks/generate-stackviz.yml Outdated
========================================
Location: {{ stackviz_html_path }}

To view the report, open the following file in your browser:
Copy link
Contributor

@michburk michburk Jan 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[blocking] Unless I'm mistaken, this file is primarily going to be accessed via the zuul logs. I think telling people to open it from their browser as if it were on their local machine is confusing and unhelpful.

@sauragar @claude
Address review feedback for stackviz integration
91fb448 
- Remove unnecessary stackviz installation check (pip is idempotent)
- Update success message to reference artifacts path instead of local file URL for Zuul CI context

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 29, 2026

Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@softwarefactory-project-zuul
Copy link

softwarefactory-project-zuul bot commented Jan 29, 2026

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/7d9db44b9d1a43ecbbe99b6e954fd194

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 26m 11s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 37m 36s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 2h 00m 31s
❌ cifmw-crc-podified-edpm-baremetal-minor-update FAILURE in 59m 23s
✔️ cifmw-multinode-tempest SUCCESS in 2h 06m 20s
✔️ cifmw-pod-zuul-files SUCCESS in 5m 27s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 9m 14s
✔️ cifmw-pod-pre-commit SUCCESS in 10m 12s
✔️ cifmw-molecule-test_operator SUCCESS in 2m 59s

@sauragar
Copy link
Author

sauragar commented Feb 3, 2026

Sorry this is another approach which I am using before but now I am going with the Generation of Stackviz report through Python code which I have done in another MR: #3642
So closing this one.
Thanks!!

@sauragar sauragar closed this Feb 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@michburk michburk michburk requested changes

Assignees

No one assigned

Labels

do-not-merge/contains-merge-commits

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@sauragar @michburk @openshift-merge-robot