Pulp 2 13 4 Test Result Summary » History » Sprint/Milestone 2
pthomas@redhat.com, 09/25/2017 05:51 PM
1 | 1 | pthomas@redhat.com | # Pulp 2 13 4 Test Result Summary |
---|---|---|---|
2 | |||
3 | Summary |
||
4 | |||
5 | Started On: September 15 , 2017 |
||
6 | Finished On: September 25, 2017 |
||
7 | Version: 2.13.5 |
||
8 | Result : Success |
||
9 | Build URL: N/A |
||
10 | Summary |
||
11 | |||
12 | This release included bug fixes. The QE tasks in the release process include making sure automation jobs pass and upgrade automation jobs pass. There were no new GitHub issues filed. The bugs included were part of 2.14 and have already been filed. |
||
13 | |||
14 | Pulp QE approve the release of pulp 2.13.4 |
||
15 | |||
16 | Beta History |
||
17 | Beta1 : September 15, 2017 |
||
18 | |||
19 | Issues Addressed |
||
20 | |||
21 | ~~~ |
||
22 | Pulp |
||
23 | 2874 Race condition during applicability regeneration for consumers with same profile |
||
24 | 2903 Process Recycling feature causes HTTP event notifier to be unreliable |
||
25 | 2734 task group never quite finishes if pulp is restarted in the middle of task run |
||
26 | 2927 Messages in resource manager queue are not persisted after restarting Qpid and cause tasks never start |
||
27 | ~~~ |
||
28 | |||
29 | ~~~ |
||
30 | Docker Support |
||
31 | 3010 Can't sync Docker images |
||
32 | ~~~ |
||
33 | |||
34 | The github issues as the following. |
||
35 | |||
36 | https://github.com/PulpQE/pulp-smash/issues/714 |
||
37 | https://github.com/PulpQE/pulp-smash/issues/715 |
||
38 | https://github.com/PulpQE/pulp-smash/issues/768 |
||
39 | |||
40 | QE was not able to do an upgrade of pulp to pulp 2.13.4 on a satellite6.3 due to a migration issue. |
||
41 | |||
42 | 2 | pthomas@redhat.com | Migrations in downstream to be different a bit is because in 6.2 a lot of cherry picks were required and some of them contained migrations. So in Satellite order of migrations is different and for that reason, we had to re-number them. Which means in order to upgrade we would have to apply the patches and then do an upgrade. |
43 | |||
44 | We will continue to pursue this task after the upstream release and report any failures. |