Skip to content

Conversation

@evgenyz
Copy link
Contributor

@evgenyz evgenyz commented Oct 15, 2025

Bash remediations require PATH to be inherited by the oscap process to work correctly.

@jan-cerny in main we still have "OSCAP_BOOTC_BUILD": "YES" in the environment:

env = {**os.environ, "OSCAP_PREFERRED_ENGINE": "SCE", "OSCAP_BOOTC_BUILD": "YES"}

So I've put it back here. Should I instead remove it from both branches?

@evgenyz evgenyz added the 1.3 Related to OpenSCAP 1.3.x version label Oct 15, 2025
@evgenyz evgenyz added this to the 1.3.13 milestone Oct 15, 2025
@jan-cerny
Copy link
Member

@evgenyz

SCAP content in ComplianceAsCode no longer depends on the OSCAP_BOOTC_BUILD environment variable. It has been removed from content in ComplianceAsCode/content#12988.

In OpenSCAP, we have also removed this variable, by #2201. The PR is at the maint-1.3 branch therefore the patch will be propagated to main branch by merge before the next release.

Bash remediations require PATH to be inherited by the
oscap process to work correctly.
@evgenyz evgenyz force-pushed the fix-oscap-im-env-1.3 branch from c7e3a61 to 9d0b404 Compare October 16, 2025 12:08
@evgenyz
Copy link
Contributor Author

evgenyz commented Oct 16, 2025

PR is now fixed.

@jan-cerny
Copy link
Member

This is a backport of #2253 to maint-1.3 and it fixes #2242 on maint-1.3. Am I correct?

@jan-cerny jan-cerny self-assigned this Oct 20, 2025
@evgenyz
Copy link
Contributor Author

evgenyz commented Oct 29, 2025

This is a backport of #2253 to maint-1.3 and it fixes #2242 on maint-1.3. Am I correct?

Yes, that's correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

1.3 Related to OpenSCAP 1.3.x version

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants