Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pickup Tower Project's repo-sync status #14687

Merged
merged 2 commits into from Apr 11, 2017
Merged

Conversation

jameswnl
Copy link
Contributor

@jameswnl jameswnl commented Apr 7, 2017

To allow user to know if Tower's latest attempt to sync a repo's playbooks is successful or not.

Part of the pivotal tracker story

Note: the other property we can use (instead of last_update_failed) is the status ([successful|failed|missing|...]). Obviously, we can have both of them (plus some other fields) captured. They all give us different aspects of the repo state. But I think we probably want to be as frugal as possible. And status needs string comparison, vs the last_update_failed boolean check, I pick boolean.

But 1 point to consider status is that In Tower, there's a manual type repo, there wouldn't be a sync and so last_update_failed won't be meaningful. The project.status would show if there's problem with it.

However, we only support Git type now. so I need someone to push one way or the other. ( @Fryguy @blomquisg )

@miq-bot add_labels enhancement, providers/ansible_tower, fine/yes

==== Updates ====
Switched to pickup status instead of last_update_failed

==== Related bug ====
https://bugzilla.redhat.com/show_bug.cgi?id=1439357

Copy link
Member

@durandom durandom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

besides rubocop alignment 👍

Copy link
Member

@carbonin carbonin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is going to be confusing. Brace yourselves.

When we branched fine we changed the spec that insures migrations will always be run in order. This makes backporting migrations to fine ... difficult.

Since fine was branched more migrations have been added to master, specifically these:

20170324124452_add_vendor_property_to_physical_server.rb
20170328110106_fix_expression_in_tenant_quota_report.rb
20170404213245_add_loc_led_state_to_physical_servers.rb

These migrations were not backported to fine.
The last migration in the fine branch is 20170320195659_remove_oid_integer_args_from_miq_queue.rb

This means that for us to backport this safely, your migration needs to be numbered between 20170320195659 and 20170324124452 - preferably an earlier number, in case we need to do this again. I'll go ahead and suggest 20170320195660

@jameswnl
Copy link
Contributor Author

jameswnl commented Apr 7, 2017

@carbonin thanks, I've renamed the file to that timestamp you suggested.

@durandom I've updated the code, to pick up status instead of last_update_failed, status would be more informative.

@miq-bot
Copy link
Member

miq-bot commented Apr 7, 2017

Checked commits jameswnl/manageiq@46ae44b~...dd66fdd with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
4 files checked, 0 offenses detected
Everything looks good. 🍪

Copy link
Member

@carbonin carbonin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @jameswnl

@jameswnl jameswnl changed the title Pickup Tower Project's last_update_failed Pickup Tower Project's repo-sync status Apr 10, 2017
@jameswnl
Copy link
Contributor Author

@miq-bot add_label bug

@miq-bot miq-bot added the bug label Apr 11, 2017
@jameswnl
Copy link
Contributor Author

jameswnl commented Apr 11, 2017

@Fryguy can you merge this? Greg B is on PTO this week.

Or @bdunne

@Fryguy Fryguy merged commit 84006ef into ManageIQ:master Apr 11, 2017
@Fryguy Fryguy added this to the Sprint 59 Ending Apr 24, 2017 milestone Apr 11, 2017
simaishi pushed a commit that referenced this pull request Apr 11, 2017
Pickup Tower Project's repo-sync status
(cherry picked from commit 84006ef)
@simaishi
Copy link
Contributor

Fine backport details:

$ git log -1
commit 8479214d9e5f57b60c136763fb9414a91e7e7f10
Author: Jason Frey <fryguy9@gmail.com>
Date:   Tue Apr 11 10:58:10 2017 -0400

    Merge pull request #14687 from jameswnl/repo-status
    
    Pickup Tower Project's repo-sync status
    (cherry picked from commit 84006ef20e6b0b17b286478769594e7b656bf4d3)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants