Bug 2139452
| Summary: | OC deployment with minimal image on Ceph nodes failed | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Giulio Fidente <gfidente> |
| Component: | openstack-tripleo-puppet-elements | Assignee: | OSP Team <rhos-maint> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | nlevinki <nlevinki> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 16.1 (Train) | CC: | johfulto, jslagle, mburns |
| Target Milestone: | z10 | Keywords: | Triaged |
| Target Release: | 16.1 (Train on RHEL 8.2) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-09-18 19:45:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2138203 | ||
| Bug Blocks: | |||
Red Hat OpenStack Platform 16.1 was retired on April 30, 2024. This has been resolved in 16.2. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |
Description of problem: The deployment failed after the OS was deployed and the NICs were configured. The deployment was with TLS everywhere enabled. The error message for all the ceph nodes was: FATAL | Install tuned | ceph-3 | error={"changed": false, "failures": ["No package tuned-prof iles-cpu-partitioning available."], "msg": "Failed to install some of the specified packages", "rc": 1, "results": []} Version-Release number of selected component (if applicable): rhosp-director-images-16.2-20220902.2.el8ost.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy environment with minimal image 2. 3. Actual results: The deployment fails Expected results: The rpm should be installed on the image beforehand and the deployment concluded successfuly Additional info: