Skip to content
Commits on Jan 30, 2012
  1. @lzap
  2. @lzap

    Revert "Make default logging level be warn"

    src/app/models/glue/pulp/user.rb#L39
    
    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 Rails.logger.info 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
    all.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=785722
    lzap committed Jan 30, 2012
  3. @lzap
  4. @lzap
  5. @lzap
  6. @lzap
  7. @lzap
  8. @lzap
  9. @lzap
  10. @tstrachota
  11. @tstrachota

    changesets - fixed validations

    It was not checking whether the distribution's repo has been promoted.
    Validations for other content is also simplified by this commit.
    tstrachota committed Jan 30, 2012
  12. @tstrachota
  13. @lzap
Commits on Jan 27, 2012
  1. @mbacovsky
  2. @mbacovsky

    Fixed failing tests

    mbacovsky committed Jan 28, 2012
  3. @weissjeffm
  4. @bkearney
  5. @mccun934
  6. @bkearney
  7. @knowncitizen

    Removing accounts.js

    knowncitizen committed Jan 27, 2012
  8. @lzap
  9. @mbacovsky
  10. @mbacovsky
  11. @lzap
  12. @lzap
  13. @iNecas

    769954 - org and repo names in custom repo content label

    Changing form of generated label from {product.id}-{repo.name} to
    {org.name}_{product.name}_{repo.name}. The reason is that this label is showen
    in redhat.repo and therefore it should be more user friendly.
    iNecas committed Jan 27, 2012
  14. @tstrachota
  15. @tstrachota
  16. @tstrachota
  17. @tstrachota

    filters - system tests

    tstrachota committed Jan 27, 2012
  18. @tstrachota
  19. @tstrachota

    filters - spec tests

    tstrachota committed Jan 27, 2012
  20. @tstrachota

    filters - orchestration

    tstrachota committed Jan 27, 2012
  21. @tstrachota
  22. @tstrachota
Something went wrong with that request. Please try again.