search

ManageIQ / manageiq-appliance

System files for the ManageIQ appliance.
Apache License 2.0
7 stars 50 forks source link

On initial appliance boot manageiq-initialize fails to configure kafka #351

Closed agrare closed 8 months ago

agrare commented 2 years ago 
Feb 14 10:25:32 ipi-dhcp-112.rtp.raleigh.ibm.com evm[7080]:  INFO -- evm: EVM:Settings Task: Setting key /prototype/messaging_type to kafka
Feb 14 10:25:32 ipi-dhcp-112.rtp.raleigh.ibm.com manageiq-initialize.sh[6977]: Failed to Configure the Message Server-
Feb 14 10:25:32 ipi-dhcp-112.rtp.raleigh.ibm.com systemctl[7086]: Removed /etc/systemd/system/multi-user.target.wants/manageiq-initialize.service.
Feb 14 10:25:33 ipi-dhcp-112.rtp.raleigh.ibm.com manageiq-initialize.sh[6946]: #<Thread:0x000055e2e253e150 /usr/share/ruby/open3.rb:287 run> terminated with exception (report_on_exception is true):
Feb 14 10:25:33 ipi-dhcp-112.rtp.raleigh.ibm.com manageiq-initialize.sh[6946]: /usr/share/ruby/open3.rb:287:in `read': stream closed in another thread (IOError)
Feb 14 10:25:33 ipi-dhcp-112.rtp.raleigh.ibm.com manageiq-initialize.sh[6946]:         from /usr/share/ruby/open3.rb:287:in `block (2 levels) in capture3'
Feb 14 10:25:33 ipi-dhcp-112.rtp.raleigh.ibm.com manageiq-initialize.sh[6946]: #<Thread:0x000055e2e253e038 /usr/share/ruby/open3.rb:288 run> terminated with exception (report_on_exception is true):
Feb 14 10:25:33 ipi-dhcp-112.rtp.raleigh.ibm.com manageiq-initialize.sh[6946]: /usr/share/ruby/open3.rb:288:in `read': stream closed in another thread (IOError)
Feb 14 10:25:33 ipi-dhcp-112.rtp.raleigh.ibm.com manageiq-initialize.sh[6946]:         from /usr/share/ruby/open3.rb:288:in `block (2 levels) in capture3'
Feb 14 10:25:33 ipi-dhcp-112.rtp.raleigh.ibm.com systemd[1]: manageiq-initialize.service: Succeeded.
Feb 14 10:25:33 ipi-dhcp-112.rtp.raleigh.ibm.com systemd[1]: Started Initialize Appliance Database.
Fryguy commented 2 years ago

Note that this should not be a problem in najdorf after #355

miq-bot commented 1 year ago

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

agrare commented 8 months ago

I no longer see this issue setting up an appliance