...
- List of all issues included in release
- In DuraCloud app Beanstalk configuration, an Environment Property named AWS_REGION must be set to the default AWS region value.
- In Management Console, ensure that no accounts have storage providers with type "DPN"
- In bridge config init JSON document: change "dpnEmailAddresses" to "targetStoreEmailAddresses"
- In bridge database, update state for any in-process snapshot or restore actions
- Snapshot:
- WAITING_FOR_DPN -> REPLICATING_TO_STORAGE
- UPDATE snapshot.snapshot SET status="REPLICATING_TO_STORAGE" WHERE status="WAITING_FOR_DPN";
- WAITING_FOR_DPN -> REPLICATING_TO_STORAGE
- Restore
WAITING_FOR_DPN -> RETRIEVING_FROM_STORAGE
UPDATE snapshot.restoration SET status="RETRIEVING_FROM_STORAGE" WHERE status="WAITING_FOR_DPN";
DPN_TRANSFER_COMPLETE -> STORAGE_RETRIEVAL_COMPLETE
- UPDATE snapshot.restoration SET status="STORAGE_RETRIEVAL_COMPLETE" WHERE status="DPN_TRANSFER_COMPLETE";
VERIFYING_DPN_TO_BRIDGE_TRANSFER -> VERIFYING_RETRIEVED_CONTENT
- UPDATE snapshot.restoration SET status="VERIFYING_RETRIEVED_CONTENT" WHERE status="VERIFYING_DPN_TO_BRIDGE_TRANSFER";
- Snapshot:
...
| Issue | bb | db | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | (bill) I'm seeing a consistent build failure in the mill in SpaceLogTest.testWriteNoExistingLogsUTF8() which seems to be due to a mis-configuration of my local bash client (on Windows). The test passes with no issues when executed via my IDE. No action to take here, just recording for historical purposes. | ||||||||||
| 2 | (bill) In the dev environment, where all instances are running in us-west-2, the setting of AWS_REGION to us-east-1 in the DuraCloud beanstalk app didn't result in duplicated spaces being created in Virginia. The reason was because there was no region set for the storage provider in the Management Console and the Mill was using an AWS_REGION value (from its environment.properties file) set to us-west-2. Changing the storage provider region in the MC didn't resolve the problem because of the s3Client cache, as described here:
|
Testing of Completed Issues
...