Task from example_v3 plugin was run twice

(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:

actual result

expected result

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

Actually, if you look into the logs, you will see that this is just a way of how puppet reports its logs. This is not the root cause. This bug is actually a duplicate of another one.

We passed SCF for 9.0. Moving medium bug to the Newton release

I'm putting this on hold until this https://review.openstack.org/#/c/333211/ is merged. Puppet debug logs could tell us more about why deploy.pp seemed to be applied twice.

It reproduced here https://product-ci.infra.mirantis.net/job/9.0.system_test.ubuntu.plugins.fuel_plugin_example/171/
Now we have puppet debug logs.

My bad, no debug logs, haven't cherrypicked to the stable/mitaka :(

So, waiting for https://review.openstack.org/#/c/340973/

The change has been merged on July, 19, waiting for the problem to reproduce.

issue was reproduced again 9.0+snapshot#76 (swarm 9.1)
https://mirantis.testrail.com/index.php?/tests/view/10388516
https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.plugins.fuel_plugin_example/17/testReport/(root)/deploy_ha_one_controller_neutron_example_v3/

Diagnostic snapshot is also available: https://drive.google.com/open?id=0B2ag_Bf-ShtTZTlpV3JfT2NDbVU

Guys, were there any changes recently on srv85? Like reinstalling it from scratch, or just libvirt or fuel-devops update? It, actually, was green quite recently.

Also, please ensure that syslinux is installed on the slave where the test is being run.

Oops, sorry - wrong window :(

Fresh failure on Swarm with the same reason:

https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.plugins.fuel_plugin_example/18/testReport/%28root%29/deploy_ha_one_controller_neutron_example_v3/

Logs are available here: https://drive.google.com/open?id=0B5HPBFb7K7gXVUhfZGFwTTZCVlE

Moving it back to confirmed...

Moving to High, since it fails 1 Swarm TC

Could you please include this https://review.openstack.org/#/c/354644/ commit into the build?

This bug is medium priority because it doesn't create any issues for users.

Status changed to Confirmed because the issue reproduced again.

Status changed to High because it affects SWARM pass rate and can affect our customers in the result.

It CANNOT affect customers! Applying puppet manifest twice gives the same result.

This is a medium priority issue that doesn't affect customers and we still waiting for extra debug info.

After fixing blocking https://bugs.launchpad.net/fuel/+bug/1621429, we have seen new failure:
https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.plugins.fuel_plugin_example/68/testReport/(root)/deploy_ha_one_controller_neutron_example_v3/deploy_ha_one_controller_neutron_example_v3/

Sure, but I need either to reproduce it locally or run the test with my patch https://review.openstack.org/#/c/354644/

Can we please get ETA for this bug fix, it is currently blocking one of the fixes that QA needs to fix Swarm blocking issue.

Reproduced an issue with more logging. This is for sure not a graph related issue. PuppetTask is run by Astute only once.

This code in Astute is most probable candidate:
https://github.com/openstack/fuel-astute/blob/master/lib/astute/puppet_task.rb#L159-L171

ETA is 2-3 days.

This https://github.com/openstack/fuel-astute/blob/master/lib/astute/puppet_task.rb#L159-L171 is for sure to blame.

The reason is that we poll puppet status somewhere inbetween puppets writes to its status file. At this point puppet status is already written, but the timestamp of the last run is not. This breaks Astute logic around this.

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/374033

Reviewed: https://review.openstack.org/374033
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=e5311dd97b4120d7aacd19b812e5548cfa5fd5e9
Submitter: Jenkins
Branch: stable/mitaka

commit e5311dd97b4120d7aacd19b812e5548cfa5fd5e9
Author: Georgy Kibardin <email address hidden>
Date: Wed Sep 21 13:58:45 2016 +0300

    Remove puppet status files right before running it

    This prevents us from picking up status files from previous run when
    current run hasn't written them for some reason, i.e. crash etc.

    Change-Id: I83d0b4aa3c42210279b75ed7b575919d2d092ff0
    Closes-Bug: #1560026

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

Test was passed (#72 https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.plugins.fuel_plugin_example/72/testReport/(root)/deploy_ha_one_controller_neutron_example_v3/)

Reviewed: https://review.openstack.org/374221
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=ac2703949fdbb9160a4ea6b722e9f1855356577f
Submitter: Jenkins
Branch: master

commit ac2703949fdbb9160a4ea6b722e9f1855356577f
Author: Georgy Kibardin <email address hidden>
Date: Wed Sep 21 13:58:45 2016 +0300

    Remove puppet status files right before running it

    This prevents us from picking up status files from previous run when
    current run hasn't written them for some reason, i.e. crash etc.

    Change-Id: I83d0b4aa3c42210279b75ed7b575919d2d092ff0
    Closes-Bug: #1560026
    (cherry picked from commit e5311dd97b4120d7aacd19b812e5548cfa5fd5e9)

This issue was fixed in the openstack/fuel-astute 10.0.0rc1 release candidate.

This issue was fixed in the openstack/fuel-astute 10.0.0 release.