Skip to content
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

"reboot" feature for VMs #248

Open
fcami opened this issue Jan 29, 2019 · 3 comments
Open

"reboot" feature for VMs #248

fcami opened this issue Jan 29, 2019 · 3 comments
Labels
groomed Issues already discussed by the dev team type:feature

Comments

@fcami
Copy link
Contributor

fcami commented Jan 29, 2019

A "reboot" capability for any of the IPA nodes used in a test suite would be useful.
Example use cases:

  • test if client bits (like sssd or autofs) survive a reboot
  • test if a reboot affects replication

That reboot feature should be able to wait for ssh to be operational again and wait for a timeout as well.

@pvoborni
Copy link
Member

Just by reading the information available in this bug report, I'd say that it doesn't belong to this project because test should drive the act of rebooting and tests should not be aware of underlying CI.

I know that this ticket is driven by the fact that NFS mounts don't get reattached ( hashicorp/vagrant#1587 ) after reboot. Thus the ticket is valid. But from this perspective, I'd say that job of CI is to get the mounts reattached after a reboot. Waiting for having ssh operational is IMO not something the CI should do - this is a domain of testing framework.

@fcami
Copy link
Contributor Author

fcami commented Feb 1, 2019

Agreed, yes, though I'm not sure CI can detect a reboot.
An alternative implementation from the testing framework's perspective might be:

  • save mount information
  • reboot
  • on reboot, make sure everything is mounted again
    It is not clear yet how fragile this will be.

@f-trivino f-trivino added the groomed Issues already discussed by the dev team label May 24, 2019
@f-trivino
Copy link
Contributor

Please, @netoarmando could you investigate if this is applicable or not?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
groomed Issues already discussed by the dev team type:feature
Projects
None yet
Development

No branches or pull requests

3 participants