OCSNG-Windows-Agent-Setup_done corrupt after Agent deployment upgrade

Bug #1015434 reported by MaRauch
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OCS Inventory: Windows Agent
Fix Released
Medium
Didier Liroulet

Bug Description

Hi,

when deploying the new Agent version through the deployment process we see that the resulting file (OCSNG-Windows-Agent-Setup_done) only contains the line "SUCCESS" but without the packet ID as the next line. Therefore the new Agent can not send the result back to server and will not remove the download-packet directory. This results into a continuous reinstall loop of the agent at each inventory-launch.
The new agent version is installed successfully and sending new inventories correctly. The only problem is that the deployment process will not finish with this problem and no further deployment is possible.

Solution 1:
When inserting the packet ID manually into the result-file after SUCCESS the agent will send the result back and finish deployment on next inventory-launch.
Solution 2:
Manually deleting the download-packet directory will unblock further deployments. But not resulting code will be sent to server (stuck at Waiting for notification)

Server-Version: 2.0.5
pre-upgrade-Agent version: 2.0.0.20 (same behavior when deploying over a 2.0.4 version!)
upgrade-Agent version: 2.0.4
Packet deployed through "Launch" using: /UPGRADE /SERVER=http://xxx.xxx.xxx.xxx/ocsinventory /S /NOSPLASH /NO_SYSTRAY /NOW /NOTAG /SSL=0

Logfile:
==============================================================================
Starting OCS Inventory NG Agent on Sunday, June 17, 2012 18:44:44.
AGENT => Running OCS Inventory NG Agent Version 2.0.4.0
AGENT => Using OCS Inventory NG FrameWork Version 2040
AGENT => Loading plug-in(s)
 PLUGIN => Searching for Plug-in DLL(s) in folder <C:\Program Files\OCS Inventory Agent\plugins>
 PLUGIN => 0 Plug-in(s) succesfully loaded
AGENT => Using network connection with Communication Server
 COM PROVIDER => Loading Communication Provider <C:\Program Files\OCS Inventory Agent\ComHTTP.dll>
AGENT => Using Communication Provider <OCS Inventory NG cURL Communication Provider> Version <2.0.4.0>
AGENT => Sending Prolog
 DID_CHECK => Read DeviceID <S01-GOO0417FPQ-2011-08-18-15-17-28> and MACs <1C:C1:DE:57:B2:23> in file <ocsinventory.dat>
 COM SERVER => Initializing cURL library for sendRequest
 COM SERVER => Using cURL with server authentication
 COM SERVER => Disabling cURL proxy support
 COM SERVER => Disabling cURL SSL server validation support
 COM SERVER => Sending HTTP Post request to URL <http://xxx.xxx.xxx.xxx/ocsinventory>
 COM SERVER => HTTP Post response received <HTTP Status Code #200>
 COM SERVER => Cleaning cURL library
================= TRACE START ===============
<?xml version='1.0' encoding='UTF-8'?>
<REPLY>
  <SUPPORT_LOG>No support registered for your installation. Check OCS Inventory NG support packages at http://www.ocsinventory-ng.com</SUPPORT_LOG>
  <OPTION>
    <NAME>DOWNLOAD</NAME>
    <PARAM FRAG_LATENCY="10" PERIOD_LATENCY="1" TIMEOUT="30" ON="1" TYPE="CONF" CYCLE_LATENCY="60" PERIOD_LENGTH="10" />
    <PARAM ID="1339939229" CERT_PATH="INSTALL_PATH" PACK_LOC="xxx.xxx.xxx.xxx/download" CERT_FILE="INSTALL_PATH/cacert.pem" TYPE="PACK" INFO_LOC="xxx.xxx.xxx.xxx/download" />
  </OPTION>
  <RESPONSE>SEND</RESPONSE>
  <PROLOG_FREQ>10</PROLOG_FREQ>
</REPLY>

================= TRACE STOP ===============
AGENT => Prolog successfully sent
SUPPORT => No support registered for your installation. Check OCS Inventory NG support packages at http://www.ocsinventory-ng.com
 AGENT => Prolog Frequency set to 10 hour(s)
