I totally agree with the "Request to BMC/Remedy" in order to "Document known bugs which are being worked upon for a Patch"... This applies to Core (binaries) and Applications as well...
Everyone is 'utilizing un-needed hours' of their own time, to stumble across, diagnose and then report these issues back to BMC. I certainly know our list grows by at least one "issue" per day, and we have not even rolled out ITSM 7 (yes we are at patch 3). And we are 100% INSIDE THE BOX so far other than the configuration data!!! <#include=SoapBoxLeftOvers.js GRIPE> BMC does not even update the HISTORY in objects it updates during the patches, to show the basic 5-W's (Who/What/Where/When/Why) for ease of back-tracking... If __ANY__ of my developers try to push something (v6-production mind you) into Test / Production with-out the 5-W's documented, they are taken for an "outside the building meeting of the minds" discussion... We also have gone as far as creating a "use once user" for the patch installation (will be started with V7-patch 4) ie "login = Patch7.0.4" !! Just to ensure that "Accumulative Patch is actually Accumulative"... as I have my doubts... </GRIPE> Unfortunately, we have had to resort to the following setup(s). Sandbox 1 = ITSM 7 Sandbox 2 = ITSM 7 Patch 1 Sandbox 3 = ITSM 7 Patch 2 Sandbox 4 = ITSM 7 Patch 3 (Matches our "live" environment without configuration data) (Very good thing we are Virtualized in these environments :) just press CLONE and GO so to say to get the next patch base online :):) ) Then when something goes "click-boom" we start and continue backwards validating "where" the issue came from. And then we can say "yes we tested it, but the test doc date reflects patch X and it worked THERE!"... With lately it being almost "Patch of the week" we cannot simply do a complete regression test every time!!! So if we had a list of "DO NOT TRY THIS AT HOME" so to say it would be much nicer :) Thanks-n-advance; HDT Platform Incident / Problem Manager & Architect Robert Molenda IT OS PA Tel: +1 408 503 2701 Fax: +1 408 503 2912 Mobile: +1 408 472 8097 [EMAIL PROTECTED] Quality begins with your actions. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of strauss Sent: Friday, March 09, 2007 9:59 AM To: [email protected] Subject: How about a list of Open Bugs for ITSM 7.0.01/02 Patch003? I would sure like to see the list of open bugs on ITSM 7.0.01.003 and 7.0.02.003 - we continue to trip over bugs that we can't live with in a production environment, which keeps pushing implementation farther and farther away. Has anyone heard when we can expect the next installable patch 004s to come out (Incident, Problem, Change, SLM)??? Or for that matter, when 7.0.03 will be released. I need a better code base to install than 7.0.02.003 - I am refreshing one complete AR server next week - taking it from Win2K3 x64 to Win2K3 R2 x86 to see if that resolves some of the myriad problems with AREA SSL, CAI, and basically anything that uses a run process command. The fact that you cannot install 7.0.02 over 7.0.01 (except SLM) makes the whole process of installing a newer application code base a complete rebuild, followed by weeks of configuration. We have already wasted months on this project due to buggy application code - it would be better to wait for a newer release than waste time configuring an older one that we already know is riddled with bugs. Christopher Strauss, Ph.D. Remedy Database Administrator University of North Texas Computing Center http://remedy.unt.edu/helpdesk/ ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
