[FOLIO-3001] Add mod-bursar-export module to testing/snapshot envs Created: 08/Feb/21 Updated: 12/Feb/21 Resolved: 12/Feb/21 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Story | Priority: | P2 |
| Reporter: | Roman Leshchenko | Assignee: | David Crossley |
| Resolution: | Done | Votes: | 0 |
| Labels: | devops-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue links: |
|
||||||||
| Sprint: | DevOps: sprint 85, DevOps Sprint 107 | ||||||||
| Development Team: | FOLIO DevOps | ||||||||
| Description |
|
There is a new *mod-bursar-export
|
| Comments |
| Comment by Roman Leshchenko [ 08/Feb/21 ] |
|
Hi Jakub Skoczen |
| Comment by David Crossley [ 10/Feb/21 ] |
|
When trying to add mod-bursar-export to the reference environments, there were major failures. Here is a snippet from Jenkins output of the job folio-testing-test/106
fatal: [10.36.1.142]: FAILED! => {"changed": false, "connection": "close", "content":
"POST request for mod-bursar-export-1.0-SNAPSHOT.3 /_/tenant failed with finishConnect(..) failed:
Connection refused: /10.36.1.142:9157"
The module docker log and the okapi log are attached to this ticket. Did your team test this with your scratch environments or VMs, before getting us to deploy it? |
| Comment by Roman Leshchenko [ 10/Feb/21 ] |
|
I tested with VMs enviroment. Thank you. |
| Comment by David Crossley [ 10/Feb/21 ] |
|
No, broken in a different way. Here is a snippet from Jenkins output of the job folio-testing-test/107
fatal: [10.36.1.154]: FAILED! => {"changed": false, "connection": "close", "content":
"Deployment failed. Could not connect to port 9157: finishConnect(..) failed:
Connection refused: localhost/127.0.0.1:9157", ...
"msg": "Status code was 400 and not [200]: HTTP Error 400: Bad Request"
Attached the okapi.log for this run. There is no docker module log available. That seems a common error message, that the docker module did not start. Perhaps Ian Hardy or Wayne Schneider can assist with that. |
| Comment by Roman Leshchenko [ 11/Feb/21 ] |
|
Thank you. Guess, I binded wrong ports. I'd appreciate if you deploy with new changes. |
| Comment by David Crossley [ 11/Feb/21 ] |
|
Yes, you had a mismatch between ModuleDescriptor, Dockerfile, and Spring application.properties files. |
| Comment by David Crossley [ 11/Feb/21 ] |
|
The folio-testing build was okay today. So mod-bursar-export is now in there. However with the error described below, i am unsure that it is reliable. However, another blow-up when i attempted to add it to folio-snapshot. Here is a snippet from Jenkins output of the job folio-snapshot/803
ok: [10.36.1.41] => (item={'name': 'mod-patron', 'version': '4.4.0-SNAPSHOT.62', 'deploy': True})
ok: [10.36.1.41] => (item={'name': 'mod-rtac', 'version': '2.1.0-SNAPSHOT.56', 'deploy': True})
ok: [10.36.1.41] => (item={'name': 'mod-bursar-export-1.0-SNAPSHOT.5', 'deploy': True})
Note the absent version number. The okapi.log just plain stops after handling the previous module mod-rtac. See attached fs-803-okapi.log John Malconian I wonder how this error managed to get past our general module build pipelines. I also wonder whether this will cause a problem with the FOLIO ModuleDescriptor Registry. Roman Leshchenko The mod-bursar-export POM has a broken version number "1.0-SNAPSHOT" should be "x.y.z-SNAPSHOT". I am going to again remove it from platform-complete, rebuild folio-snapshot for other people, and await advice on how to proceed. |
| Comment by David Crossley [ 11/Feb/21 ] |
|
I suppose best to now use version number something like 1.0.1-SNAPSHOT We have a DevOps meeting in a few hours, so i can clarify there. Sorry, we both made a few mistakes during this effort. I should have used the folio-snapshot-test Jenkins build, as well as the folio-testing-test. There are some differences. |
| Comment by Roman Leshchenko [ 11/Feb/21 ] |
|
David Crossley really appreciate your work. Thanks a lot! I have changed the version number to "1.0.1-SNAPSHOT" |
| Comment by John Malconian [ 11/Feb/21 ] |
|
David Crossley I don't think Okapi enforces semantic version when modules descriptors are posted and I'm guessing that Maven CI pipeline is not checking the validity of the version grabbed from the Maven POM. This may be something we want to add. |
| Comment by David Crossley [ 12/Feb/21 ] |
|
Roman Leshchenko The daily build today of folio-snapshot was successful. So this is all done now. |
| Comment by Marc Johnson [ 12/Feb/21 ] |
|
My interpretation of the above is that a module version number not in the major.minor.patch form breaks the snapshot environment build. Have I understood this correctly? If so, what causes that failure (and doesn't cause the testing environment builds to fail)? |