Cathy Zhou wrote: > I tried to test bfu from snv_74 to the clearview-uv bits today with the > following configuration: > > a. aggr1 created over bge1 > b. /etc/hostname.aggr1 > > The system successfully booted but it fails to plumb the aggr1 interface. > The problem is that the data-link configuration migration (aggregation > creation in this case) happens in the /var/svc/profile/upgrade script, which > is run by the system/manifest-import service, and is after the > network/physical service (which plumbs the aggr1 interface). > > I am wondering while you tested system upgrade, whether the same problem > showed up. > > I can think of two options to solve this problem: > > 1. Instead of write those "dladm" commands to /var/svc/profile/upgrade, we > write it to another script, and run that script at the very beginning of > network/physical service. > > 2. Change the dependency so that instead of system/manifest-import depending > on network/physical, we make network/physical depends on > system/manifest-import.
Another potential option: 3. Create a dlmgmt-upgrade service which disables itself the first time it is run. This service would read the dladm command from the custom script described in 1. The inetd-upgrade service is similar to this. > Option 2 requires to break the current dependency between manifest-import > and network/physical. I don't know it is possible. Today, > system/manifest-import indirectly depends on network/iscsi_initiator and > system/identity:node, which both depends on network/physical. I don't think option 2 is feasible. -Seb
