Commits on Feb 1, 2012
Commits on Jan 31, 2012
Commits on Jan 30, 2012
  1. Merge branch 'promotion-search'

    ehelms committed Jan 30, 2012
  2. Merge branch 'master' into promotion-search

    ehelms committed Jan 30, 2012
  3. Promotion Search: Fixes for broken unit tests related to adding

    index_packages during promotion.
    ehelms committed Jan 30, 2012
  4. Promotion Search - Fixes issue with tupane slider showing up partially

    inside the left side tree.
    ehelms committed Jan 30, 2012
  5. 748060 - fix bbq on promotions page

    Due to a race condition, the bbq for the promotions page was not
    behaving properly when user was viewing an item from the content
    tree (e.g. distro, pkg, errata).  Essentially, the panel would
    receive and process the hash_change event for the list of items
    (e.g. distros) was rendered in the content tree.  As a result, it
    would not be able to display the item that was previously selected
    (e.g. a distro).
    bbuckingham committed Jan 30, 2012
  6. Promotion Search - Re-factors search enabling on sliding tree to be more

    stand alone and decoupled.  Fixes issues with search widget not closing
    properly on tab changes.
    ehelms committed Jan 30, 2012
  7. 757094 - Product should be readable even it has no enabled repos

    Editable as well. Otherwise we can't enable the repos.
    iNecas committed Jan 30, 2012
  8. Promotion Search - Adds proper checks when there is no next environment

    for listing promotable packages.
    ehelms committed Jan 30, 2012
  9. 785703 - fixing user creation code

    lzap committed Jan 30, 2012
  10. Revert "Make default logging level be warn"

    If this method (or any orchestration action) returns false (or nil), our
    orchestration is stopped with an error.
    Unfortunately (or thankfully) after Bryan's patch (setting logging level to
    info) the statement started to return nil which
    effectively stopped our orchestration.
    We obviously test this with higher levels (e.g. debug) but not lower levels
    (like warn or fatal or error :-)
    I am reverting Bryan's change, because I already did a review of our info
    logging messages and we should not have many of them anymore (only six).
    I created new BZ for this issue - we should review all possible settings of
    KATELLO_LOGGING. We might need to correct all orchestration action methods,
    or maybe the way we deal with return values from them. That would fix them
    lzap committed Jan 30, 2012