[ironic] Port for node that already has a port

Bug #1524422 reported by Kyrylo Romanenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Invalid
Medium
Kyrylo Romanenko

Bug Description

We can create a port for the node that already has a port.

Expected that such action should be prohibited in Ironic.

Steps:

root@node-4:~# ironic port-create -n 53c690ef-d158-4fcc-a67d-aa29f98a626b -a 64:5f:1b:c3:5c:d5
+-----------+--------------------------------------+
| Property | Value |
+-----------+--------------------------------------+
| node_uuid | 53c690ef-d158-4fcc-a67d-aa29f98a626b |
| extra | {} |
| uuid | 2558b4a1-cf35-4b6d-b8cf-519c51209386 |
| address | 64:5f:1b:c3:5c:d5 |
+-----------+--------------------------------------+

root@node-4:~# ironic port-create -n 53c690ef-d158-4fcc-a67d-aa29f98a626b -a 64:5f:1b:c3:5c:d6
+-----------+--------------------------------------+
| Property | Value |
+-----------+--------------------------------------+
| node_uuid | 53c690ef-d158-4fcc-a67d-aa29f98a626b |
| extra | {} |
| uuid | 679ba606-8cd2-4387-b125-36aaf43ec8a5 |
| address | 64:5f:1b:c3:5c:d6 |
+-----------+--------------------------------------+

Here you can see that two ports with MACs 64:5f:1b:c3:5c:d5 and 64:5f:1b:c3:5c:d6 were assigned for one node with uuid 53c690ef-d158-4fcc-a67d-aa29f98a626b.

Env:
VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "8.0"
  openstack_version: "2015.1.0-8.0"
  api: "1.0"
  build_number: "243"
  build_id: "243"
  fuel-nailgun_sha: "1b6ae6c7fd4766f4a57d90afc1cd0f2315255a42"
  python-fuelclient_sha: "91474bd8c526f4f536ab13368feb4a5c1b84d185"
  fuel-agent_sha: "660c6514caa8f5fcd482f1cc4008a6028243e009"
  fuel-nailgun-agent_sha: "a33a58d378c117c0f509b0e7badc6f0910364154"
  astute_sha: "b60624ee2c5f1d6d805619b6c27965a973508da1"
  fuel-library_sha: "22ed1ebd7804457a02b51b57c7019d853c528611"
  fuel-ostf_sha: "a98973482f839554d90cc1c071d625a01e018cfe"
  fuel-mirror_sha: "5a1efffd411611b87cbd45af59b9733b7e170cd4"
  fuelmenu_sha: "fcb15df4fd1a790b17dd78cf675c11c279040941"
  shotgun_sha: "25a0cc461a9fa4f7684f04cef0ff4ad9aa99a64d"
  network-checker_sha: "a3534f8885246afb15609c54f91d3b23d599a5b1"
  fuel-upgrade_sha: "1e894e26d4e1423a9b0d66abd6a79505f4175ff6"
  fuelmain_sha: "ff6eec402830ea8aa9898249b5eeb928576962ff"

ironic client version 0.8.1

Tags: ironic
summary: - Port for node that already has a port
+ [ironic] Port for node that already has a port
Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

Why can't a node have multiple ports? I thought, this was a valid use case.

Changed in mos:
assignee: MOS Ironic (mos-ironic) → Kyrylo Romanenko (kromanenko)
status: New → Incomplete
Revision history for this message
Kyrylo Romanenko (kromanenko) wrote :

Now I know that it is a correct behavior to boot one machine with several network interfaces.

Changed in mos:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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