Fuel for OpenStack

[master-pkg-systest-centos] Fails on .spec file update from upstream for python-cryptography package

Bug #1599901 reported by Ivan Udovichenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
Critical
Artem Panchenko
Fuel for OpenStack 10.0

Bug Description

In cases when we use Obsoletes:/Provides: types of dependency in .spec file for python2-cryptography package. [1]
fuel-qa script fails during packages update. [2]

Using Obsoletes:/Provides: types of dependency is perfectly fine and should not lead to such errors.

[1] https://review.fuel-infra.org/#/c/22949/5/python-cryptography.spec #61,#66
[2] https://packaging-ci.infra.mirantis.net/job/master-pkg-systest-centos/1003/console

Tags: area-ci
Igor Yozhikov (iyozhikov)
Changed in fuel:
importance: Undecided → Critical
assignee: nobody → Fuel QA telco (fuel-qa-telco)
assignee: Fuel QA telco (fuel-qa-telco) → Fuel QA Team (fuel-qa)
Revision history for this message
Igor Yozhikov (iyozhikov) wrote :

Suggestion:
When fuel-qa running yum update: script could count amount of changed packages.
4 example catching strings which are starting from "Installing" or "Erasing".

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-qa (master)

Fix proposed to branch: master
Review: https://review.openstack.org/339159

Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → Artem Panchenko (apanchenko-8)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-qa (master)

Reviewed: https://review.openstack.org/339159
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=62f3da00cb3ff15417697cef121c88275a583c3e
Submitter: Jenkins
Branch: master

commit 62f3da00cb3ff15417697cef121c88275a583c3e
Author: Artem Panchenko <email address hidden>
Date: Thu Jul 7 20:40:38 2016 +0300

    Fix "variable referenced before assignment" error

    It's possible to get the error above if no packages
    were updated on master node in 'admin_install_updates'
    method.

    Also tests must handle situations when old package is
    replaced by new one, so it's marked as installed but
    not upgraded.

    Change-Id: I6fe99ae16d887024643c60ea60e7650181fd432a
    Closes-bug: #1599901

Changed in fuel:
status: In Progress → Fix Committed
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.