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

allow consistently reexecute after failure #119

merged 1 commit into from Jan 23, 2019


Copy link

commented Jan 17, 2019

Save generated passwords to temp file until installation finishes.

What it fixes: on some slower HW or in virtualization, sometimes the vmadm create command times out and installation crashes. It can be re-started by
svcadm clear init
But it generates passwords and certificates again and it creates inconsistency with already-deployed service VMs. Consequently the services refuse to play together.


@YanChii YanChii self-assigned this Jan 17, 2019

@YanChii YanChii requested a review from dn0 Jan 17, 2019

# certificate for DC internal services

This comment has been minimized.

Copy link

dn0 Jan 22, 2019


Can't we store it /tmp if it is a temp file?
(i.e. do we want to support resume of installation after a reboot?)

This comment has been minimized.

Copy link

YanChii Jan 22, 2019

Author Contributor

We definitely want to support the resume. It happes relatively often that vmadm chokes for some reason on slow servers and I really don't want to re-start the whole installation because of this.

/tmp destination is possible but with permanent storage, you can tell the customer just to reboot the box to resume the installation. Otherwise you need to give specific instructions how to clear the service.

This comment has been minimized.

Copy link

dn0 Jan 23, 2019



dn0 approved these changes Jan 23, 2019

@YanChii YanChii merged commit c061a7b into erigones:master Jan 23, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
You can’t perform that action at this time.