[FOLIO-2787] upgrade ref envs to Okapi 4.x Created: 08/Sep/20 Updated: 28/Sep/20 Resolved: 28/Sep/20 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Jakub Skoczen | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | DevOps: Sprint 97 | ||||||||
| Development Team: | FOLIO DevOps | ||||||||
| Description |
|
See
|
| Comments |
| Comment by John Malconian [ 10/Sep/20 ] |
|
I notice in my testing after unpinning okapi in ansible that okapi 3 is still installed. It looks like the folioci apt config on focal is still configured to use the xenial repo. deb "https://repository.folio.org/packages/ubuntu" "xenial"/ This makes sense I guess since we still wanted Okapi 3 installed until okapi 4 was ready. Will need to update this to point to the focal repo. |
| Comment by John Malconian [ 10/Sep/20 ] |
|
There is an issue with the okapi 4.1.1 deb package. Specifically, in the /usr/share/folio/okapi/bin/okapi.sh startup script: VERSION=$("$JAVA" -version 2>&1 | awk -F '"' '/version/ { print $2 }' \
| awk -F '.' '{ print $2 }')
if [ "$VERSION" -lt "8" ]; then
echo "Java version 8 or higher is required."
exit 0
fi
The command 'java -version 2>&1 | awk -F '"' '/version/ { print $2 }' | awk -F '.' '{ print $2 }'' returns '0' with openjdk-11. 'java -version' output might be slightly different than it was with openjdk-8. Going to need a bugfix release of okapi. |
| Comment by John Malconian [ 10/Sep/20 ] |
|
Created PR https://github.com/folio-org/okapi/pull/969 with fix. |
| Comment by John Malconian [ 15/Sep/20 ] |
|
Adam Dickmeiss merged the fix (removed Java version checking from okapi startup script) to master. A new package will be available when the next Okapi release is made. |
| Comment by John Malconian [ 24/Sep/20 ] |
|
The 'okapi-secure' folio-ansible role fails on task 'name: Check if mod-users and mod-permissions are already enabled on supertenant'. GET request to 'http://10.36.1.106:9130/_/proxy/tenants/supertenant/modules/mod-users-17.1.1-SNAPSHOT.146' generates a 403 - 'Access requires permission: okapi.proxy.tenants.modules.enabled.get'. I assume this is related to the changes made in https://folio-org.atlassian.net/browse/OKAPI-835 |
| Comment by John Malconian [ 25/Sep/20 ] |
|
All needed changes to folio-ansible are on branch 'FOLIO-2787-unpin-okapi' and we have a successful folio-snapshot-test build. Will merge these changes and unpin Okapi on Monday. |
| Comment by John Malconian [ 28/Sep/20 ] |
|
Unpinned Okapi today. Next set of reference builds should include Okapi 4. See https://github.com/folio-org/folio-ansible/pull/376 for changes to folio-ansible. |