Bug 1949703
Summary: | Instance sticks in BUILD when scheduling with a port assigned invalid MAC | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | nacurry |
Component: | openstack-nova | Assignee: | Alex Stupnikov <astupnik> |
Status: | CLOSED UPSTREAM | QA Contact: | OSP DFG:Compute <osp-dfg-compute> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 16.2 (Train) | CC: | alifshit, astupnik, dasmith, eglynn, jhakimra, kchamart, sbauza, sgordon, smooney, vromanso |
Target Milestone: | --- | Keywords: | Patch, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-06-01 15:54:45 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
nacurry
2021-04-14 20:28:30 UTC
From Nova's POV, this is valid, as OVO raising a ValueError should cause the instance to go into ERROR, and not remain stuck in BUILD. I've also filed BZ 1951228 with Neutron to request better validation at the port create API level. Hi Artom,
> OVO raising a ValueError should cause the instance to go into ERROR, and not remain stuck in BUILD
Currently, the instance remains in BUILD state indefinitely. We want it to go into ERROR state, correct?
(In reply to nacurry from comment #4) > Hi Artom, > > OVO raising a ValueError should cause the instance to go into ERROR, and not remain stuck in BUILD > > Currently, the instance remains in BUILD state indefinitely. We want it to > go into ERROR state, correct? Correct. I was essentially agreeing with your initial description, though the impact is admittedly low, since what will most likely end up happening regardless of whether the instance is stuck in BUILD or goes into ERROR is that the user will delete it. The real fix would be for Neutron to validate the MAC address when creating the port - hence why I filed BZ 1951228. Closing as UPSTREAM since this is a small cosmetic fix and we don't need any downstream trackers/cherry-picks for this. |