Skip to content

Refresh compliance suite acceptance nodesets #252

Description

@silug

Summary

The compliance suite's beaker nodesets in `spec/acceptance/suites/compliance/nodesets/` are out of date relative to the rest of the module.

Evidence

After PR #238 deletes the EOL `amzn2.yml` and `centos8.yml` from this directory, the remaining files are:

  • `default.yml` — still targets CentOS 7 (`box: centos/7`, `platform: el-7-x86_64`, `puppet_collection: puppet7`). EL7 was dropped in 9.0.0.
  • `centos9.yml` — almost certainly also stale (`puppet7` default, possibly other drift), but at least the platform is supported.

The main suite's nodesets (`spec/acceptance/nodesets/`) were brought current as part of the EL10/openvox8 cleanup; this directory was missed.

Proposed Fix

  • Replace `default.yml` with an EL10 + `openvox8` target consistent with `spec/acceptance/nodesets/default.yml`.
  • Update `centos9.yml` (and consider whether to add full per-distro coverage matching the main suite — but per project convention, vagrant nodesets should be limited to one or two representatives, so a single `default.yml` may be sufficient).
  • Decide whether the compliance suite is still being run in CI. If not, this directory may be removable entirely.

Definition of Done

Compliance-suite nodesets target a currently-supported OS and default to `openvox8`, or the directory is removed if the suite is no longer maintained.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status
    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions