Release Notes
Issues discovered in testing
Issues discovered in testing:
| Discovered by | Issue | bb | db | nw | af | |
|---|---|---|---|---|---|---|
| 1 | Bill | DuraCloud integration tests failing due to Spring Security's use of StrictHttpFirewall which does not allow the use of percent symbols.
|  | |||
| 2 | Bill | When viewing snapshot totals in the UI, the number of snapshots in the spaces list doesn't match the number in the snapshot totals table. This is because only complete snapshots are included in the total. I expect this may be confusing to users (as it was to me initially). The simple resolution would be to adjust the totals table to capture details from all snapshots (complete and in-process). A follow-on ticket could be opened to expand the table to specify details for total, complete, and in-process snapshots.
| | |||
| 3 | Andy | The integration test for the Swift S3 endpoint is failing, because the CONTENT_RANGE header is being filtered out. Adding it to the list of valid Swift metadata fixes the issue.
| | |||
| 4 | Danny | Management Console: When the jsessionid is used for session management it causes an error due to the Spring Security firewall | | |||
| 5 | Danny | Management Console: Invitation email contains a double slash, which results in an error from the Spring Security firewall when clicking on the link |
(still) | |||
| 6 | Bill | If S3 has an issue retrieving a bucket in an account, then the DurAdmin UI isn't able to display the space listing. The error in the logs: ERROR 2021/12/09 20:41:48 [http-nio-8080-exec-21] (SpacesController.java:92) [getSpacesAsJson()] - Error attempting to get space ACLs 'contentwriter-test-space-33162' due to: null In this case, spaces were deleted from S3, but apparently they weren't removed completely or correctly, so S3 is sending back a bucket listing that includes buckets that fail when you attempt to access them (like to get metadata for ACLs). | JIRA ticket needed | |||
| 7 | Danny | Duraspace refs in duradmin and synctoolui links: https://github.com/duracloud/duracloud/pull/163 | | |||
| 8 | Bill | On Windows, the SyncTool installer for 7.1.0-SNAPSHOT is flagged as a potential security risk when starting it up. We should check to see if the released 7.1.0 version has the same warning, and if so, create a JIRA ticket to look into it. | JIRA ticket needed |
Testing of Completed Issues
| Item | bb | db | nw | af | Status |
|---|---|---|---|---|---|
DURACLOUD-1319 - Getting issue details... STATUS | | | N/A |  | |
DURACLOUD-1310 - Getting issue details... STATUS | | | | ||
DURACLOUD-1309 - Getting issue details... STATUS | N/A | N/A | | | |
DURACLOUD-1308 - Getting issue details... STATUS | - the new log messages are present at least | N/A | N/A | | |
DURACLOUD-1306 - Getting issue details... STATUS | | | N/A | | |
DURACLOUD-1299 - Getting issue details... STATUS | | | N/A | | |
DURACLOUD-1298 - Getting issue details... STATUS | | | | | |
DURACLOUD-1297 - Getting issue details... STATUS | | | | | |
DURACLOUD-1292 - Getting issue details... STATUS | N/A | N/A | N/A | | |
DURACLOUD-1268 - Getting issue details... STATUS | | | | ||
DURACLOUD-1258 - Getting issue details... STATUS | | | | ||
DURACLOUD-1257 - Getting issue details... STATUS | | | | ||
DURACLOUD-1150 - Getting issue details... STATUS | | | N/A | | |
DURACLOUD-1317 - Getting issue details... STATUS | | N/A | | ||
DURACLOUD-1279 - Getting issue details... STATUS | #2 | | N/A | | |
DURACLOUD-1304 - Getting issue details... STATUS | | | | ||
DURACLOUD-1321 - Getting issue details... STATUS | | | | | |
DURACLOUD-1313 - Getting issue details... STATUS | | | | | |
DURACLOUD-1330 - Getting issue details... STATUS | | | | ||
DURACLOUD-1278 - Getting issue details... STATUS | N/A | N/A | N/A | |
Regression Testing
| Task | bb | db | nw | af |
|---|---|---|---|---|
| Perform Regression Tests |  | I verified that we can build the installers and the osx installer works. I also ran the rest api scripts | | |
Use ZAProxy to perform a security analysis
| Report summary:
|
Build Tests
| Test | bb | db | nw | af |
|---|---|---|---|---|
| Update all dependencies to 7.1.0-SNAPSHOT versions | |
| | |
| mvn clean install (full build + integration tests) - DuraCloud DB | | | | |
| mvn clean install (full build + integration tests) - DuraCloud | #1 | | | |
| mvn clean install (full build + integration tests) - Management Console | | | | |
| mvn clean install (full build + integration tests) - Mill | | | | |
| mvn clean install (full build + integration tests) - Snapshot | | | | N/A |
Release Actions - for each baseline (in this order): DB, DuraCloud, MC, Mill, Snapshot
- Complete testing
- Perform version release (v7.1.0): https://github.com/duracloud/deployment-docs/blob/master/release-new-version.md
DuraCloud DB 7.1.0
a note here: the artifacts get signed and published when the main branch is pushed. I didn't realize that and manually signed and published the artifacts. That is why the publish to sonatype failed on the main branch: the artifacts were already present.
DuraCloud 7.1.0
# A manual deploy was required. It was not clear what the issue was sonatype - apparently a validation rule failed when trying to close the staging repository. # To create the elastic beanstalk zip: cd target zip -r duracloud-elasticbeanstalk-7.1.0-33fa7cd.zip dura* .ebextensions ROOT.war .platform # Then manually upload to github release page # I manually created the installers and uploaded them to the release page.
- DuraCloud MC 7.1.0
- DuraCloud Mill 4.1.0
- DuraCloud Bridge 3.1.0
- Deploy release zip to production Beanstalk
- Create release notes in Github
- Update documentation
- Update download links to point to Github release
