Fuel for OpenStack

[system-tests][qa][ibp] add partitioning test for image based

Bug #1419833 reported by Alexander Gordeev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
Fuel QA Team
Fuel for OpenStack 10.0
Mitaka
Won't Fix
Medium
Fuel QA Team
Fuel for OpenStack 9.0
Newton
Confirmed
Medium
Fuel QA Team
Fuel for OpenStack 10.0

Bug Description

to ensure that the following bug https://bugs.launchpad.net/fuel/+bug/1410471 was completely resolved
special test case needed:

eg.:
1) boot VM into bootstrap
2) inject provision.json (with enhanced parititioning scheme, i'll post it later)
3) simultaneously run something that will load VM's all cpu cores heavily and run 'partition' hook. (it's a part of fuel-agent, which executes only partitioning)
4) examine exit code of 'partition'. 0 means that test has been passed

Nastya Urlapova (aurlapova)
Changed in fuel:
milestone: none → 6.1
status: New → Confirmed
Timur Nurlygayanov (tnurlygayanov)
Changed in fuel:
importance: Undecided → Medium
Dmitry Pyzhov (dpyzhov)
tags: added: feature-image-based
removed: image-based partition provision
Nastya Urlapova (aurlapova)
summary: - [qa][ibp] add partitioning test for image based
+ [system-tests][qa][ibp] add partitioning test for image based
tags: added: system-tests
Nastya Urlapova (aurlapova)
Changed in fuel:
importance: Medium → High
Maksym Strukov (unbelll)
Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → Maxim Strukov (unbelll)
Bogdan Dobrelya (bogdando)
tags: added: non-release
Revision history for this message
Nastya Urlapova (aurlapova) wrote :

@Alexander, we are still waiting your parititioning scheme.

Changed in fuel:
assignee: Maxim Strukov (unbelll) → Aleksandr Gordeev (a-gordeev)
Revision history for this message
Vladimir Kozhukalov (kozhukalov) wrote :

Input data could be taken from any installation. They are written in fuel-agent log and one also could take them from /tmp/provision.json on bootstrap node. Example is here http://paste.openstack.org/show/274165/

Revision history for this message
Vladimir Kozhukalov (kozhukalov) wrote :

Previous sample is corrupted, here is correct one http://paste.openstack.org/show/277332/ By the way, you can get it from /var/log/docker-logs/nailgun/app.log on the master node.

Changed in fuel:
assignee: Aleksandr Gordeev (a-gordeev) → Fuel QA Team (fuel-qa)
Revision history for this message
Nastya Urlapova (aurlapova) wrote :

Moved to 7.0, we use IBP in swarm, on scale and others labs, so this case should be covered already.

Changed in fuel:
milestone: 6.1 → 7.0
Dennis Dmitriev (ddmitriev)
Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → Dennis Dmitriev (ddmitriev)
status: Confirmed → In Progress
Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :

The test case should cover the situation when a volume device is not ready yet when fuel-agent is going to partition a volume.

fuel-agent is waiting for kernel until it creates the volume device using the command 'udevadm settle'.

In the test case, when bootstrap image is loaded, step 3 "run something that will load VM's all cpu cores heavily" does not make sense because in the test environment all devices will be already created, and test will always pass.

There is needed a low-level solution of how to make the custom situation when /dev/vda is busy and 'udevadm settle' will be waiting until /dev/vda becomes ready.

Changed in fuel:
status: In Progress → Incomplete
assignee: Dennis Dmitriev (ddmitriev) → Fuel QA Team (fuel-qa)
Revision history for this message
Timur Nurlygayanov (tnurlygayanov) wrote :

Do we have any update? This issue is in Incomplete state more than 1 month without any changes, I'm going to change the status to Invalid. Please, update the status if we need to fix something here.

Changed in fuel:
status: Incomplete → Invalid
Sergey Shevorakov (sshevorakov)
Changed in fuel:
milestone: 7.0 → 9.0
status: Invalid → Confirmed
importance: High → Medium
tags: added: area-qa
removed: feature-image-based non-release
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.