Magnum

"magnum node-list" doesn't work for Kub

Bug #1510054 reported by Egor Guz
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Won't Fix
Undecided
Unassigned
Magnum mitaka-1

Bug Description

magnum node-list
+------+------+----------+
| uuid | type | image_id |
+------+------+----------+
+------+------+----------+

kubectl get nodes
NAME LABELS STATUS
k8-ueeeq34rgg-0-4t73rojocliq-kube-minion-enneznu6yeyc kubernetes.io/hostname=k8-ueeeq34rgg-0-4t73rojocliq-kube-minion-enneznu6yeyc NotReady
k8-ueeeq34rgg-1-u3ttmdulxtbj-kube-minion-q7pm262itb5z kubernetes.io/hostname=k8-ueeeq34rgg-1-u3ttmdulxtbj-kube-minion-q7pm262itb5z Ready

Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
space (fengzhr)
Changed in magnum:
assignee: nobody → space (fengzhr)
space (fengzhr)
Changed in magnum:
assignee: space (fengzhr) → nobody
Revision history for this message
Eli Qiao (taget-9) wrote :

node-list was removed by

commit b393e77f81f9cc2acf661a7d726d2e306703a6fc
Author: Hua Wang <email address hidden>
Date: Wed Feb 3 17:22:11 2016 +0800

    Remove node object from magnumclient

    The node object represents either a bare metal or virtual machine
    node that is provisioned with an OS to run the containers, or
    alternatively, run kubernetes. Magnum use Heat to deploy the nodes,
    so it is unnecessary to maintain node object in Magnum. Heat can do
    the work for us. The code about node object is useless now, so let's
    remove it from Magnum.

    Change-Id: Icb7bd21032b592c94033d93e22f460d8c2270fbe
    Closes-Bug: #1541255
    Depends-On: If8761b06a364127683099afb4dc51ea551be6f89

Changed in magnum:
status: New → Won't Fix
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.