summaryrefslogtreecommitdiff
path: root/releasenotes/notes/remove-vifs-on-teardown-707c8e40c46b6e64.yaml
blob: 4b323fa151081e68f8e57d5aae3d511b44716772 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
---
upgrade:
  - |
    The behavior for retention of VIF interface attachments has changed.

    If your use of the Bare Metal service is reliant upon the behavior of
    the VIFs being retained, which was introduced as a behavior change
    during the Ocata cycle, then you must update your tooling to explicitly
    re-add the VIF attachments prior to deployment.
fixes:
  - |
    Fixes potential case of VIF records being orphaned as the service
    now removes all records of VIF attachments upon the teardown of a deployed
    node. This is in order to resolve issues related to where it is
    operationally impossible in some circumstances to remove a VIF
    attachment while a node is being undeployed as the Compute service
    will only attempt to remove the VIF for five minutes.

    See `bug 1743652 <https://bugs.launchpad.net/ironic/+bug/1743652>`_ for more details.