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

Test on Fedora 41 #508

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Conversation

SohamJuneja
Copy link

This PR solves #503 by introducing support for Fedora 41 in the Molecule testing environment. The following changes have been made:

Updated molecule.yml: Added Fedora 41 as a platform in the test matrix for the Molecule configuration.
Verified Setup: Successfully pulled the fedora:41 Docker image and confirmed its functionality by running basic commands (uname -a, cat /etc/os-release) inside the container to ensure that Fedora 41 is set up correctly.
Test Validation: Ensured that Fedora 41 runs as expected in the Docker container, confirming that the setup is valid for testing purposes.

Testing done

Submitter checklist

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests - that demonstrates feature works or fixes the issue

@SohamJuneja SohamJuneja requested a review from a team as a code owner January 28, 2025 06:48
molecule/default/molecule.yml Outdated Show resolved Hide resolved
@MarkEWaite MarkEWaite changed the title Add support for Fedora 41 in Molecule testing environment Test on Fedora 41 Jan 29, 2025
The fedora:41 container image does not have the necessary
configuration for our use in Molecule.

The dokken/fedora-41:latest image is the better choice
for this use.

Tested on my local computer with:

python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
molecule test
deactivate
@SohamJuneja
Copy link
Author

@MarkEWaite Apologies for the oversight, and thank you for stepping in to make the necessary changes. Regarding the next steps, how would you suggest we proceed from here?

@MarkEWaite
Copy link
Contributor

Regarding the next steps, how would you suggest we proceed from here?

The latest failures should be visible when you run the tests using the instructions in the README. If you can see those failures, then you can start diagnosing what might be causing those failures.

I'm out of office until next week, so won't be able to spend any time on it until next week at the earliest.

2 similar comments
@MarkEWaite
Copy link
Contributor

Regarding the next steps, how would you suggest we proceed from here?

The latest failures should be visible when you run the tests using the instructions in the README. If you can see those failures, then you can start diagnosing what might be causing those failures.

I'm out of office until next week, so won't be able to spend any time on it until next week at the earliest.

@MarkEWaite
Copy link
Contributor

Regarding the next steps, how would you suggest we proceed from here?

The latest failures should be visible when you run the tests using the instructions in the README. If you can see those failures, then you can start diagnosing what might be causing those failures.

I'm out of office until next week, so won't be able to spend any time on it until next week at the earliest.

@SohamJuneja
Copy link
Author

@MarkEWaite Thanks for the update! I'll go through the test failures as per the README instructions and start diagnosing the issue

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