Hide Forgot
Description of problem: During Proxy configuration,the MonitoringScout is not able to download initial config file NOCpulse.ini from IPv6 Spacewalk (ip6 hostname or ip) Version-Release number of selected component (if applicable): SatConfig-general 1.216.25-1.el6 nocpulse-common 2.2.1-1.el6 perl-libwww-perl 5.833-2.el6 perl 5.10.1-119.el6_1.1 How reproducible: 100% Steps to Reproduce: 1. register to IPv6 parent SW 2. run configure-proxy.sh 3. be sure to enable Monitoring Scout, during MonitoringScout service start error message is printed Actual results: NOCpulse.ini is not downloaded, following error message is printed: Starting MonitoringScout ... 2012-02-16 08:59:13 InstallSoftwareConfig: !! Couldn't download NOCpulse.ini: 500 Can't connect to ipv6-machine.domain:443 (Bad hostname 'ipv6-machine.domain') Expected results: NOCpulse.ini is downloaded, no error messages, just [ OK ] Additional info: NOCpulse::NOCpulseini->download_nocpulseini is using perl-libwww-perl LWP::UserAgent->get, which seems not being aware of IPv6
I believe just adding use Net::INET6Glue::INET_is_INET6; could make the monitoring code IPv6 aware.
I tried to add "use Net::INET6Glue::INET_is_INET6;" into /usr/share/perl5/vendor_perl/NOCpulse/NOCpulseini.pm and yes 500 was gone, but 403 popped instead. 2013-03-25 21:57:14 InstallSoftwareConfig: !! Couldn't download NOCpulse.ini: 403 Forbidden Not sure if it helped or not. (Dimi would say: Im'suspicious about that :-)
INET6Glue for IPv4 behaves same way as for IPv6: 403 Forbidden. So it seems it just breaks IPv4 connection and doesn't help to establish IPv6 connection... I tested these cases: [1] IPv4 Starting MonitoringScout ... Starting InstallSoftwareConfig ... [ OK ] [2] IPv4, INET6Glue Starting MonitoringScout ... 2013-03-25 22:35:19 InstallSoftwareConfig: !! Couldn't download NOCpulse.ini: 403 Forbidden [3] IPv6, INET6Glue Starting MonitoringScout ... 2013-03-25 22:40:35 InstallSoftwareConfig: !! Couldn't download NOCpulse.ini: 403 Forbidden [4] IPv6 (reported issue) Starting MonitoringScout ... 2013-03-25 22:43:43 InstallSoftwareConfig: !! Couldn't download NOCpulse.ini: 500 Can't connect to ipv6-machine.domain:443 (Bad hostname 'ipv6-machine.domain')
As of the Spacewalk 2.3 release, Spacewalk no longer supports monitoring. Closing.
This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug.