Server fails to copy client package when it's been updated
Bug #1155247 reported by
Javier Collado
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| UTAH |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
UTAH server fails to update the client package when it's been updated during
the provisioning phase.
The reason for this is that the server expects to find the packages that it
copies to the system under test after the installation succeeds. However, when
the packages are updated in between, then it no longer finds the files because
the file names include the revision number.
Some solution should be implemented to avoid the failures that are currently
happening that are because of a problem in the testing environment, not because
of a problem in the test cases themselves.
Revision history for this message
| Javier Collado (javier.collado) wrote | #1 |
| Changed in utah: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
To post a comment you must log in.
After some discussion in the mail list, there's some agreement on what a good
solution would be.
- The client package is no longer going to be included in the server package,
but downloaded to a shared location (if not available) to make sure it's
available when the distribution has been installed.
- The download location will be configurable to make it possible to switch
between stable and daily releases when needed.
- In the shared location only the latest two different versions will be kept
since that's the number of package versions that are expected to coexist in a
jenkins node running multiple jobs.