AGENT => Inventory required
AGENT => Launching hardware and software checks
 INVENTORY => Loading Download history
 INVENTORY => Adding Download Package <1309348400> to report
 INVENTORY => Logged on user ID is <userl>
 INVENTORY => Operating System is <Microsoft Windows 7 Enterprise 6.1.7601 Service Pack 1>, description <>
 INVENTORY => Operating System uses 32 bits memory address width
 INVENTORY => Computer domain or workgroup is <xxx.xxx.xxx.xxx>
 WARNING *** INVENTORY => Failed to retrieve user domain
 INVENTORY => System Manufacturer <Hewlett-Packard>, System Model <HP Compaq 8000 Elite SFF PC>, System S/N <CZC0417FPQ>, Bios Manufacturer <Hewlett-Packard>, Bios Date <10/22/2009>, Bios Version <786G7 v01.02>
 INVENTORY => 1 processor(s) Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz [2 core(s) x64] at 3000 MHz
 INVENTORY => OS Memory 3543 MB, OS Swap size 3862 MB
 INVENTORY => 5 memory slot(s) found
 INVENTORY => 2 input device(s) found
 INVENTORY => 34 system port(s) found
 INVENTORY => 4 system slot(s) found
 INVENTORY => 16 system controler(s) found
 INVENTORY => 2 storage peripheral(s) found
 INVENTORY => 1 sound device(s) found
 WARNING *** INVENTORY => Failed to retrieve modems
 INVENTORY => 1 network adapter(s) found
 INVENTORY => 5 system printer(s) found
 INVENTORY => 2 video adapter(s) found
 INVENTORY => 1 system monitor(s) found
 INVENTORY => Default IPv4 address is <xxx.xxx.xxx.xxx>
 INVENTORY => Registered company <@domainou>, registered owner <user name>, Product ID <55041-00...>
 INVENTORY => Product key <BBBBB-BB...>
 INVENTORY => 124 software found
 INVENTORY => Computer/VM UUID is <xxx.xxx.xxx.xxx>
 INVENTORY => Computer seems to be physical host
 INVENTORY => Bogus summed Memory Slots, 4096 is too far from 3543 (keeping the last one)
 INVENTORY => Reading last inventory state
AGENT => Communication Server ask for Package Download
 DOWNLOAD => Package history file successfully cleaned for duplicate IDs
 DOWNLOAD => Found OCS Inventory Agent Setup result file <C:\ProgramData\OCS Inventory NG\Agent\download\OCSNG-Windows-Agent-Setup_done>
ERROR *** DOWNLOAD => Found result code <SUCCESS> for OCS Inventory Agent Setup package but no package ID specified, so unable to send result code
DOWNLOAD => Download and setup tool successfully started
 EXECUTABLE PLUGIN => Searching for VBS script(s) in folder <C:\Program Files\OCS Inventory Agent\plugins>
 EXECUTABLE PLUGIN => Found executable plugin <msoffice-key.vbs>
 EXECUTABLE PLUGIN => Plugin <msoffice-key.vbs> executed successfully
 EXECUTABLE PLUGIN => Searching for executable(s) in folder <C:\Program Files\OCS Inventory Agent\plugins>
AGENT => Sending Inventory
 INVENTORY => Checking last inventory state
 INVENTORY => Logical drives inventory state changed
INVENTORY => Inventory changed since last run
 INVENTORY => Generating XML document with Device properties
 INVENTORY => XML Update 5 Logical Drive(s)
 INVENTORY => XML Update common Device properties
 INVENTORY => XML Update BIOS
 INVENTORY => XML Update 2 Input Device(s)
 INVENTORY => XML Update 34 System Port(s)
 INVENTORY => XML Update 16 System Controler(s)
 INVENTORY => XML Update 4 System Slot(s)
 INVENTORY => XML Update 1 Sound Device(s)
 INVENTORY => XML Update 2 Storage Peripheral(s)
 INVENTORY => XML Update 2 Logical Drive(s)
 INVENTORY => XML Update 0 Modem(s)
 INVENTORY => XML Update 1 Network Adapter(s)
 INVENTORY => XML Update 2 Video Adapter(s)
 INVENTORY => XML Update 1 Monitor(s)
 INVENTORY => XML Update 5 Printer(s)
 INVENTORY => XML Update 125 Software
 INVENTORY => XML Update 0 Registry Value(s)
 INVENTORY => XML Update Administrative Information(s)
 COM SERVER => Initializing cURL library for sendRequest
 COM SERVER => Using cURL with server authentication
 COM SERVER => Disabling cURL proxy support
 COM SERVER => Disabling cURL SSL server validation support
 COM SERVER => Sending HTTP Post request to URL <http://xxx.xxx.xxx.xxx/ocsinventory>
 COM SERVER => HTTP Post response received <HTTP Status Code #200>
 COM SERVER => Cleaning cURL library
