Le 5 juin 2015 à 12:01, "Alex Khivin" <email address hidden> a écrit :
> @Nicolas
> you can try to apply this fix and if it will not help then fill free to create new launchpad bug with related logs.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1457055
>
> Title:
> Cinder loses rabbitmq exchanges and get stuck in reply loop
>
> Status in Mirantis OpenStack:
> Fix Committed
> Status in Mirantis OpenStack 6.0-updates series:
> Fix Committed
> Status in Mirantis OpenStack 6.0.x series:
> Fix Committed
>
> Bug description:
> During failover tests cinder got stuck in endless loop trying to reply in non-existent exchange.
> It tried to publish message about 100 times for 20 minutes and was fixed only when we have created the missing exchange/queue in rabbitmq manually.
> All this time during erroneous reply publish cinder-volume was not available to process queries.
>
> Small example of logs: http://paste.mirantis.net/show/445/
> Snapshot: https://drive.google.com/a/mirantis.com/file/d/0B5oyxJmUjFQcWVo0OGVOdkhvTDQ/view?usp=sharing
> Version:
> DEPRECATION WARNING: /etc/fuel/client/config.yaml exists and will be used as the source for settings. This behavior is deprecated. Please specify the path to your custom settings file in the FUELCLIENT_CUSTOM_SETTINGS environment variable.
> api: '1.0'
> astute_sha: cb655a9a9ad26848bcd9d9ace91857b6f4a0ec15
> auth_required: true
> build_id: 2015-05-18_03-43-53
> build_number: '432'
> feature_groups:
> - mirantis
> fuel-library_sha: 1621cb350af744f497c35f2b3bb889c2041465d8
> fuel-ostf_sha: 9ce1800749081780b8b2a4a7eab6586583ffaf33
> fuelmain_sha: 0e970647a83d9a7d336c4cc253606d4dd0d59a60
> nailgun_sha: 076566b5df37f681c3fd5b139c966d680d81e0a5
> openstack_version: 2014.2.2-6.1
> production: docker
> python-fuelclient_sha: 38765563e1a7f14f45201fd47cf507393ff5d673
> release: '6.1'
> release_versions:
> 2014.2.2-6.1:
> VERSION:
> api: '1.0'
> astute_sha: cb655a9a9ad26848bcd9d9ace91857b6f4a0ec15
> build_id: 2015-05-18_03-43-53
> build_number: '432'
> feature_groups:
> - mirantis
> fuel-library_sha: 1621cb350af744f497c35f2b3bb889c2041465d8
> fuel-ostf_sha: 9ce1800749081780b8b2a4a7eab6586583ffaf33
> fuelmain_sha: 0e970647a83d9a7d336c4cc253606d4dd0d59a60
> nailgun_sha: 076566b5df37f681c3fd5b139c966d680d81e0a5
> openstack_version: 2014.2.2-6.1
> production: docker
> python-fuelclient_sha: 38765563e1a7f14f45201fd47cf507393ff5d673
> release: '6.1'
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mos/+bug/1457055/+subscriptions
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
Thanks Alex, Where do we find the fix ?
Nicolas
Le 5 juin 2015 à 12:01, "Alex Khivin" <email address hidden> a écrit :
> @Nicolas /bugs.launchpad .net/bugs/ 1457055 paste.mirantis. net/show/ 445/ /drive. google. com/a/mirantis. com/file/ d/0B5oyxJmUjFQc WVo0OGVOdkhvTDQ /view?usp= sharing client/ config. yaml exists and will be used as the source for settings. This behavior is deprecated. Please specify the path to your custom settings file in the FUELCLIENT_ CUSTOM_ SETTINGS environment variable. 8bcd9d9ace91857 b6f4a0ec15 497c35f2b3bb889 c2041465d8 0b8b2a4a7eab658 6583ffaf33 d336c4cc253606d 4dd0d59a60 1c3fd5b139c966d 680d81e0a5 fuelclient_ sha: 38765563e1a7f14 f45201fd47cf507 393ff5d673 8bcd9d9ace91857 b6f4a0ec15 497c35f2b3bb889 c2041465d8 0b8b2a4a7eab658 6583ffaf33 d336c4cc253606d 4dd0d59a60 1c3fd5b139c966d 680d81e0a5 fuelclient_ sha: 38765563e1a7f14 f45201fd47cf507 393ff5d673 /bugs.launchpad .net/mos/ +bug/1457055/ +subscriptions
> you can try to apply this fix and if it will not help then fill free to create new launchpad bug with related logs.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Cinder loses rabbitmq exchanges and get stuck in reply loop
>
> Status in Mirantis OpenStack:
> Fix Committed
> Status in Mirantis OpenStack 6.0-updates series:
> Fix Committed
> Status in Mirantis OpenStack 6.0.x series:
> Fix Committed
>
> Bug description:
> During failover tests cinder got stuck in endless loop trying to reply in non-existent exchange.
> It tried to publish message about 100 times for 20 minutes and was fixed only when we have created the missing exchange/queue in rabbitmq manually.
> All this time during erroneous reply publish cinder-volume was not available to process queries.
>
> Small example of logs: http://
> Snapshot: https:/
> Version:
> DEPRECATION WARNING: /etc/fuel/
> api: '1.0'
> astute_sha: cb655a9a9ad2684
> auth_required: true
> build_id: 2015-05-18_03-43-53
> build_number: '432'
> feature_groups:
> - mirantis
> fuel-library_sha: 1621cb350af744f
> fuel-ostf_sha: 9ce180074908178
> fuelmain_sha: 0e970647a83d9a7
> nailgun_sha: 076566b5df37f68
> openstack_version: 2014.2.2-6.1
> production: docker
> python-
> release: '6.1'
> release_versions:
> 2014.2.2-6.1:
> VERSION:
> api: '1.0'
> astute_sha: cb655a9a9ad2684
> build_id: 2015-05-18_03-43-53
> build_number: '432'
> feature_groups:
> - mirantis
> fuel-library_sha: 1621cb350af744f
> fuel-ostf_sha: 9ce180074908178
> fuelmain_sha: 0e970647a83d9a7
> nailgun_sha: 076566b5df37f68
> openstack_version: 2014.2.2-6.1
> production: docker
> python-
> release: '6.1'
>
> To manage notifications about this bug go to:
> https:/
_______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ _______ __
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.