Hide Forgot
Created attachment 1507057 [details] Screenshot showing the broken UI Description of problem: After installing cockpit-composer, accessing Cockpit to go to the new image builder application leads to a UI that lets you do absolutely nothing. Version-Release number of selected component (if applicable): 0.1.5-1.el8 How reproducible: Always Steps to Reproduce: 1. Install lorax-composer 2. Restart cockpit (if needed) 3. Connect to cockpit and attempt to use the image builder UI Actual results: The UI lets me do nothing... Expected results: The UI lets me do stuff to create images... Additional info:
Sounds like the lorax-composer backend failed to start?
(In reply to Neal Gompa from comment #0) > Created attachment 1507057 [details] > Screenshot showing the broken UI > > Description of problem: > After installing cockpit-composer, accessing Cockpit to go to the new image > builder application leads to a UI that lets you do absolutely nothing. > > Version-Release number of selected component (if applicable): > 0.1.5-1.el8 > > How reproducible: > Always > > Steps to Reproduce: > 1. Install lorax-composer > 2. Restart cockpit (if needed) > 3. Connect to cockpit and attempt to use the image builder UI > > Actual results: > The UI lets me do nothing... > > Expected results: > The UI lets me do stuff to create images... > > Additional info: Did you run 'systemctl enable lorax-composer.socket && systemctl start lorax-composer.socket' ? http://weldr.io/lorax/f28-branch/lorax-composer.html#quickstart You can check to see if things are working correctly from the cmdline using 'composer cli status show'
$ composer-cli status show 2018-11-26 15:31:07,522: /run/weldr/api.socket does not exist $ sudo composer-cli status show 2018-11-26 15:31:26,956: UnixHTTPConnectionPool(host='localhost', port=None): Max retries exceeded with url: /api/status (Caused by ProtocolError('Connection aborted.', ConnectionRefusedError(111, 'Connection refused')))
I had done the following prior to running that: $ sudo systemctl enable --now lorax-composer.socket Created symlink /etc/systemd/system/sockets.target.wants/lorax-composer.socket → /usr/lib/systemd/system/lorax-composer.socket.
Next thing to do is to look at the output from journalctl and see why the service isn't being started. Do you have SELinux in Permissive mode?
It took a reboot after doing so, but now it worked! I wonder if it was just "stuck" after it failed initially...?
(In reply to Neal Gompa from comment #6) > It took a reboot after doing so, but now it worked! > > I wonder if it was just "stuck" after it failed initially...? I think if the .socket doesn't successfully start the .service it gets stopped so that may be what happened. A start should start it up again w/o needing a reboot. But I'm not sure what failed in the first place that made it necessary to do that. You can also look at the logs in /var/log/lorax-composer/composer.log and see if there's anything obvious (SELinux complaint or traceback of some kind).
(In reply to Brian Lane from comment #7) > (In reply to Neal Gompa from comment #6) > > It took a reboot after doing so, but now it worked! > > > > I wonder if it was just "stuck" after it failed initially...? > > I think if the .socket doesn't successfully start the .service it gets > stopped so that may be what happened. A start should start it up again w/o > needing a reboot. But I'm not sure what failed in the first place that made > it necessary to do that. > > You can also look at the logs in /var/log/lorax-composer/composer.log and > see if there's anything obvious (SELinux complaint or traceback of some > kind). Sorry, I meant to reply to this. Yeah, that's basically what happened. Aside from the (already known) SELinux denials, it's otherwise fine. Thanks for the help!