================= TRACE START ===============
<?xml version='1.0' encoding='UTF-8'?>
<REPLY>
  <RESPONSE>NO_ACCOUNT_UPDATE</RESPONSE>
</REPLY>

================= TRACE STOP ===============
AGENT => Inventory successfully sent
 INVENTORY => Writing new inventory state
AGENT => Unloading communication provider
AGENT => Unloading plug-in(s)
AGENT => Execution duration: 00:00:08.

Revision history for this message
alexinthesky (alexandrechappaz) wrote :

I observe the same behavior :
upgrading from v 4061 to 2.0.4.0 though the teledeployement, except the status is stuck in "BAD_DIGEST".

seems like this is a wanted behavior as in the code of the windows agent:
Agent/CapDownlad.cpp, line 316 :

 if (csID.IsEmpty())
 {
  // Upgrading from agent 1.X or previous to 2.0.0.22 ?
  m_pLogger->log(LOG_PRIORITY_ERROR, _T( "DOWNLOAD => Found result code <%s> for OCS Inventory Agent Setup package but no package ID specified, so unable to send result code"), csCode);
  return FALSE;
 }

Do you think of a way to automatise one of the the workarounds descibed?

Changed in ocsinventory-windows-agent:
assignee: nobody → Didier Liroulet (dliroulet)
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Didier Liroulet (dliroulet) wrote :

Hi.

