Hide Forgot
Description of problem: I have Spacewalk 1.6 running on RHEL5 with IPv6 only address. When I enable Monitoring there, I see ISE. Version-Release number of selected component (if applicable): spacewalk-monitoring-1.4.1-1.el5 How reproducible: 1 of 1 attempt Steps to Reproduce: 1. have Spacewalk 1.6 running on RHEL5 with IPv6 only address (well, loopback have IPv4 adress) 2. Admin -> Spacewalk Configuration -> Enable Monitoring (tick it) -> Update Actual results: ISE Expected results: Monitoring should be correctly enabled. Additional info: Probably interesting line from /var/log/tomcat5/catalina.out is: 2012-02-15 07:54:02,237 [TP-Processor1] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/rhn].[action] - Servlet.service() for servlet action threw exception java.sql.SQLException: ORA-12899: value too large for column "SPACEWALK"."RHN_SAT_CLUSTER"."VIP" (actual: 48, maximum: 15)
Created attachment 562209 [details] /var/log/tomcat5/catalina.out
ISE happened because we tried to store an IPv6 address to a 15bytes long vip column. Extending schema to have IPv6 columns as well ... spacewalk.git: b89843f5d8a23a8dc494627d9c77d3836735b92b fc45905e8eaa29c808cd6179452830665383c1c4 5d96ec51b1dfde9dc01170187005eeda14ad2b7e e2c70e2d58c3eaa461bd8afedb6e714a4ec1cea9
+ one checkstyle fix ... spacewalk.git: b2ecf11e5497bbd032320193988f16ffd3023804
use loopback IPs in case the host has no DNS entry ... spacewalk.git: 2036c8e0e15de8d26cae406bddc32933862fb128
Spacewalk 1.7 has been released: https://fedorahosted.org/spacewalk/wiki/ReleaseNotes17