Closed (fixed)
Project:
Provision
Version:
7.x-3.x-dev
Component:
Install process
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
10 Sep 2016 at 14:01 UTC
Updated:
3 Nov 2016 at 13:34 UTC
Jump to comment: Most recent
Comments
Comment #2
helmo commentedHmm, not sure why that would be needed. 'client_email' is passed as parameter to the provision-install command a few lines lower. Could we then remove that one?
Comment #3
memtkmcc commentedHmm.. but it just never worked for us without that patch after moving to 3.x.
Comment #4
memtkmcc commentedWithout this patch Aegir always forced
this.email@is.invalidfor us.Comment #5
memtkmcc commentedAlso, I don't understand why it is passed to provision-install separately, and not written in the provision-save step above.
Comment #6
memtkmcc commentedSo yeah, it seems redundant, but also weird how it got
this.email@is.invalidfor us without that option added to the array for provision-save.Comment #7
colanJust to confirm the problem, I ran into this when installing Aegir manually before I started using the Debian package:
drush hostmaster-install --client_name=$SUDO_USER --client_email=$SUDO_USER@example.com --http_service_type=nginx --working-copyThe --client_email never had any effect.
Comment #8
memtkmcc commentedYeah, I have some logs from our tests archived, and it looked like this:
Comment #9
helmo commentedAdded to https://github.com/aegir-project/provision/pull/6 to help test .. (PS: Travis is not fully functional yet.)
Comment #11
helmo commentedmerged