First of all, alexinthesky, concerning update from version v1.x or v2 previous to 2.0.0.22, there is a security flaw in deployment mechanism, which could allow a user to run a command using OCS system service account, even if user is not local administrator and, so, possibly gain administrator privileges. This flaw is fixed on 2.0.0.22 or higher by computing a Digest on all package downloaded by agent, and refusing running package command with error BAD_DIGEST. We did not find any solution as workaround of this, when upgrading from v1.X to v2 :-( So, having a BAD_DIGEST error when upgrading from v1.x is a normal behavior.

Second, since v2.0.0.22, MaRauch's solution 1 is implemented in agent. When agent unzip package in Windows temp folder, it creates a file "OCSNG-Windows-Agent-PackageID" when contains package ID. When you launch agent's setup from this folder using /UPGRADE parameter, setup try to read this file (normally located in the same folder) to use the Package ID.

I will check this to ensure there is no problem here.

Regards

Revision history for this message
Didier Liroulet (dliroulet) wrote :

Hi.

Here is a new version of agent fixing numerous bugs, including this one I hope.

Could you please try it and ensure you don't encounter the problem any more when upgrading agent 2.0.0.22 or higher ?

Regards

Revision history for this message
MaRauch (martin-rauch) wrote :
Download full text (6.2 KiB)

Hi,

did a test on on machine. Unfortunately the same behavior as before. The new agent gets installed correctly but the file "OCSNG-Windows-Agent-Setup_done" gets created in the download directory only with one line "SUCCESS" and not package ID.
Consecutive Agent-runs will rerun the installation over and over again.

Here's the download.log:
==============================================================================
Starting OCS Inventory NG Package Download and Setup Tool on Sunday, July 22, 2012 10:47:34.
DOWNLOAD => Running OCS Inventory NG Download Version 2.0.4.0
DOWNLOAD => Using OCS Inventory NG FrameWork Version 2040
DOWNLOAD => Using network connection with Communication Server
 COM PROVIDER => Loading Communication Provider <C:\Program Files\OCS Inventory Agent\ComHTTP.dll>
DOWNLOAD => Using Communication Provider <OCS Inventory NG cURL Communication Provider> Version <2.0.4.0>
DOWNLOAD => Starting new period of 10 cycles
 DOWNLOAD => Flushing package queue
DOWNLOAD => Parsing directory <C:\ProgramData\OCS Inventory NG\Agent\download> for packages
 DOWNLOAD => Verifying package <C:\ProgramData\OCS Inventory NG\Agent\download\1342944280>
DOWNLOAD => Package <1342944280> verified and added to process queue
 DOWNLOAD => Processing packages for cycle 1 on Sunday, July 22, 2012 10:47:34
 DOWNLOAD => Pausing for cycle latency (60 seconds)
 DOWNLOAD => Processing packages for cycle 2 on Sunday, July 22, 2012 10:48:34
 DOWNLOAD => Pausing for cycle latency (60 seconds)
 DOWNLOAD => Processing packages for cycle 3 on Sunday, July 22, 2012 10:49:34
 DOWNLOAD => Pausing for cycle latency (60 seconds)
 DOWNLOAD => Processing packages for cycle 4 on Sunday, July 22, 2012 10:50:34
 DOWNLOAD => Pausing for cycle latency (60 seconds)
 DOWNLOAD => Processing packages for cycle 5 on Sunday, July 22, 2012 10:51:34
DOWNLOAD => Downloading package fragment <1342944280-1>
 COM SERVER => Initializing cURL library for getFile
 COM SERVER => Using cURL with server authentication
 COM SERVER => Disabling cURL proxy support
 COM SERVER => Disabling cURL SSL server validation support
 COM SERVER => Sending fileGet request to URL <HTTP://xx.xx.xx.xx/download/1342944280/1342944280-1>
 COM SERVER => fileGet response received <HTTP Status Code #200>
 COM SERVER => Cleaning cURL library
 DOWNLOAD => Pausing for fragment latency (10 seconds)
 DOWNLOAD => Pausing for cycle latency (60 seconds)
 DOWNLOAD => Processing packages for cycle 6 on Sunday, July 22, 2012 10:52:45
 DOWNLOAD => Pausing for cycle latency (60 seconds)
 DOWNLOAD => Processing packages for cycle 7 on Sunday, July 22, 2012 10:53:45
 DOWNLOAD => Pausing for cycle latency (60 seconds)
 DOWNLOAD => Processing packages for cycle 8 on Sunday, July 22, 2012 10:54:45
 DOWNLOAD => Pausing for cycle latency (60 seconds)
 DOWNLOAD => Processing packages for cycle 9 on Sunday, July 22, 2012 10:55:45
 DOWNLOAD => Pausing for cycle latency (60 seconds)
 DOWNLOAD => Processing packages for cycle 10 on Sunday, July 22, 2012 10:56:45
DOWNLOAD => Building package <1342944280>
 PACKAGE => Verifying fragment files of package <1342944280>
 PACKAGE => Checking free disk space for package <1342944280>
 PACKAGE => Bu...

Read more...

Revision history for this message
Didier Liroulet (dliroulet) wrote :

Hi MaRauch,

When upgrade 2.0.4 to 2.0.4.2, it works on my test platform. So, could you please look for folder "PackageID.ocs" into Windows Temp directory ?

There must be a folder with agent's setup files.

1) Is there in this folder is a file named "OCSNG-Windows-Agent-PackageID" ? Does it contains package ID ?

2) Is there a file named "OCS-NG-Windows-Agent-Setup.log" ? Could you paste it here ?

Thanks by advance.

Regards

Revision history for this message
MaRauch (martin-rauch) wrote :

Hi,

I tried it again with the same result. Here is the log information:

