Skip to content

Remove remaining OS_CONF_RELEASE_PATH usage on ubuntu-jammy branch #679

Description

@coderabbitai

Summary

A follow-up fix is needed on the ubuntu-jammy branch to finish the transition away from OS_CONF_RELEASE_PATH and consistently use BPM_RELEASE_PATH.

Context

PR #678 updated acceptance-tests/ipv4director/smoke/smoke_suite_test.go to upload the BPM release instead of the OS config release, but other related references still remain and should be cleaned up on the ubuntu-jammy branch as part of the merge-forward workflow.

Requested by: @aramprice

Affected areas

  • acceptance-tests/ipv4director/auditd/smoke_suite_test.go
  • ci/tasks/test-stemcell.sh

Required changes

  • Update the auditd smoke suite to read BPM_RELEASE_PATH instead of OS_CONF_RELEASE_PATH.
  • Remove the legacy OS_CONF_RELEASE_PATH export from the test-stemcell task if it is no longer needed.
  • Keep the release upload/setup flow aligned across the acceptance test suites.

Rationale

The current PR switched one smoke suite over to BPM, but leaving the older OS_CONF_RELEASE_PATH references behind creates inconsistent setup behavior and leaves a retired variable in circulation.

Acceptance criteria

  • No remaining required usage of OS_CONF_RELEASE_PATH in the acceptance test setup for this flow on ubuntu-jammy.
  • The auditd smoke suite uses BPM_RELEASE_PATH.
  • ci/tasks/test-stemcell.sh no longer exports the legacy OS config release path for this scenario.
  • The issue is fixed on ubuntu-jammy so it can merge forward cleanly.

Backlinks

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions