Bug 1277520

Summary: Deploy from appliance failed because missed answer
Product: [oVirt] ovirt-hosted-engine-setup Reporter: Artyom <alukiano>
Component: GeneralAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED DUPLICATE QA Contact: Ilanit Stein <istein>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 1.3.1CC: bugs, didi, lveyde, rmartins, sbonazzo, stirabos
Target Milestone: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-04 15:19:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
setup log none

Description Artyom 2015-11-03 13:54:35 UTC
Created attachment 1088993 [details]
setup log

Description of problem:
Deploy from appliance failed because missed answer on:
Would you like transactions from the Red Hat Access Plugin sent from the RHEV Manager to be brokered through a proxy server? (Yes, No) [No]: [ ERROR ] Failed to execute stage 'Environment customization': End of file

Version-Release number of selected component (if applicable):
rhevm-appliance-20151029.2-1.el6ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. run hosted-engine --deploy on host
2. choose deployment from appliance
3. answer yes on question: Automatically execute engine-setup on the engine appliance on first boot
4. continue deployment

Actual results:
Deployment failed with error:
Would you like transactions from the Red Hat Access Plugin sent from the RHEV Manager to be brokered through a proxy server? (Yes, No) [No]: [ ERROR ] Failed to execute stage 'Environment customization': End of file


Expected results:
deployment succeed without any errors

Additional info:

Comment 1 Artyom 2015-11-04 15:19:05 UTC

*** This bug has been marked as a duplicate of bug 1277521 ***