HugePages don't support Life Cycle Management
Bug #1584831 reported by
Ksenia Svechnikova
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel Sustaining | ||
Bug Description
Versions of components: Fuel-10
Detailed bug description: 1Gb HugePages are configuring in grub in provisioning stage, so they couldn't be changes using usual flow of deploy-changes
Steps to reproduce:
1. Prepare env with nodes that support 1Gb HugePages
2. Configure HP on each compute node
3. Deploy cluster
4. Change number of 1Gb HP on one compute node
5. Run Deploy changes
Expected results: New number of 1 Gb HP is allocated on compute node
Actual result: number of 1 Gb HP isn't changes
1Gb HugePages are configured on provision stage through kernel parameters [0]
| description: | updated |
| summary: |
- HugePages doesn't support Task Based Deployment + HugePages doesn't support Life Cycle Management |
| summary: |
- HugePages doesn't support Life Cycle Management + HugePages don't support Life Cycle Management |
| Changed in fuel: | |
| status: | New → Confirmed |
| assignee: | nobody → Fuel Customer Enablement Team (fuel-customer-enablement) |
| description: | updated |
| tags: | added: area-python |
Revision history for this message
| Arthur Svechnikov (asvechnikov) wrote | #1 |
| Changed in fuel: | |
| assignee: | Fuel LCM Team (fuel-lcm) → Fuel Sustaining (fuel-sustaining-team) |
To post a comment you must log in.
Kernel update to the version 3.16+ should resolve this issue