• Attendees / Apologies
• Upcoming Availability 

ERM-2956 - Getting issue details... STATUS

• no key exception
• • is that the liquibase issue?
  • or are there multiple causes? it has been observed on EPAM multi-tenant installs
• Inappropriate use of metaspace parameter by EPAM team
  • no action possible by ERM
• Liquibase bug
  
  • changes affect G5 only
  • requires liquibase dependency update - which cannot be backported to Orchid or prior
• "No key ...." exception 
• Locks being applied but then not released in
  • table tenant_changelog_lock (caused either by liquibase bug or app stopping while lock in place)
  • would need devops attention rather than work from Bienenvolk
• New unknowns
  • can the no key" 

WIP 

• What progress or impediment on previously stated actions?
• What's left to do?
• Any new unknowns?
• What help or input is needed?
• When expected to be ready for review?

Pending

• Are the blocking conditions still relevant? 
• What action is needed to unblock, and by whom?

• Who needs to be involved in the elaboration process? 
• What is the timeframe for getting input?
• When is the issue expected to be ready for development?

• Who is picking up what next?
• When is next issue expected to start / complete?
• Anything needed to start next issue (dependencies or clarifications)?

Blocked

• ERM-2939 - Getting issue details... STATUS
  
  • Progress/Impediments:
    • required bubbling hierarchy update, which is tricky with Grails save handling of save
    • identified what appeared to be a non-standard double-saving code block that has been moved to event listener - appeared to work, but broke ingest when merged
    • currently only bubbles 1 step up or down, rather than full tree
    • last updated increasingly proving to be the wrong field for this
  • TODO:
    • merge frontend changes for ERM-2923
    • revert changes in listener from ERM-2939
    • then review what the goal for coverage and last updated and re-engineer an appropriate solution as part of UXPROD-4272 & UXPROD-4271 (Owen) and review with team+Steve
  • New unknowns / help or input needed: NA
  • ETA for review: today
• ERM-2641 - Getting issue details... STATUS
  • Essentially blocked by ERM-2956, as that may precipitate further changes that will cause repeat regression testing 

Needs Elaboration / Triage

• ERM-2940 - Getting issue details... STATUS
  • attempt to move to testImplementation

Sprint Backlog - Next Up

• NA

Allocations

• Claudia: NA
• Ethan: 
  • ERM-2940 - Getting issue details... STATUS
  • ERM-2630 - Getting issue details...