Provisioning image isn't rebuilt if packages list was changed

Bug #1578565 reported by Artem Panchenko
This bug report is a duplicate of:  Bug #1485997: [IBP] Non-dynamic image. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
Fuel build team
Mitaka
Won't Fix
Medium
Fuel build team

Bug Description

Provisioning image isn't rebuilt if packages list was changed after environment deployment, for example I tried to add 'nmap' to the packages list and provision new nodes, but old target image was used:

http://paste.openstack.org/show/496197/

Looks like Fuel developers are aware about this issue: https://github.com/openstack/fuel-agent/blob/d1fc735650760b8622bdcd6a3234ccc5f3a8d8d1/fuel_agent/manager.py#L1026-L1027

Steps to reproduce:

1. Deploy any environment with default packages list
2. Add 'nmap' to the packages list on 'settings' tab
3. Add new node to the environment and provision it
4. Go to the new provisioned node and check 'nmap' command

Expected result:

`nmap` command is available

Actual result:

command in not found, 'nmap' package is not installed

Workaround:

remove target images manually to force rebuilding

Changed in fuel:
status: New → Confirmed
assignee: nobody → Fuel build team (fuel-build)
tags: added: area-build
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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