Skip to content

Agent fails because 302 is returned #1

@michealbeatty

Description

@michealbeatty

watcher.sh looks for a status of 200 but a status of 302 is actually returned which causes agent to report the service is down and then the container stops.

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