| Summary: | nova-novncproxy does not work after systemd-journald restarts | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | VIKRANT <vaggarwa> |
| Component: | openstack-nova | Assignee: | Eoghan Glynn <eglynn> |
| Status: | CLOSED NOTABUG | QA Contact: | Prasanth Anbalagan <panbalag> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9.0 (Mitaka) | CC: | berrange, dasmith, eglynn, kchamart, nchandek, sbauza, sferdjao, sgordon, srevivo, vaggarwa, vromanso |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-24 13:35:29 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: | |
|
Description
VIKRANT
2016-11-03 11:58:54 UTC
Workaround : One way to fix is to modify shared by Cu : /lib/systemd/system/openstack-nova-novncproxy.service so that it does not use the default redirecting to systemd-journald by adding these 2 lines to it StandardOutput=null StandardError=null For example this way [root@controller-1 ~]# cat /lib/systemd/system/openstack-nova-novncproxy.service [Unit] Description=OpenStack Nova NoVNC Proxy Server After=syslog.target network.target [Service] Type=simple User=nova EnvironmentFile=-/etc/sysconfig/openstack-nova-novncproxy StandardOutput=null StandardError=null ExecStart=/usr/bin/nova-novncproxy --web /usr/share/novnc/ $OPTIONS [Install] WantedBy=multi-user.target I'm pretty sure that restarting of the systemd-journald process is *not* supported by the systemd project. The journal holds the other end of the stdout/stderr FDs for processes connected to it, and when you restart journald those FDs get closed, breaking stdout/err for every process. (In reply to Daniel Berrange from comment #2) > I'm pretty sure that restarting of the systemd-journald process is *not* > supported by the systemd project. The journal holds the other end of the > stdout/stderr FDs for processes connected to it, and when you restart > journald those FDs get closed, breaking stdout/err for every process. According to the last comment from Daniel, can Cu explain why there are restarting 'systemd-journald' ? (In reply to Daniel Berrange from comment #2) > I'm pretty sure that restarting of the systemd-journald process is *not* > supported by the systemd project. The journal holds the other end of the > stdout/stderr FDs for processes connected to it, and when you restart > journald those FDs get closed, breaking stdout/err for every process. In NCIO16.5 there is one puppet module, which modifies journal configuration. To make that setting active, the systemd-journald must be restarted. I do not know if there is any other way. I think the idea here is to do that restart after all controller and compute nodes have been installed.. The change to journald configuration is to make journal logs storage persistent. Othewise the journald log information will be lost after rebooting the node. The fix creates /etc/systemd/journald.conf.d/persistent_storage.conf That has setting [Journal] Storage=persistent I heard that there should be a RedHat ticket for that problem (journald information will be lost after reboot). WONTFIX/NOTABUG therefore QE Won't automate |