Mirantis OpenStack

DBError: UPDATE statement on table 'ports' expected to update 1 row(s); 0 were matched

Bug #1369611 reported by Anastasia Palkina
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Fix Released
Low
Ann Taraday
Mirantis OpenStack 6.0-updates
5.0.x
Won't Fix
Low
MOS Neutron
Mirantis OpenStack 5.0-updates
5.1.x
Won't Fix
Low
Denis Meltsaykin
Mirantis OpenStack 5.1.1-updates
6.0.x
Won't Fix
Low
Ann Taraday
Mirantis OpenStack 6.0-updates
6.1.x
Fix Released
Low
Ann Taraday
Mirantis OpenStack 6.1

Bug Description

"build_id": "2014-09-15_00-01-46",
"ostf_sha": "64cb59c681658a7a55cc2c09d079072a41beb346",
"build_number": "8",
"auth_required": true,
"api": "1.0",
"nailgun_sha": "b8d8189cc37d6d1b26f4479be6be7313beefb1c8",
"production": "docker",
"fuelmain_sha": "d7ed7973034bde73d3f42c000984423b59b2312b",
"astute_sha": "f5fbd89d1e0e1f22ef9ab2af26da5ffbfbf24b13",
"feature_groups": ["experimental"], "
release": "5.1",
"release_versions": {"2014.1.1-5.1": {"VERSION": {"build_id": "2014-09-15_00-01-46", "ostf_sha": "64cb59c681658a7a55cc2c09d079072a41beb346", "build_number": "8", "api": "1.0", "nailgun_sha": "b8d8189cc37d6d1b26f4479be6be7313beefb1c8", "production": "docker", "fuelmain_sha": "d7ed7973034bde73d3f42c000984423b59b2312b", "astute_sha": "f5fbd89d1e0e1f22ef9ab2af26da5ffbfbf24b13", "feature_groups": ["experimental"], "release": "5.1", "fuellib_sha": "395fd9d20a003603cc9ad26e16cb13c1c45e24e6"}}}, "fuellib_sha": "395fd9d20a003603cc9ad26e16cb13c1c45e24e6"

1. Create new environment (CentOS, simple mode)
2. Choose GRE Neutron
3. Choose Ceilometer
4. Add controller, compute, cinder, 2 mongo
5. Move Storage network to other interface and untag it
6. Start deployment. It was successful
7. Start OSTF tests. It was successful
8. But there are many tracebacks on controller (node-14) in neutron-server.log (see paste below)

http://paste.openstack.org/show/111770/

Revision history for this message
Anastasia Palkina (apalkina) wrote :
Revision history for this message
Eugene Nikanorov (enikanorov) wrote :

This is a MOS bug, not Fuel's
However, its severity is not High, as this error doesn't indicate that anything is broken.

Nastya Urlapova (aurlapova)
Changed in mos:
importance: Undecided → High
assignee: nobody → MOS Neutron (mos-neutron)
milestone: none → 5.1
no longer affects: fuel
Eugene Nikanorov (enikanorov)
Changed in mos:
importance: High → Low
Dmitry Mescheryakov (dmitrymex)
Changed in mos:
milestone: 5.1 → 5.1.1
status: New → Confirmed
Dmitry Mescheryakov (dmitrymex)
Changed in mos:
status: Confirmed → Won't Fix
Revision history for this message
Ann Taraday (akamyshnikova) wrote :

According to provided logs at the same time for the same port delete_port and update_device_down commands have been executed. That's why update_device_down shows this DBError.

Environment where this error can be reproduced is required for further analysis as it is not clear in what case this commands execute together. Later these commands are executed one after another and error does't appear.

Revision history for this message
Eugene Nikanorov (enikanorov) wrote :

AFAIK there is an upstream bug on this. Or at least this was seen multiple times in gate jobs.

I think we only should catch this exception and no more than that.
I don't think we need to fix it in mos-neutron. Let's wait for an upstream fix.

Revision history for this message
Ann Taraday (akamyshnikova) wrote :

Fix for this was merged to master https://review.openstack.org/143826. I added this change as backport for stable/juno. If it won't be accepted will push a separate change to mos 6.1.

Revision history for this message
Ann Taraday (akamyshnikova) wrote :

Change https://review.openstack.org/148845 was merged to stable/juno

Revision history for this message
Fabrizio Soppelsa (fsoppelsa) wrote :

Do you think that the fix https://bugs.launchpad.net/neutron/+bug/1405379 can be backported to 5.1.1 series?
It's customer found in 5.1.1.

tags: added: customer-found
Revision history for this message
Ann Taraday (akamyshnikova) wrote :

@Fabrizio Soppelsa (fsoppelsa)

Yes, existing patch https://review.openstack.org/148845 could be backported to 5.x series.

Revision history for this message
Alexander Ignatov (aignatov) wrote :

According to Ann's investigation I'm moving this bug to cnfirmed and to -updates branch.

Revision history for this message
Kristina Berezovskaia (kkuznetsova) wrote :

Verify:
This issue not reproduced on the last MOS 6.1 images, rally tests for ports are also successful

Revision history for this message
Vitaly Sedelnik (vsedelnik) wrote :

Won't Fix in 5.1.1-updates because of Low proirity

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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