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
Add kickstart test to test hostname #112
Conversation
I think we need to care most about the output of |
But now I realized that it wouldn't work as one would expect, I guess. It's probably again a fancy DBus thing that does nothing useful in combination with |
Good point with the |
I added |
That however tests a different thing. It's only my theory (based on quite a lot of disappointing experience with these "systemd-ish" services), but I think |
So the |
Yes, we could test that here as well. And at some point we may also add kickstart tests that test other phases of the installation process -- e.g. the hostname should be set in the installation environment way early than in the |
Ok it's settled I change the tests to I want to ask one more question it's related to my other PR too (#117 and #115). I'm using network-* prefix now but from I found in PR #118 you didn't want the prefix. So I change this to without prefix variants. So this test will be named as hostname.[ks|sh]. Other tests will be renamed in the same manner. Do you agree @vpodzime, @clumens ? |
Yeah, stripping out the network- prefix seems like a good idea here too. |
Thank you much. |
Test is easy: