Actions
Issue #9528
closedError during pulp_installer if ran as user-data
Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Master
Platform Release:
OS:
CentOS 7
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Running pulp_installer as user-data at the end of an EC2 fresh install fails during one of the last steps with:
TASK [pulp.pulp_installer.pulp_webserver : Accept HTTP connections on port 80] ***
ERROR:dbus.proxies:Introspect error on :1.57:/org/fedoraproject/FirewallD1: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
fatal: [127.0.0.1]: FAILED! => {"msg": "Unexpected failure during module execution.", "stdout": ""}
It seems a problem with firewalld hanging up if instance is freshly installed and still not rebooted: [[https://forums.centos.org/viewtopic.php?f=47&t=52162&p=220915#p220915]] but I cannot be sure.
I can provide my user-data (shell script), if it can be useful.
Updated by micuz over 2 years ago
As far as I'm reading, using "firewall-offline-cmd" could be solve the issue.
Updated by micuz over 2 years ago
After a first reboot, obviously, pulp_installer works fine but this makes impossible automatically installing Pulp at the end of an EC2 deployment as user-data.
Updated by fao89 over 2 years ago
- Category set to Installer - Moved to GitHub issues
- Status changed from NEW to CLOSED - DUPLICATE
Actions