Errata
From GoGrid
Open Issues
RHEL Servers Accessing Cloud Storage
Reported: 12/08/2008
Progress: 10%
Resolved: None
Severity: Minor
Description: Some RHEL servers cannot install the SAMBA client using up2date. A workaround is to install the SAMBA rpm by downloading the package from the SAMBA website using wget.
Resolution: No
Resolved Issues
Incorrect Passwords Being Set on VM's
Reported on: 04/17/2009
Progress: 100%
Resolved: 07/01/2009
Severity: Minor
Description: A small percentage of servers may experience and issue where the password is set incorrectly upon instantiation. In order to work around this, immediately delete your VM and create a new one.
Resolution: Yes
API Call grid.server.add Longer than Normal for 8GB Windows Server Deployments
Reported: 02/12/2009
Progress: 100%
Resolved: 07/01/2009
Severity: Minor
Description: There is a known bug when deploying 8GB Windows-based servers via the API that may result in the server not fully deploying. The workaround for this is to wait 30-60 minutes for the server add to time out and add another 8GB Windows server. GoGrid is actively working on this bug-fix and will address the issue in an upcoming release. You will not be charged for any server RAM hours during the deployment process.
Resolution: Yes
My.GoGrid.com Login Errors
Reported: 8/15/2008
Progress: 100%
Resolved: 5/22/2009
Severity: Minor
Description: On occasion, customers may receive 404 errors, parse errors or an LDAP authentication prompt when attempting to log into my.gogrid.com. The temporary solution to this is to clear the browser's cache (shift F5) before attempting to log in again.
Resolution: Yes
Windows Server 2003 SQL Standard User Interface Error:
Reported: 09/19/2008
Progress: 100%
Resolved: In Progress
Severity: Minor
Last Update: 09/22/2008
Description: When deploying a Windows 2003 Server with MSSQL 2005 Standard installed, the user-interface incorrectly displays a confirmation request for MSSQL 2005 Workgroup. The actual image will have MSSQl 2005 Standard installed on it. This is a user-interface typo and can be ignored.
Resolution: Yes
New servers remain in Building State
Reported: 7/22/2008
Progress: 100%
Resolved: 10/17/2008
Severity: Moderate
Last update: 10/17/2008
Description: On occasion, a newly added server shows it is in a built state (yellow indicator) even though the system is live and responds to ping and can be accessed remotely.
Resolution: Yes
HTTPS/Header inserts = SSL Acceleration
Reported: 7/21/2008
Progress: 100%
Resolved: 8/13/2008
Severity: Minor
Last update: 8/13/2008
Description: When building an SSL load balancer, the httpxff profile is placed on the VIP, breaking the service.
Resolution: Yes
Red Hat Images up2date/Red Hat Update Agent
Reported: 5/25/2008
Progress: 100%
Resolved: 7/19/2008
Severity: Minor
Last update: 7/21/2008
Description: Users running Red Hat Enterprise Linux servers cannot retrieve packages from the Red Hat Network (RHN). The Systems Team is currently
working on a fix that gives each server a unique activation to RHN. The bug is expected to be resolved in 1-2 weeks.
Resolution: Yes
Network Bridging
Reported: 5/15/2008
Progress: 100%
Resolved:7/10/2008
Severity: Moderate
Last update: 7/21/2008
Description: Servers lose connectivity to the Internet. The bug affects both Windows and Linux servers. The root cause is related to the Xen Hypervisor and the associated paravirtualization drivers on the guest OS. The Xen Hypervisor has been patched with an updated service pack and the bug appears to have resided, however, the Systems Team is doing further testing to ensure the bug is completely resolved. A full resolution is expect in 1 week.
Resolution: Yes
F5 X-fer Forward (Header Inserts)
Reported: 5/10/2008
Progress: 100%
Resolved: 7/19/2008
Severity: Minor
Last update: 7/21/2008
Description: F5 users cannot obtain source IP address of internet users from the log files of their web servers. The root cause has been identified and a fix will be applied in 1 week.
Resolution: Yes
Windows security identifier (SID)
Reported: 5/12/2008
Progress: 100%
Resolved: 7/19/2008
Severity: Moderate
Last update: 7/21/2008
Description: Changes users make to their Windows server do not remain intact in the registry. The root cause has been identified and is associated with the Windows Secure Identifier (SID). A fix is in place and is expected to be applied in 1 week.
Resolution: No
Managed Node Stability
Reported: 5/1/2008
Progress: 100%
Resolved: 6/17/2008
Severity: Critical
Last update: 6/17/2008
Description: Nodes crash causing all servers on the node to go down. The root cause is a hardware incompatibility issue with the node motherboard and RAID controller card. Maintenance will be scheduled for the week of 6/9 to resolve the issue. In the meantime, all nodes are being monitored and in the event of a crash, scripts will bring the node and all servers back online. Users can expect 5-10 minutes of downtime. We have not noticed any crash patterns and we are currently seeing on average 1 node crash every 2 days.
Resolution: Yes
Windows Private Networking
Reported: 5/15/2008
Progress: 100%
Resolved 6/4/2008
Severity: Minor
Last update: 6/6/2008
Description: Some users running Windows 2003 Server servers could not create a private network. The root cause was related to the Xen Hypervisor.
Resolution: The GoGrid Systems Team modified the Xen Hypervisor and the issue is resolved.
