We need to use previous release mirror as a primary mirror during development cycle
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Sergey Kulanov |
Bug Description
Detailed bug description:
When we deploy with mirror http://
There is a consistency problem with currently created mirror for a new release.
When we create mirror for new release - it is a snapshot of some state.
And when we try to use that mirror we get an error because iso is shipped with another mirror.
Steps to reproduce:
Run tests which use mirror during development cycle when version mirror is not ready [2] and [3]
Expected results:
Environment is deployed with needed packages
Actual result:
Packages are not found/wrong version.
Workaround:
There are number of workarounds like update repo settings, update fuel-mirror config.
Impact:
We can not track packages errors during development cycle.
Description of the environment:
Any fuel deployment.
Additional information:
We can update fuel-mirror or repository settings, but it would be hack on the product, which should not exist.
[0] http://
[1] http://
[2] https:/
[3] https:/
description: | updated |
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
assignee: | Fuel build team (fuel-build) → Sergey Kulanov (skulanov) |
tags: | added: feature |
Changed in fuel: | |
status: | Confirmed → New |
Changed in fuel: | |
status: | New → Won't Fix |
Changed in fuel: | |
assignee: | Fuel build team (fuel-build) → Sergey Kulanov (skulanov) |
status: | Won't Fix → In Progress |
That should be fixed in 10.0 with data-driven deployment. We should test it with newly implemented deploy tool