New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
initrock via rockstor-pre fails on non-existent /etc/issue #2335
Comments
And the associated systemd service:
|
Our more recent treatment of /etc/issues: We also have an older mechanism resourcing osi.py: |
It is proposed that we postpone any major changes to our existing outdated treatment of /etc/issue and for the time being fix our simple failure to back-up a file that does not exist, for whatever reason. Later, maybe in our next testing channel run-up to our subsequent stable release, post 4.1.0-0, we can move over to using the issue-generator systemd service and simply drop our desired content into new within proposed content directories managed by this service. But for now we have basic failure to address to ensure we are more robust to whatever has caused this anomalous missing /etc/issue file situation. |
From the following it looks like we have some dead code here also:
So system/osi.py: update_issue() is no longer used. And we appear to no longer use issue.rockstor as we once did in src/rockstor/storageadmin/views/network.py
Which in this case is our initial failure point. I.e. we attempt to copy /etc/issue to /etc/issue.rockstor as we used to then copy this back over to /etc/issue in src/rockstor/storageadmin/views/network.py but no longer do this. |
I am working on a pull request for this issue. |
We previously assumed the existence of /etc/issue, avoid rockstor service failures in this case by creating during the open process if required. Includes: - Remove the now defunct /etc/issue.rockstor copy from /etc/issue. - Remove dead code previously used to update /etc/issue - osi.py: update_issue()
…e_fails_on_no_/etc/issue initrock via rockstor-pre fails on non-existent /etc/issue #2335
Under some circumstances a system can end up with no /etc/issue. Initrock, run by rockstor-pre.service can then fail trivially via:
Which in-turn fails rockstor.service & consequently rockstor-bootstrap.service vai a dependency chain.
The default upstream contents of /etc/issue is, in our new upstream of openSUSE, determined initially by:
The text was updated successfully, but these errors were encountered: