Cluster deployment failed with the error: Failed to execute ironic_post_swift_key/2

Bug #1570942 reported by Sofiia Andriichenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Status tracked in 10.0.x
10.0.x
Confirmed
High
Nikita Karpin
9.x
Confirmed
High
Nikita Karpin

Bug Description

log swift-object-server on contlroller
http://paste.openstack.org/show/494225/
from log "failed to connect to 192.168.1.4" , but 192.168.1.4 doesn't exist, 192.168.1.3 and 192.168.1.5 exists

Steps:
1. Deploy cluster with the following configuration:

1 Controller
1 Compute
1 Ironic.

Settings:
Compute - QEMU.
Network - Neutron with VLAN segmentation, DVR enabled.
Storage Backends - Cinder LVM over iSCSI for volumes.

2. Add 1 Ironic and 1 Controller+Ironic node.
3. Deploy changes.
4. Run OSTF. Run happy-path to boot Ironic VM instance.
5. Delete 1 Ironic and 1 Controller+Ironic node.
6. Deploy changes.

Actuall:
Changes deployment failed in 99% of deployment on controller
ERROR. Deployment has failed. All nodes are finished. Failed tasks: Task[ironic_post_swift_key/2] Stopping the deployment process!

Expected:
Deployment pass

Revision history for this message
Sofiia Andriichenko (sandriichenko) wrote :
Revision history for this message
Sofiia Andriichenko (sandriichenko) wrote :
Dina Belova (dbelova)
tags: added: area-ironic
Changed in mos:
assignee: nobody → MOS Ironic (mos-ironic)
Changed in mos:
importance: Undecided → High
status: New → Confirmed
summary: - Failed to execute ironic_post_swift_key/2
+ Cluster deployment failed with the error: Failed to execute
+ ironic_post_swift_key/2
Changed in mos:
milestone: none → 9.0
description: updated
Revision history for this message
Bug Checker Bot (bug-checker) wrote : Autochecker

(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
Revision history for this message
Andrey Shestakov (ashestakov) wrote :

Looks like swift scale down is not works properly.
After controller deletion swift ring should rebuild.

tags: added: area-swift
tags: removed: area-ironic
Revision history for this message
Alyona Kiseleva (akiselyova) wrote :

According to swift logs, swift wasn't configured properly in redeployment process.
Nodes should be removed from swift-ring-builder, rings should be rebalanced and object.ring.gz should be sent to nodes after it. I see error with it in swift log, so, something from this process was missed. Something like

swift-ring-builder /etc/swift/account.builder remove <ip_address>/<device_name>
swift-ring-builder /etc/swift/container.builder remove <ip_address>/<device_name>
swift-ring-builder /etc/swift/object.builder remove <ip_address>/<device_name>

swift-ring-builder /etc/swift/account.builder rebalance
swift-ring-builder /etc/swift/container.builder rebalance
swift-ring-builder /etc/swift/object.builder rebalance

swift-ring-builder /etc/swift/account.builder
swift-ring-builder /etc/swift/container.builder
swift-ring-builder /etc/swift/object.builder

It's a deployment problem.

Revision history for this message
Nikita Karpin (mkarpin) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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