Do not use fixed timeouts for image building
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Triaged
|
Low
|
Fuel Sustaining | ||
Mitaka |
Won't Fix
|
Low
|
Fuel Python (Deprecated) | ||
Newton |
Triaged
|
Low
|
Fuel Sustaining |
Bug Description
Deployment finishes with error due to timeout when creating Ubuntu images with debootstrap for nodes.
Timeout was too short in my case (3600s = 60min) - perhaps it could be configurable?
Deployment failed with the following error: http://
1) Create env (iso fuel-6.1-361):
- Ubuntu HA Neutron with VLAN segmentation
- 1x Controller, Storage - Ceph OSD
- 2x Compute, Storage - Ceph OSD
(proably any Ubuntu configuration will be affected)
2) Start deployment.
Expected result:
- deployed cluster
Actual result:
- deployment error
Suspected reason:
- deboostrap is not able to finish creating an image on fuel master before the timeout (3600s) - due to slow performance of my test system but it may happen also on more powerful systems e.g. due to network overload.
Manual FIX:
- after deployment error wait for deboostrap to finish creating the image and redeploy (the image will be found and used by fuel without need to recreate it)
Changed in fuel: | |
importance: | Undecided → High |
tags: | added: feature |
summary: |
- Deployment error due to timeout: [600] Error running provisioning: - Failed to execute hook . + Do not use fixed timeouts for image building |
Changed in fuel: | |
importance: | Medium → Wishlist |
status: | New → Confirmed |
tags: | added: feature-image-based |
Changed in fuel: | |
milestone: | 7.0 → next |
Changed in fuel: | |
milestone: | next → 7.0 |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
tags: | removed: feature |
Changed in fuel: | |
status: | Confirmed → Triaged |
importance: | Wishlist → Low |
tags: | added: area-python |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
Marek, 3600 should more than enough too create a base debian/ubuntu chroot. Please, evaluate your environment/network performance.