OCS-NG-Windows-Agent-Setup.log:
********************************************************
Starting OCS Inventory NG Agent 2.0.4.2 setup on 24/07/2012 at 18:12:07
Checking if setup not already running...OK.
Checking Operating System...OK, Windows 2000 or higher.
Command line is: OCSNG-Windows-Agent-2.0.4.2\OCS-NG-Windows-Agent-Setup.exe /UPGRADE /SERVER=http://xx.xx.xx.xx/ocsinventory /S /NOSPLASH /NO_SYSTRAY /NOW /NOTAG /SSL=0
Parsing command line arguments...OK.
Checking for silent mode...Enabled.
Checking for splash screen...Disabled.
Checking if logged in user has Administrator privileges...OK.
Creating directory <C:\ProgramData\OCS Inventory NG\Agent>...
SetACL allowing Users / Power users read/write permissions on <C:\ProgramData\OCS Inventory NG\Agent>...Result: 0
SetACL propagating inherited permissions on <C:\ProgramData\OCS Inventory NG\Agent\Download>...Result: 0
Trying to determine if service was previously installed...Yes.
Trying to stop service and kill processes...
Is Service <OCS Inventory Service> running...Yes.
Trying to stop Service <OCS Inventory Service>...Ok
Is Service <OCS Inventory Service> running...No - Waiting 1 second(s) for Service to stop...
Trying to kill process OcsSystray.exe...Result: 603
Trying to kill process OcsService.exe...Result: 603
Trying to kill process OCSInventory.exe...Result: 603
Trying to kill process download.exe...Result: 0
Trying to kill process inst32.exe...Result: 603
Waiting 10 seconds for processes to terminate...
Copying new files to directory <C:\Program Files\OCS Inventory Agent>...
Windows XP or higher detected, installing default cURL library and MS CRT/MFC 9.0...
Copying new files status is ;-)
Writing agent configuration file by launching ocsinventory.exe /SAVE_CONF...Result: 0
[/NO_SYSTRAY] used, so removing Systray applet startup menu shortcut <C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\OCS Inventory NG Systray.lnk>...
Checking if service OCS Inventory Service is registered into Windows Service Manager...Yes
Nothing to do to register OCS Inventory Service into Windows Service Manager.
Starting OCS Inventory Service...Ok.
Writing setup result <SUCCESS> for Package ID <> to file <C:\ProgramData\OCS Inventory NG\Agent\Download\OCSNG-Windows-Agent-Setup_done>...
SUCCESS: OCS Inventory NG Agent 2.0.4.2 successfuly installed on 24/07/2012 at 18:12:54
;-)

File "done" contains:
SUCCESS

File "OCSNG-Windows-Agent-PackageID" contains the packet-id:
1343145556

Revision history for this message
Didier Liroulet (dliroulet) wrote :

Ok, I understand where is the problem.

Installer "OCS-NG-Windows-Agent-Setup.exe" search for file "OCSNG-Windows-Agent-PackageID" in the same folder.

But, you're launching installer from a sub folder "OCSNG-Windows-Agent-2.0.4.2" of the folder containing "OCSNG-Windows-Agent-PackageID" file.

That's why installer cannot find corresponding package ID.

So, I can write a fix to also search for "OCSNG-Windows-Agent-PackageID" file in parent folder, but only one level.

I think it will cover most a the case for agent deploying.

Stay tuned.

Regards

Changed in ocsinventory-windows-agent:
status: In Progress → Fix Committed
Revision history for this message
Didier Liroulet (dliroulet) wrote :

Hi.

Here a 2.0.4.3 release of agent, which the previously described workaround.

Could you please check if it is working in your environment ?

Regards

Revision history for this message
MaRauch (martin-rauch) wrote :

Hi,

I tried it on two systems. One was working the other one not. I have to investigate further what the difference is.

Here is the log file:

