skills.rest
openshift-eng
openshift-engOFFICIAL
Explore all skills by this author →
WebsiteGitHub

lvms:z-stream-report

Generate LVMS z-stream release urgency reports by correlating support dates, release recency, and JIRA bugs.

7|15|Updated Jan 23, 2026
Search Tags:#container registry#jira#lvms#cve triage#automation report#release urgency#support lifecycle
One-click install
npx skills add https://github.com/openshift-eng/edge-tooling --skill lvms-z-stream-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lvms:z-stream-report
Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/lvms/skills/z-stream-report
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill lvms-z-stream-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, curl, jq, skopeo, webfetch, grep, glob.

What problem does it solve?

It helps engineers determine which LVMS minor versions urgently need a z-stream release by combining support lifecycle timing, container release freshness, and active JIRA bug and CVE signals.

Core Features & Use Cases

  • Support-driven urgency: Calculates urgency based on the latest active LVMS support phase end date (maintenance or EUS terms) to highlight versions nearing end-of-support.
  • Release freshness analysis: Uses Red Hat container catalog tag history to measure days since the latest z-stream release for each supported version.
  • JIRA bug and security triage: Queries OCPBUGS for open Logical Volume Manager Storage bugs and vulnerabilities, classifies CVEs, and weights urgency by severity and priority.

Quick Start

Run /lvms:z-stream-report after setting JIRA_BASE_URL, JIRA_EMAIL, and JIRA_API_TOKEN so the skill can query JIRA and generate the urgency report.

Frequently Asked Questions about lvms:z-stream-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize LVMS z-stream releases using support lifecycle and open CVEs?▼

Prioritize LVMS z-stream releases by correlating Red Hat support lifecycle end dates with open JIRA bugs and CVEs. This generates an urgency report highlighting supported versions nearing end-of-support that require immediate release planning and risk triage.

What is the best way to automate LVMS CVE triage across supported versions?▼

Automate LVMS CVE triage by querying OCPBUGS via the JIRA v3 REST API to classify open vulnerabilities and bugs. This approach weights urgency by severity and priority to produce actionable release recommendations for edge platform engineering.

How do I check LVMS container release freshness using the Red Hat registry?▼

Check LVMS container release freshness by using registry tooling like skopeo to inspect container tag history. This calculates the days since the latest z-stream release for each supported version to measure update recency.

Do I need JIRA API credentials to generate an LVMS z-stream urgency report?▼

Yes, you need JIRA_BASE_URL, JIRA_EMAIL, and JIRA_API_TOKEN configured for Basic auth. These credentials allow the report automation to query the JIRA v3 REST API for open OCPBUGS and CVEs required to calculate release urgency scores.

Does this z-stream report work with Red Hat EUS and maintenance support phases?▼

Yes, the z-stream report works with Red Hat EUS and maintenance support phases. It calculates urgency based on the latest active support phase end date to specifically highlight LVMS versions nearing end-of-support.

Why does my LVMS z-stream release planning fail to account for security deadlines?▼

LVMS z-stream release planning fails to account for security deadlines when it lacks correlation between support lifecycle dates and open CVEs. Integrating JIRA bug triage with container tag freshness resolves this gap.

Related Skills

Explore More Software Engineering Skills→
XAIHTXAIHT
14

jira

Automate Jira issue management via the Jira REST API v3.

Official
Intermediate
openshift-engopenshift-eng
7

microshift-release:release-versions

Determine MicroShift release availability and generate a structured Markdown report.

Official
Intermediate
openshift-engopenshift-eng
112

OCPBUGS Jira Conventions

Automate OCPBUGS Jira bug creation with version fields and labels.

Community
Basic
RHEcosystemAppEngRHEcosystemAppEng
48

red-hat-product-lifecycle

Query Red Hat product lifecycle phases and support end dates via API.

Official
Intermediate