Can't create a snapshot of an instance with virtual function attached

[Gil Meir]

In Fuel v6.0 instances using SR-IOV for networking are created successfully, but taking a snapshot fails.
The part of the error in compute.log is attached.

[Andrey Danin (gcon-monolake)]

Gil,
Did this functionality (snapshot creation with VF attached) work before? Or is it working in vanilla OpenStack but isn't in MOS?

[Gil Meir (gilmeir-d)]

This is probably an integration issue with our solution and Juno upstream sriovnicswitch mechanism driver and its related changes in neutron/libvirt/nova, not sure yet.
One of the causes *might* be an out of date glance client, which contains an upstream bug which was fixed 1-2 weeks ago (https://review.openstack.org/#/c/129289/), but this doesn't completely solve our issue, so let's wait with this. We are investigating the issue.

[Gil Meir (gilmeir-d)]

There is a manual workaround for this - shutting down the instance before taking a snapshot.
Need to add it to release notes.

[Irina Povolotskaya (ipovolotskaya)]

Added to 6.0 RN within https://review.openstack.org/#/c/136739/

[Roman Alekseenkov (ralekseenkov)]

Updating priority to High for customer-found issues, so they don't get moved to 7.0

[Mike Scherbakov (mihgen)]

We do not such a policy for increasing importance of the bug if it has customer-found tag. Tag "customer-found" be itself makes the priority of the bug resolution higher among the other bugs of same importance, but which do not have such a tag. For instance, among all High bugs those which have "customer-found" taking the highest priority.

We have strict criteria for importance of bugs: https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Confirm_and_triage_bugs. This particular bug qualifies only for Medium as highest according to:
"specific hardware, configurations, or components are working incorrectly; or is completely unusable but there's a workaround". There is a workaround, so we can just document this workaround in known issues for 6.1 release. In order to document it, I'm tagging it with "release-notes" tag. As we passed SCF, all bugs lower than High are moved to the next milestone, so I'm closing this bug as Won't fix for 6.1.

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/223546

[OpenStack Infra (hudson-openstack)]

Change abandoned by Olga Gusarenko (<email address hidden>) on branch: master
Review: https://review.openstack.org/223546
Reason: abandoning this as it was fixed in 6.1 plugin

[Aviram Bar-Haim (aviramb)]

Assignee is removed since we don't see this problem anymore..

[Bartosz Kupidura (zynzel)]

If reporter will reproduce issue on master (newton), please update status to confirmed