Back to bug 1493476
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Matt Benjamin (redhat) | 2017-09-20 11:21:25 UTC | Status | NEW | ASSIGNED |
| CC | sshreeka | |||
| Flags | needinfo?(sshreeka) | |||
| Shreekar | 2017-09-20 11:46:35 UTC | Flags | needinfo?(sshreeka) | |
| Matt Benjamin (redhat) | 2017-10-05 18:10:36 UTC | Target Release | 3.0 | 3.1 |
| Harish NV Rao | 2017-10-09 09:26:56 UTC | CC | hnallurv | |
| Blocks | 1494421 | |||
| Doc Type | If docs needed, set a value | Release Note | ||
| Bara Ancincova | 2017-10-12 12:44:57 UTC | Docs Contact | bancinco | |
| Doc Type | Release Note | Known Issue | ||
| Flags | needinfo?(mbenjamin) | |||
| Matt Benjamin (redhat) | 2017-10-12 12:50:57 UTC | Doc Text | Cause: RGW does not currently accept a value of '0' for the Expiration, Days lifecycle configuration parameter. Consequence: Setting an expiration of '0 days' cannot be used as a mechanism to trigger background expiration of objects. Workaround (if any): Delete objects directly. | |
| Flags | needinfo?(mbenjamin) | |||
| Matt Benjamin (redhat) | 2017-10-12 12:51:52 UTC | Doc Text | Cause: RGW does not currently accept a value of '0' for the Expiration, Days lifecycle configuration parameter. Consequence: Setting an expiration of '0 days' cannot be used as a mechanism to trigger background expiration of objects. Workaround (if any): Delete objects directly. | Cause: RGW does not currently accept a value of '0' for the Expiration, Days lifecycle configuration parameter. Consequence: Setting an expiration of '0 days' cannot be used as a mechanism to trigger background delete of objects. Workaround (if any): Delete objects directly. |
| Bara Ancincova | 2017-10-12 13:10:23 UTC | Doc Text | Cause: RGW does not currently accept a value of '0' for the Expiration, Days lifecycle configuration parameter. Consequence: Setting an expiration of '0 days' cannot be used as a mechanism to trigger background delete of objects. Workaround (if any): Delete objects directly. | .The `Expiration, Days` parameter cannot be set to `0` The Ceph Object Gateway does not accept the value of `0` for the `Expiration, Days` configuration parameter. Consequently, setting the expiration to `0` cannot be used to trigger background delete operation of objects. To work around this problem, delete objects directly. |
| Flags | needinfo?(mbenjamin) | |||
| Matt Benjamin (redhat) | 2017-10-12 13:25:39 UTC | Doc Text | .The `Expiration, Days` parameter cannot be set to `0` The Ceph Object Gateway does not accept the value of `0` for the `Expiration, Days` configuration parameter. Consequently, setting the expiration to `0` cannot be used to trigger background delete operation of objects. To work around this problem, delete objects directly. | .The `Expiration, Days` S3 Lifecycle parameter cannot be set to `0` The Ceph Object Gateway does not accept the value of `0` for the `Expiration, Days` Lifecycle configuration parameter. Consequently, setting the expiration to `0` cannot be used to trigger background delete operation of objects. To work around this problem, delete objects directly. |
| Flags | needinfo?(mbenjamin) | |||
| Drew Harris | 2018-04-02 13:32:55 UTC | Priority | unspecified | medium |
| CC | anharris | |||
| Tejas | 2018-05-09 05:55:23 UTC | CC | tchandra | |
| Matt Benjamin (redhat) | 2018-05-09 15:23:28 UTC | Target Release | 3.1 | 3.* |
| PnT Account Manager | 2018-10-02 21:31:36 UTC | CC | owasserm | |
| Matt Benjamin (redhat) | 2019-03-06 00:12:30 UTC | Target Release | 3.* | 4.0 |
| Target Milestone | rc | z1 | ||
| RHEL Program Management | 2019-03-06 00:12:32 UTC | Target Release | 4.0 | 3.* |
| Matt Benjamin (redhat) | 2019-03-06 00:12:59 UTC | Target Release | 3.* | 4.0 |
| Matt Benjamin (redhat) | 2019-03-06 00:33:10 UTC | Summary | [ rgw ]: Enabling Lifecycle on a bucket, for expiration day=0, getting XML error instead of deleting object immediately | [ rgw ]: Enabling Lifecycle on a bucket, for expiration day=0, getting XML error |
| Giridhar Ramaraju | 2019-08-05 13:10:19 UTC | QA Contact | ceph-qe-bugs | hgurav |
| Hemant G | 2019-08-06 09:05:48 UTC | QA Contact | hgurav | tchandra |
| Gaurav Sitlani | 2019-10-10 07:11:14 UTC | CC | gsitlani | |
| Matt Benjamin (redhat) | 2019-10-10 15:39:03 UTC | Link ID | Ceph Project Bug Tracker 38389 | |
| Target Milestone | z1 | rc | ||
| Matt Benjamin (redhat) | 2019-10-11 17:27:13 UTC | Status | ASSIGNED | POST |
| Severity | low | medium | ||
| errata-xmlrpc | 2019-10-16 02:09:48 UTC | Status | POST | MODIFIED |
| CC | tserlin | |||
| Fixed In Version | ceph-14.2.4-14.el8cp | |||
| Status | MODIFIED | ON_QA | ||
| Bara Ancincova | 2019-12-10 10:44:19 UTC | Blocks | 1730176 | |
| Bara Ancincova | 2020-01-07 13:27:15 UTC | Fixed In Version | ceph-14.2.4-14.el8cp | ceph-14.2.4-14.el8cp, ceph-14.2.4-2.el7cp |
| Doc Text | .The `Expiration, Days` S3 Lifecycle parameter cannot be set to `0` The Ceph Object Gateway does not accept the value of `0` for the `Expiration, Days` Lifecycle configuration parameter. Consequently, setting the expiration to `0` cannot be used to trigger background delete operation of objects. To work around this problem, delete objects directly. | .The `Expiration, Days` S3 Lifecycle parameter can now be set to `0` The Ceph Object Gateway did not accept the value of `0` for the `Expiration, Days` Lifecycle configuration parameter. Consequently, setting the expiration to `0` could not be used to trigger background delete operation of objects. With this update, `Expiration, Days` can be set to `0` as expected. | ||
| Doc Type | Known Issue | Bug Fix | ||
| Flags | needinfo?(mbenjamin) | |||
| errata-xmlrpc | 2020-01-31 11:26:41 UTC | Status | ON_QA | RELEASE_PENDING |
| errata-xmlrpc | 2020-01-31 12:44:52 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2020-01-31 12:44:52 UTC | |||
| errata-xmlrpc | 2020-01-31 12:45:25 UTC | Link ID | Red Hat Product Errata RHBA-2020:0312 |
Back to bug 1493476