[regression] Swift service fails to start with [Errno 2] No such file or directory: '/etc/swift/object.ring.gz

Bug #1582646 reported by Volodymyr Shypyguzov on 2016-05-17
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
High
Dmitry Ilyin
Mitaka
High
Dmitry Ilyin
Newton
High
Dmitry Ilyin

Bug Description

Test group: deploy_neutron_vlan_ha
Steps to reproduce:
        1. Create cluster
        2. Add 3 nodes with controller role
        3. Add 2 nodes with compute role
        4. Deploy the cluster
        5. Run network verification
        6. Run OSTF << Fails

Expected result: OSTF tests passed
Actual result: OSTF test fails on checking backends state

In swift-all.log:
#012IOError: [Errno 2] No such file or directory: '/etc/swift/object.ring.gz'

Also, reproduce at bonding test cases
https://product-ci.infra.mirantis.net/job/9.0.system_test.ubuntu.bonding_ha/109/consoleFull
setting to swarm-blocker

Changed in fuel:
importance: Undecided → High
tags: added: swarm-blocker
Changed in fuel:
assignee: nobody → MOS Linux (mos-linux)
Dmitry Teselkin (teselkin-d) wrote :
Changed in fuel:
assignee: MOS Linux (mos-linux) → MOS Packaging Team (mos-packaging)
summary: - Swift service fails to start with [Errno 2] No such file or directory:
- '/etc/swift/object.ring.gz
+ [regression] Swift service fails to start with [Errno 2] No such file or
+ directory: '/etc/swift/object.ring.gz
Changed in fuel:
milestone: none → 9.0
status: New → Confirmed

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

version

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

tags: added: need-info
Igor Yozhikov (iyozhikov) wrote :

Packages? as far as I know and according to Swift manuals? are not responsible for rings creation.
Ring creation and synchronization must be done using CM tools or manually.
Also in deployment logs was found next:
node-1 - primary controller - ring files created
node-4 and node-5 - rest controllers - didn't sync ring files.
Procedure described at https://github.com/openstack/fuel-library/blob/2f9f9516f04de573809b4d1162dfd2b9087ea90f/deployment/puppet/openstack_tasks/manifests/swift/proxy_storage.pp#L421-L440 has not been seen in logs.

Please, reproduce this bug and provide ENV for further investigation.

Changed in fuel:
status: Confirmed → Incomplete
Igor Yozhikov (iyozhikov) wrote :

s/?/,/

Igor Yozhikov (iyozhikov) wrote :

During more deep investigation made with Dmitry Ilyin found root cause - wrong
puppet sequence of steps.

Changed in fuel:
assignee: MOS Packaging Team (mos-packaging) → MOS Puppet Team (mos-puppet)
Dmitry Ilyin (idv1985) on 2016-05-19
Changed in fuel:
assignee: MOS Puppet Team (mos-puppet) → Dmitry Ilyin (idv1985)

Reviewed: https://review.openstack.org/318563
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=52716670dcd2636828ea49165e24219fd07aea1a
Submitter: Jenkins
Branch: master

commit 52716670dcd2636828ea49165e24219fd07aea1a
Author: Dmitry Ilyin <email address hidden>
Date: Thu May 19 13:50:28 2016 +0300

    Refactor openstack_tasks::swift

    Change-Id: I7ff5778367a30b00975ba41069dd6e11332a5c38
    Related-bug: 1582646

Reviewed: https://review.openstack.org/320374
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=765af856b63f8e99ad8c82f303432d572c399bd3
Submitter: Jenkins
Branch: stable/mitaka

commit 765af856b63f8e99ad8c82f303432d572c399bd3
Author: Dmitry Ilyin <email address hidden>
Date: Thu May 19 13:50:28 2016 +0300

    Refactor openstack_tasks::swift

    cherry picked from commit 52716670dcd2636828ea49165e24219fd07aea1a
    Change-Id: I7ff5778367a30b00975ba41069dd6e11332a5c38
    Related-bug: 1582646

tags: added: in-stable-mitaka

There were no reproduces on swarm on iso 9.0 mos iso #416

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

Other bug subscribers