********************************************************
Starting OCS Inventory NG Agent 2.0.4.3 setup on 27/07/2012 at 15:45:13
Checking if setup not already running...OK.
Checking Operating System...OK, Windows 2000 or higher.
Command line is: OCSNG-Windows-Agent-2.0.4.3\OCS-NG-Windows-Agent-Setup.exe /UPGRADE /SERVER=http://xx.xx.xx.xx/ocsinventory /S /NOSPLASH /NO_SYSTRAY /NOW /NOTAG /SSL=0
Parsing command line arguments...OK.
Checking for silent mode...Enabled.
Checking for splash screen...Disabled.
Checking if logged in user has Administrator privileges...OK.
Creating directory <D:\Dokumente und Einstellungen\All Users\Anwendungsdaten\OCS Inventory NG\Agent>...
SetACL allowing Users / Power users read/write permissions on <D:\Dokumente und Einstellungen\All Users\Anwendungsdaten\OCS Inventory NG\Agent>...Result: 0
SetACL propagating inherited permissions on <D:\Dokumente und Einstellungen\All Users\Anwendungsdaten\OCS Inventory NG\Agent\Download>...Result: 0
Trying to determine if service was previously installed...Yes.
Trying to stop service and kill processes...
Is Service <OCS Inventory Service> running...Yes.
Trying to stop Service <OCS Inventory Service>...Ok
Is Service <OCS Inventory Service> running...No - Waiting 1 second(s) for Service to stop...
Trying to kill process OcsSystray.exe...Result: 603
Trying to kill process OcsService.exe...Result: 603
Trying to kill process OCSInventory.exe...Result: 603
Trying to kill process download.exe...Result: 0
Trying to kill process inst32.exe...Result: 603
Waiting 10 seconds for processes to terminate...
Copying new files to directory <C:\Programme\OCS Inventory Agent>...
Windows XP or higher detected, installing default cURL library and MS CRT/MFC 9.0...
Copying new files status is ;-)
Writing agent configuration file by launching ocsinventory.exe /SAVE_CONF...Result: 0
[/NO_SYSTRAY] used, so removing Systray applet startup menu shortcut <D:\Dokumente und Einstellungen\All Users\Startmenü\Programme\Autostart\OCS Inventory NG Systray.lnk>...
Checking if service OCS Inventory Service is registered into Windows Service Manager...Yes
Nothing to do to register OCS Inventory Service into Windows Service Manager.
Starting OCS Inventory Service...Ok.
Writing setup result <SUCCESS> for Package ID <> to file <D:\Dokumente und Einstellungen\All Users\Anwendungsdaten\OCS Inventory NG\Agent\Download\OCSNG-Windows-Agent-Setup_done>...
SUCCESS: OCS Inventory NG Agent 2.0.4.3 successfuly installed on 27/07/2012 at 15:46:06
;-)

Revision history for this message
Didier Liroulet (dliroulet) wrote :

Hi.

It seems that agent setup is not able to read Package ID (file OCSNG-Windows-Agent-PackageID) in his folder, or his parent folder.

In your case, file is located into Windows temp directory under directory "packageid.ocs" or "packageid.ocs\OCSNG-Windows-Agent-2.0.4.3"

Could please check that ?

Regards

Revision history for this message
MaRauch (martin-rauch) wrote :

Hi,

I did some further test with different OSs (XP, Vista, Win7). Apparently all of them installed successfully and created the "done" file correctly.
You should add it into your documentation that the ZIP-file should be created with only one subdirectory (for 2.0.4.3 and above) or even with a flat layout for agent based upgrades below 2.0.4.

Martin

Revision history for this message
Didier Liroulet (dliroulet) wrote :

Thanks for your help Martin.

Regards

Revision history for this message
Didier Liroulet (dliroulet) wrote :

Released in 2.0.5

Regards

Changed in ocsinventory-windows-agent:
status: Fix Committed → Fix Released
Revision history for this message
Artur (artur-wilman) wrote :

Unfortunatly, the problem still exist in 2.0.5 version. Here is my log file:

Starting OCS Inventory NG Agent on Wednesday, February 06, 2013 08:59:54.
AGENT => Running OCS Inventory NG Agent Version 2.0.5.0
AGENT => Using OCS Inventory NG FrameWork Version 2.0.5.0
AGENT => Loading plug-in(s)
AGENT => Using network connection with Communication Server
AGENT => Using Communication Provider <OCS Inventory NG cURL Communication Provider> Version <2.0.5.0>
AGENT => Sending Prolog
AGENT => Prolog successfully sent
SUPPORT => No support registered for your installation. Check OCS Inventory NG support packages at http://www.ocsinventory-ng.com
AGENT => Inventory required
AGENT => Launching hardware and software checks
AGENT => Communication Server ask for Registry Query
AGENT => Sending Inventory
INVENTORY => Inventory changed since last run
AGENT => Inventory successfully sent
AGENT => Communication Server ask for Package Download
ERROR *** DOWNLOAD => Found result code <SUCCESS> for OCS Inventory Agent Setup package but no package ID specified, so remove all packages to avoid running Agent setup in loop !
DOWNLOAD => Package <1351516676> added to download queue
DOWNLOAD => Package <1357804089> added to download queue
DOWNLOAD => Download and setup tool successfully started
AGENT => Unloading communication provider
AGENT => Unloading plug-in(s)
AGENT => Execution duration: 00:00:11.

Artur

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.