Magnum

Endpoint not found after changing service name

Bug #1586575 reported by hongbin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
hongbin

Bug Description

$ magnum bay-create --name k8sbay --baymodel k8sbaymodel --node-count 1
Create for bay k8sbay failed: Remote error: EndpointNotFound publicURL endpoint for container-infra service not found
[u' (HTTP 500) (Request-ID: req-a4f38927-7c9a-4135-a184-269474e2d6bb)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

Fix proposed to branch: master
Review: https://review.openstack.org/322369

Changed in magnum:
assignee: nobody → hongbin (hongbin034)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/322369
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=96c0286d50c81752fbdf8a746b476278b4004f28
Submitter: Jenkins
Branch: master

commit 96c0286d50c81752fbdf8a746b476278b4004f28
Author: Hongbin Lu <email address hidden>
Date: Fri May 27 22:16:28 2016 -0500

    Fix an EndpointNotFound error

    Make it backward-compatible with old service type, while printing a
    warning message.

    Change-Id: I8e65e3cd4ebf732fa014c8d492280213ed052ff2
    Closes-Bug: #1586575

Changed in magnum:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 3.0.0

This issue was fixed in the openstack/magnum 3.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.