Activity log for bug #1566395

Date Who What changed Old value New value Message
2016-04-05 15:36:15 Sivasathurappan Radhakrishnan bug added bug
2016-04-05 15:36:28 Sivasathurappan Radhakrishnan swift: assignee Sivasathurappan Radhakrishnan (siva-radhakrishnan)
2016-04-05 15:38:39 Sivasathurappan Radhakrishnan description direct_get_suffix_hashes doesn't use replication_ip or replication_port for doing REPLICATE. Since we have an option of doing replication in separate network, we can add replication_ip while creating rings if not it will get filled in with the regular node's ip. direct_get_suffix_hashes doesn't use replication_ip and replication_port for doing REPLICATE. Since we have an option of doing replication in separate network, we can add replication_ip and port while creating rings if not it will get filled in with the regular node's ip.
2016-04-05 15:40:13 Sivasathurappan Radhakrishnan description direct_get_suffix_hashes doesn't use replication_ip and replication_port for doing REPLICATE. Since we have an option of doing replication in separate network, we can add replication_ip and port while creating rings if not it will get filled in with the regular node's ip. direct_client.direct_get_suffix_hashes(swift/common/direct_client.py) doesn't use replication_ip and replication_port for doing REPLICATE. Since we have an option of doing replication in separate network, we can add replication_ip and port while creating rings if not it will get filled in with the regular node's ip.
2016-04-05 15:50:17 Sivasathurappan Radhakrishnan description direct_client.direct_get_suffix_hashes(swift/common/direct_client.py) doesn't use replication_ip and replication_port for doing REPLICATE. Since we have an option of doing replication in separate network, we can add replication_ip and port while creating rings if not it will get filled in with the regular node's ip. direct_client.direct_get_suffix_hashes doesn't use replication_ip and replication_port for doing REPLICATE. Since we have an option of doing replication in separate network, we can add replication_ip and port while creating rings if not it will get filled in with the regular node's ip.
2016-04-05 16:09:34 clayg swift: status New Confirmed
2016-04-05 16:09:39 clayg swift: importance Undecided Low
2016-04-05 22:57:25 OpenStack Infra swift: status Confirmed In Progress
2016-04-12 10:29:34 OpenStack Infra swift: status In Progress Fix Released
2016-04-21 16:55:47 OpenStack Infra tags in-feature-crypto
2016-05-31 23:39:57 OpenStack Infra tags in-feature-crypto in-feature-crypto in-feature-hummingbird