RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1223443 - You can still check introspection status for ironic nodes that have been deleted
Summary: You can still check introspection status for ironic nodes that have been deleted
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: openstack-tripleo
Version: trunk
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: Kilo
Assignee: James Slagle
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-20 14:03 UTC by Udi Kalifon
Modified: 2016-05-19 15:41 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 15:41:30 UTC
Embargoed:


Attachments (Terms of Use)

Description Udi Kalifon 2015-05-20 14:03:24 UTC
Description of problem:
You can run "openstack baremetal introspection status $node_id -f value -c finished" on nodes that are no longer registered in ironic.


Version-Release number of selected component (if applicable):
openstack-ironic-api-2015.1-dev684.el7.centos.noarch
python-rdomanager-oscplugin-0.0.7-dev6.el7.centos.noarch


How reproducible:
100%


Steps to Reproduce:
1. Register and discover nodes
2. Store the node ids in an environment variable by running "node_ids=$(ironic node-list | tail -n +4 | head -n -1 | awk -F "| " '{print $2}')"
3. Delete all nodes by running "for node_id in $node_ids; do ironic node-delete $node_id; done"
4. Check the introspection status of the deleted nodes by "for node_id in $node_ids; do openstack baremetal introspection status $node_id -f value -c finished; done"


Actual results:
Info for the deleted nodes is still available in the system.


Expected results:
You should get an error when trying to query on nodes that no longer exist.

Comment 3 Chandan Kumar 2016-05-19 15:41:30 UTC
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.


Note You need to log in before you can comment on or make changes to this bug.