[ICN-260] KUD Multi Vagrant 18.04 issue Created: 11/Feb/20  Updated: 17/Dec/20  Resolved: 21/Apr/20

Status: Done
Project: Integrated Cloud Native NFV
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Kuralamudhan Ramakrishnan Assignee: Le Yao
Resolution: Done Votes: 0
Labels: icn-kud-r3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File FW About ICN-217.msg     File Sync up on Multi-cluster vagrant bug in KUD.ics    
Issue Links:
Blocks
is blocked by ICN-281 Vagrant vm can not get correct name s... Done
is blocked by ICN-285 Installer vm cannot install nfs becau... Done
is blocked by ICN-286 All other VMs are unreachable for Ins... Done
is blocked by ICN-303 Compute01 no spcae left in KUD Multi ... Done
Epic Link: Kud v2.0 for ICN
Sprint: ICN Sprint 11, ICN Sprint 12, ICN Sprint 13, ICN Sprint 16

 Description   

Pre-requisition: Ramp on KUD

Resources: Baremetal server

Components Version: Ubuntu 18.04, KUD

Task Description: 

  1. Revert back the commit - https://github.com/onap/multicloud-k8s/commit/f3c09ea952108a5bf9b0bc143ffeee2a1bf73fd3
  2. Run the KUD with Multi Vagrant option
  3. Hit the problem with Vagrant VMs are not created

Testing:  Run Multi Vagrant and KUD run

Expected Deliverables: Add the patch in the KUD repo - https://github.com/onap/multicloud-k8s/tree/master/kud/hosting_providers/vagrant

 Comments   
Comment by Kuralamudhan Ramakrishnan [ 03/Apr/20 ]

Bug is not yet fixed

Comment by Le Yao [ 24/Mar/20 ]

The patch in ONAP/multicloud-k8s has been merged. And I have tested the newest version, all are successful.
https://gerrit.onap.org/r/c/multicloud/k8s/+/102561

Comment by Le Yao [ 26/Feb/20 ]

When solving this problem, executing the command "vagrant up" will meet the above errors, and it is caused by the nameserver issue. The related jira is:
ICN-281:https://jira.akraino.org/browse/ICN-281

Comment by Le Yao [ 18/Feb/20 ]

With all vms running well and network is working, it would report the following errors when command 'vagrang up'.

An error occurred while executing multiple actions in parallel.
Any errors that occurred are shown below.

An error occurred while executing the action on the 'controller01'
machine. Please handle this error then try again:

The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

An error occurred while executing the action on the 'controller02'
machine. Please handle this error then try again:

The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

An error occurred while executing the action on the 'controller03'
machine. Please handle this error then try again:

The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

An error occurred while executing the action on the 'compute01'
machine. Please handle this error then try again:

The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

An error occurred while executing the action on the 'compute02'
machine. Please handle this error then try again:

The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Generated at Sat Feb 10 05:58:29 UTC 2024 using Jira 9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1.