Bug 791217

Summary:	IPv6: MonitoringScout on Proxy cannot download NOCpulse.ini from Spacewalk
Product:	[Community] Spacewalk	Reporter:	Lukas Pramuk <lpramuk>
Component:	Proxy Server	Assignee:	Stephen Herr <sherr>
Status:	CLOSED WONTFIX	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.6	CC:	ggainey, jpazdziora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-30 16:02:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	790326, 1484117

Description Lukas Pramuk 2012-02-16 14:30:17 UTC

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

Comment 1 Jan Pazdziora 2012-04-10 14:20:36 UTC

I believe just adding

  use Net::INET6Glue::INET_is_INET6;

could make the monitoring code IPv6 aware.

Comment 2 Lukas Pramuk 2013-03-26 09:50:31 UTC

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 :-)

Comment 4 Lukas Pramuk 2013-03-26 10:04:41 UTC

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')

Comment 5 Grant Gainey 2015-03-30 16:02:17 UTC

As of the Spacewalk 2.3 release, Spacewalk no longer supports monitoring.  Closing.

Comment 6 Eric Herget 2017-09-28 17:55:58 UTC

This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.