Fuel for OpenStack

[IBP] Non-dynamic image

Bug #1485997 reported by Aleksey Zvyagintsev
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
Fuel Sustaining
Fuel for OpenStack 10.0
Mitaka
Won't Fix
Medium
Fuel Python (Deprecated)
Fuel for OpenStack 9.0
Newton
Confirmed
Medium
Fuel Sustaining
Fuel for OpenStack 10.0

Bug Description

Work-flow:
1) Create env
2) Pass custom repo
3)Provision new env
IBP system populate images:
/var/www/nailgun/targetimages/env_*_ubuntu_1404_amd64*
4)Reset env
5)Update repo list
6)Provision env

Expecting result:
Fuel should re-create images, or atleast show related warning.

Actual result:
Fuel use old images w\o any warning.

Aleksey Zvyagintsev (azvyagintsev)
Changed in fuel:
importance: Undecided → Critical
Alexei Sheplyakov (asheplyakov)
Changed in fuel:
importance: Critical → Wishlist
Revision history for this message
Alexei Sheplyakov (asheplyakov) wrote :

Reusing existing images is a normal behavior.
You can easily remove them to force a rebuild.

Revision history for this message
Aleksey Zvyagintsev (azvyagintsev) wrote :

And how customer should understand that it is "normal" and what and where exactly i should remove this images?
I propose to add at least warning.

Revision history for this message
Alexander Gordeev (a-gordeev) wrote :

is it really expected that env reset will remove target images?

Changed in fuel:
assignee: nobody → Fuel Python Team (fuel-python)
tags: added: feature-image-based ibp
Revision history for this message
Aleksey Zvyagintsev (azvyagintsev) wrote :

No, expected that if user made some changes in env, which can affect\effect on IBP images, which has already created- user should be at least warned.

Ihor Kalnytskyi (ikalnytskyi)
Changed in fuel:
status: New → Confirmed
milestone: 7.0 → 8.0
Revision history for this message
Artem Panchenko (apanchenko-8) wrote :

I don't think this bug is new functionality request, because we didn't have such issue with deprecated classic provisioning. So changing its status to 'medium'. Also I agree with Aleksey (azvyagintsev) - if cloud administrator changes settings (e.g. repos list) after env reset, then he/she expects that all changes will be applied during new deployment.

@Documentation team, please add this bug to 7.0 release notes. Workaround is manual removal of images (on master node) after environment reset:

ENV_ID=1 find /var/www/nailgun/targetimages/ -name "env_$ENV_ID_*" -delete

where ENV_ID is id of OpenStack environment.

Changed in fuel:
importance: Wishlist → Medium
tags: added: release-notes
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to fuel-docs (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/223584

Olga Gusarenko (ogusarenko)
tags: added: release-notes-done rn7-0
removed: release-notes
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to fuel-docs (master)

Reviewed: https://review.openstack.org/223584
Committed: https://git.openstack.org/cgit/stackforge/fuel-docs/commit/?id=290baf9ff01bca0dfd0de9b13a6b5ca9b97d393c
Submitter: Jenkins
Branch: master

commit 290baf9ff01bca0dfd0de9b13a6b5ca9b97d393c
Author: OlgaGusarenko <email address hidden>
Date: Tue Sep 15 16:22:27 2015 +0300

    [RN 7.0] Non-dynamic image issue

    Adds Non-dynamic image known issue

    Change-Id: Ic1471edb41d6c7f40ac141422b4ec6a252797745
    Related-Bug:#1485997

Dmitry Pyzhov (dpyzhov)
no longer affects: fuel/8.0.x
Dmitry Pyzhov (dpyzhov)
tags: added: area-python
Dmitry Pyzhov (dpyzhov)
tags: added: feature
Changed in fuel:
milestone: 8.0 → 9.0
no longer affects: fuel/7.0.x
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.