Hi Jack,
On 05/28/10 05:11 PM, Jack Schwartz wrote:
Hi Jan.
Thanks for shedding some light on this...
On 05/28/10 01:34 AM, Jan Damborsky wrote:
Hi Jack,
On 05/28/10 02:10 AM, Jack Schwartz wrote:
Hi everyone.
Currently AI doesn't copy the logfile if the install fails because
of the DDU or install errors. How come? I would like to fix this.
Mary also filed bug 16088 against Driver-Update on this very issue.
But I wonder why AI wasn't copying the logfile on errors even before
Driver-Update came along. All I can come up with is:
- if /a wasn't mounted, the copy could generate additional errors.
(Seems like a small issue to me.)
Th original idea behind this behavior was that if the installation
fails,
then we should take the shortest path to abort in order to leave the
system
as untouched as possible for the inspection.
OK...
Also target BE is left mounted on /a in this case (assuming the
failure happened
after BE was created and mounted).
Sure, and it is important that this functionality remains.
In that case, we wanted to avoid cascade of error messages not related
to the failure itself - they would be confusing and could mask the real
problem - as an recent example, see
https://defect.opensolaris.org/bz/show_bug.cgi?id=11500#c8
OK. I suspected this, but wanted to make sure there wasn't some other
reason as well...
Does anyone have a good reason why I shouldn't attempt to copy the
logfile to /a whether or not any install errors occurred?
I can see that we could make this step more robust by checking for
presence of /a/var/sadm/system/logs directory first and copy log files
only if it exists.
Yes, I was thinking along these lines as well.
Looking at existing ls_transfer() code [1], in case target directory
does not exist,
ls_transfer() calls mkdirp(3GEN) to create it. We could either go with such
approach or change the behavior as described above. That would work, since
/var/sadm/system/logs/ directory is currently being delivered by
pkg://opensolaris.org/service/management/sysidtool package.
I am also wondering if we need to enhance current error handling to
account
for situations like some of DDU failures which if my understanding is
correct
are being treated as 'non-fatal' errors ?
Currently, if the DDU is unsuccessful at installing at least one
needed package to the booted environment, a warning is issued but the
install continues. The idea here is that if something critical was
missing the install would fail anyhow, but the install should be
attempted.
If the DDU is unsuccessful at installing at least one needed package
to the target, there is a chance the system might not be bootable. In
this case the install terminates abnormally, to give the user a chance
to inspect the system before rebooting. There is a message displayed
about this just before termination.
Please feel free to let me know if you have ideas to enhance/improve
this.
I have taken a closer look at the implementation and how user is
informed and I think that user is given appropriate guidance on console
and in log file about what to do in case DDU does not succeed. To be honest,
at this point I don't have any suggestions which would improve the existing
behavior.
Jan
References:
[1]
http://src.opensolaris.org/source/xref/caiman/slim_source/usr/src/lib/liblogsvc/ls_main.c#ls_transfer
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
