Skip to content
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.

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

(NEXMANAGE-1272) Always add /var/intel-manageability directory for SQLITE3 DB #642

Merged
merged 2 commits into from
Feb 27, 2025

Conversation

nmgaston
Copy link
Contributor

@nmgaston nmgaston commented Feb 27, 2025

PULL DESCRIPTION

/var/intel-manageability directory is required for SQLITE3. It was not getting created when using LUKS instead of the intel secret. This also creates the directory when LUKS is used.

Impact Analysis

Info Please fill out this column
Root Cause Using LUKS was bypassing creating the /var/intel-manageability directory which is required for sqlite3
Jira ticket NEXMANAGE-1272

CODE MAINTAINABILITY

  • Added required new tests relevant to the changes
  • Updated Documentation as relevant to the changes
  • PR change contains code related to security
  • PR introduces changes that break compatibility with other modules/services (If YES, please provide description)
  • Run go fmt or format-python.sh as applicable
  • Update Changelog
  • Integration tests are passing
  • If Cloudadapter changes, check Azure connectivity manually

Code must act as a teacher for future developers

@nmgaston nmgaston requested a review from gblewis1 as a code owner February 27, 2025 19:04
@nmgaston nmgaston changed the title Always add /var/intel-manageability directory for SQLITE3 DB (NEXMANAGE-1272) Always add /var/intel-manageability directory for SQLITE3 DB Feb 27, 2025
@nmgaston nmgaston merged commit 47f66d0 into develop Feb 27, 2025
7 checks passed
@nmgaston nmgaston deleted the NEXMANAGE-1272 branch February 27, 2025 20:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants