Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • C CRS Conversion
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 17
    • Issues 17
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Upcoming Change to GitLab Pages The GitLab Pages URL is planned to migrate from the current *.pages.community.opengroup.org to a simpler domain: *.pages.opengroup.org. At the same time, HTTPS will be enabled for the server. This change is planned for May 21, 2022.

If you have questions or concerns, please email forum-support@opengroup.org.

  • Open Subsurface Data Universe Software
  • Platform
  • System
  • Reference and Helper Services
  • CRS Conversion
  • Issues
  • #27

Closed
Open
Created Sep 07, 2021 by Rostislav Vatolin [SLB]@rvatolin☕Maintainer

Conversion service fails at deployment stage after update of core libraries

Conversion service fails after updating the core libraries because it doesn't have the configuration to call partition service. This started happening after this MR: osdu/platform/system/lib/cloud/azure/os-core-lib-azure!134 (merged)

To resolve the issue please set the property azure.serviceBus.manager.enabled to false

Assignee
Assign to
Time tracking