Skip to content

ORAS publishing errors not being fully displayed #1115

Open

Description

@isc-dchui

Describe the bug

When publishing to an OCI/ORAS repo, a 401 bad credentials error is being truncated and lost. It manifests as ERROR! Unable to push <PYTHON EXCEPTION> 246 <class 'ValueError'>: Issue retrieving session url: {'errors': which is unhelpful as the actual error is missing.

When the actual error message is saved to a debug global, the missing information is present. So somehow somewhere it is being truncated.
^mtempdc(7463.984942,"errMsg")="ValueError(""Issue retrieving session url: {'errors': [{'status': 401, 'message': 'Bad Credentials'}]}"")"

To Reproduce

Unfortunately I've been unable to reproduce this so far.

Expected behavior

Python errors should be properly displayed to the user. 401, 403, and 404 errors should also maybe get special handling. (This would likely be a good workaround trying to reproduce the full error.)

System information (please complete the following information):

  • IPM version: 0.10.6
  • IRIS version: Unknown
  • OS: Linux
  • Docker or local: Docker

Dev notes

Look at the %IPM.Repo.Oras.PublishService class, especially the Push() and PushOras() methods.

Activity

  1. isc-dchui commented on Apr 10, 2026

    @isc-dchui
    CollaboratorAuthor

    Note that this truncated error messaging also occurs when an incompatible Python version is installed (because that will only throw warnings and not fail IPM install itself), and certain commands are run. In general we should properly propagate Python errors to the user.

  2. isc-kiyer commented on Apr 10, 2026

    @isc-kiyer
    Collaborator

    To properly propagate python errors, we may want to consider moving all of our Language = python references to external .py files and use %SYS.Python since that is the recommended approach to using embedded python

  3. isc-dchui commented on Apr 20, 2026

    @isc-dchui
    CollaboratorAuthor

    Rough idea:
    IPM .py files should be <FileCopy>'d to /mgr/ipm/<version>/python and then IPM code calls into %SYS.Python.Import with the constructed full path

  4. added this to the v0.10.x milestone on May 19, 2026
  5. isc-dchui commented on May 19, 2026

    @isc-dchui
    CollaboratorAuthor

    Users keep bumping into very unhelpful python exceptions so priority of this should be bumped.

  6. modified the milestones: v0.10.9, v0.10.10 on Aug 3, 2026
  7. modified the milestones: v0.10.10, v0.10.11 on Oct 5, 2026
  8. self-assigned this
    on Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions