Bug 1170064
| Summary: | MonitoringScout -> NPBootstrap not starting after upgrade from 5.3.0 to 5.7.0: Status: '403 Forbidden' | ||
|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Jan Hutař <jhutar> |
| Component: | Upgrades | Assignee: | Tomáš Kašpárek <tkasparek> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 570 | CC: | jdobes, jhutar, tlestach |
| 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: | 2018-04-09 16:08:19 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1162131 | ||
|
Description
Jan Hutař
2014-12-03 07:41:15 UTC
Upstream work
spacewalk.git:
4c8a12a7789b0a7bef51e68dd0bb2ef18285df6f
1170064 - equality is too strict
Seems like this is linked to IPv6.
Disabling IPv6 in OS did not help (changed error message to
"(socket: Address family not supported by protocol)").
Disabling AAAA record made Perl library use IPv4 and it worked.
Example workaround:
add line for `$(hosntame)` to `/etc/hosts` (IPv4) and in
`/etc/nsswith.conf` change hosts to not use dns.
# hosts: files dns
hosts: files
(check with `host $(hostname)` that you gen only IPv4 record.
After that try restart, NPBootstrap should start.
Reported bug 1264580 when i have seen this again recently. We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog. We believe this bug has been fixed in the latest Satellite 5 version (5.8) (monitoring has been completely removed form the product), so closing the bug as CURRENTRELEASE. Please feel free to re-open in case you discover any issues. |