Bug #48919
closedteuthology rgw qa/tasks/barbican.py
0%
Description
The barbican task has a 'year 2021" problem and no longer works. This is because it has a hard-coded expiration date of "2020-12-31T19:14:44.180394" which is now in the past. It should be based on the current time + X instead.
Symptom is: "Cannot create secret"
Updated by Marcus Watts over 3 years ago
I have a fix as part of this PR: https://github.com/ceph/ceph/pull/38605
Updated by Marcus Watts over 3 years ago
I have just this fix in
https://github.com/ceph/ceph/pull/39010
Updated by Casey Bodley about 3 years ago
- Status changed from New to Pending Backport
- Backport set to pacific
- Pull request ID set to 39010
Updated by Backport Bot about 3 years ago
- Copied to Backport #49044: pacific: teuthology rgw qa/tasks/barbican.py added
Updated by Nathan Cutler about 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Updated by Casey Bodley about 3 years ago
- Status changed from Resolved to Pending Backport
- Backport changed from pacific to octopus nautilus
also needed on octopus/nautilus
Updated by Backport Bot about 3 years ago
- Copied to Backport #49835: nautilus: teuthology rgw qa/tasks/barbican.py added
Updated by Backport Bot about 3 years ago
- Copied to Backport #49836: octopus: teuthology rgw qa/tasks/barbican.py added
Updated by Loïc Dachary about 3 years ago
- Backport changed from octopus nautilus to pacific octopus nautilus
Updated by Nathan Cutler about 3 years ago
Rejected nautilus backport as a consequence of the following thought process:
1. The fix being backported changes one file: qa/tasks/barbican.py
2. This file appears to have been introduced by https://github.com/ceph/ceph/pull/30218
3. https://github.com/ceph/ceph/pull/30218 went in for octopus and does not appear to have been backported to nautilus at all.
Updated by Loïc Dachary over 2 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".