*Synopsis*: onu should avoid upgrading from non-ON repos

CR 6960247 changed on Jun 10 2010 by <User 1-5Q-1267>

=== Field ============ === New Value ============= === Old Value =============

Category               consolidation               opensolaris                
Public Comments        New Note                                               
SubCategory            os-net-tools                triage-queue               
====================== =========================== ===========================

     
*Change Request ID*: 6960247

*Synopsis*: onu should avoid upgrading from non-ON repos

  Product: solaris
  Category: consolidation
  Subcategory: os-net-tools
  Type: Defect
  Subtype: 
  Status: 1-Dispatched
  Substatus: 
  Priority: 3-Medium
  Introduced In Release: 
  Introduced In Build: 
  Responsible Engineer: 
  Keywords: opensolaris

=== *Description* ============================================================
Category
    consolidation
Sub-Category
    os-net-tools
Description
    After an onu upgrade from snv_134 to snv_142, I noticed that not only ON 
packages
had been upgraded, but also e.g. virtualbox from the extra repo, which was
inststalled in a zfs dataset shared between the BEs.  I don't think this is
appropriate: onu should just upgrade O/N and nothing more (or at the very least
provide such a mode of operation.
Frequency
    Always
Regression
    no
Steps to Reproduce
    Perform onu upgrade with other repos configured.
Expected Result
    Only freshly build O/N packages are upgraded.
Actual Result
    Unrelated packages from other repos are upgraded.
Error Message(s)
    
Test Case
    
Workaround
    
Additional configuration information

*** (#1 of 1): 2010-06-10 17:12:35 GMT+00:00 <User 1-9HOB9N>


=== *Public Comments* ========================================================
I would very much like this not to happen - or at least not for "non-ON" repos,
since I have used onu to upgrade the X consolidation packages, and don't see 
why most consolidations couldn't use it to upgrade from their IPS builds.
Perhaps "not from repos other than the ones specified to upgrade from" would 
be better?

*** (#1 of 1): 2010-06-10 18:21:44 GMT+00:00 <User 1-5Q-1267>


=== *Workaround* =============================================================

=== *Additional Details* =====================================================
        Targeted Release: 
        Commit To Fix In Build: 
        Fixed In Build: 
        Integrated In Build: 
        Verified In Build: 
  See Also: 
  Duplicate of: 
  Hooks:
        Hook1: 
        Hook2: 
        Hook3: 
        Hook4: 
        Hook5: 
        Hook6: <email address omitted>
  Program Management: 
  Root Cause: 
  Fix Affects Documentation: No
  Fix Affects Localization: No

=== *History* ================================================================
        Date Submitted: 2010-06-10 17:12:35 GMT+00:00
        Submitted By: <User 1-9HOB9N>

        Status Changed    Date Updated                  Updated By


=== *Service Request* ========================================================
        Impact: Significant
        Functionality: Primary
        Severity: 2
        Product Name: solaris
        Product Release: solaris_nevada
        Product Build: snv_142
        Operating System: solaris_nevada
        Hardware: generic
        Submitted Date: 2010-06-10 17:12:35 GMT+00:00


=== *Multiple Release (MR) Cluster* - 0 ======================================

_______________________________________________
on-ips-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/on-ips-dev

Reply via email to