Skip to content

Discovery job created by blueprint apply failed with invalid uri #106

@toyidong

Description

@toyidong

Environment: Universal orchestrator v25 and RFJKS extensions (blueprint is only applicable to v25 and earlier version UO )

Steps:

  1. Enable "Allow Blueprint" for RFJKS certificate store type
  2. Schedule a RFJKS discovery job for orchestrator A
  3. Generate a blueprint for orchestrator A
  4. Apply this blueprint to orchestrator B, check the new RFJKS discovery job is created for orchestrator B
  5. Let both orchestrators to run the jobs, with correct job settings, orchestrator A should complete job successfully, but orchestrator B will get error "Invalid Uri"

Root cause:

in WinRMHandler.cs line 38, the connection is using input server string to construct Uri. In the case of blueprint apply, the new job will use target orchestrator's client machine for the target server name, (which usually the FQDN of target machine without protocol part, e.g. http://). This will cause error in Uri construction.

I am wondering before constructing Uri, we may want to validate and transform the server string to a valid string, if necessary

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions