[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647236#comment-14647236
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-126196695
  
Awesome, thanks!

Cheers,
Wilder

Sent from my iPhone

On 30 Jul 2015, at 07:22, kishankavala 
mailto:notificati...@github.com>> wrote:


Hi @wilderrodrigues,
@sanjeevneelarapu filed ticket for 
"default policy ACCEPT" issue. 
https://issues.apache.org/jira/browse/CLOUDSTACK-8688

—
Reply to this email directly or view it on 
GitHub.



> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.6.0
>
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647206#comment-14647206
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user kishankavala commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-126186427
  
Hi @wilderrodrigues, 
@sanjeevneelarapu  filed ticket for "default policy ACCEPT" issue. 
https://issues.apache.org/jira/browse/CLOUDSTACK-8688


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.6.0
>
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645853#comment-14645853
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-125915603
  
Awesome! Thanks a lot, @karuturi and @kishankavala 

Cheers,
Wilder


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.6.0
>
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645850#comment-14645850
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user kishankavala commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-125915281
  
Thanks @wilderrodrigues 
I merged https://github.com/apache/cloudstack/pull/634/
I'll created separate ticket to track  "default policy ACCEPT" issue.


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.6.0
>
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645780#comment-14645780
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-125894943
  
Hi @kishankavala 

Let's try to focus on 1 change at a time:

1. the port 3922 is blocked
2. default policy ACCEPT

So, the changes on the "cloud-early-config" won't cause any harm to the 
VPC/Isolated VRs, right?

Once we have the port fixed we move on to the next.

Cheers,
Wilder


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.6.0
>
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645771#comment-14645771
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user kishankavala commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-125890106
  
@wilderrodrigues iptables issue is not specific to dhcpsrvr (shared VR). On 
isolated VR also default policy is ACCEPT
```
root@r-23-VM:~# iptables -L -nv
Chain INPUT (policy ACCEPT 9620 packets, 1598K bytes)




> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.6.0
>
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645759#comment-14645759
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-125889027
  
Hi @kishankavala,

If it doesn't match the content of rules.v4 perhaps the iptables-save is 
not being called when dhcpsrvr.

By adding the change you suggested the code on the CsAddress.py line 367 
will be executed:

if self.get_type() in ["control"]:
self.fw.append(["filter", "", "-A FW_OUTBOUND -m state --state 
RELATED,ESTABLISHED -j ACCEPT"])
self.fw.append(["filter", "", "-A INPUT -i %s -p tcp -m tcp 
--dport 3922 -m state --state NEW -j ACCEPT" % self.dev])

I can add the changes here and run tests before you create the PR, if 
that's okay with you.

Cheers,
Wilder


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.6.0
>
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645707#comment-14645707
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user kishankavala commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-125882216
  
Sure @wilderrodrigues 
I'll create a PR. 

But iptables rules are more open now (default ACCEPT).
root@r-30-VM:~# iptables -L INPUT -nv
Chain INPUT (policy ACCEPT 104 packets, 14936 bytes)

It doesn't match content in /etc/iptables/rules.v4 


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.6.0
>
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645688#comment-14645688
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-125878438
  
Nice catch, @kishankavala !

I checked the history of the file and found out that the changes for VPC 
router and normal router were added in the commit 
13b7ca1b3fc3d3c44d677307a59a5205b6c881bb

The extra iff you added, for the dhcpsrvr case, will do it.

Do you want to create a new PR for that one? I can test it as well. Since 
it's touching only dhcpsrvr (used for basic zones) I'm not expecting problemas 
with VPC routers or other routers used for advanced zones.

Cheers,
Wilder 


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.6.0
>
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645582#comment-14645582
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user kishankavala commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-125864299
  
@wilderrodrigues
Below changes fixed the issue but not sure if it breaks anything else:

kk-cloudstack > git diff
diff --git a/systemvm/patches/debian/config/etc/init.d/cloud-early-config 
b/systemvm/patches/debian/config/etc/init.d/cloud-early-config
index 711d575..934ba9c 100755
--- a/systemvm/patches/debian/config/etc/init.d/cloud-early-config
+++ b/systemvm/patches/debian/config/etc/init.d/cloud-early-config
@@ -1339,6 +1339,10 @@ start() {
  dhcpsrvr)
  [ "$NAME" == "" ] && NAME=dhcpsrvr
  setup_dhcpsrvr
+ if [ -x /opt/cloud/bin/update_config.py ]
+ then
+/opt/cloud/bin/update_config.py cmd_line.json
+ fi
  ;;
  secstorage)
  [ "$NAME" == "" ] && NAME=secstorage


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.6.0
>
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645486#comment-14645486
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-125850427
  
Hi @kishankavala 

I'm on it.

Cheers,
Wilder


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.6.0
>
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645467#comment-14645467
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user kishankavala commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-125846995
  
Hi @wilderrodrigues 
Please look into CLOUDSTACK-8683 when possible


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.6.0
>
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644486#comment-14644486
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-125639101
  
Hi @kishankavala 

Are you looking at the other problem or can I have a look into it?

I was able to reproduce here... just let me know if you need help.

Cheers,
Wilder


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.6.0
>
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[Wilder Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644413#comment-14644413
 ] 

Wilder Rodrigues commented on CLOUDSTACK-8668:
--

I will mark this issue as resolved, since the port problem has been created 
under another issue id.

> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.6.0
>
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644291#comment-14644291
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user kishankavala commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-125580306
  
Yes @wilderrodrigues "VR started successfully ". But port 3922 is not open. 
Once I add iptables rule to allow 3922, MS is able to program rules.
I'm looking at CLOUDSTACK-8683, but might take a while for me to find the 
root cause.


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Wilder Rodrigues
>Priority: Blocker
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[Kishan Kavala (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644290#comment-14644290
 ] 

Kishan Kavala commented on CLOUDSTACK-8668:
---

Yes Wilder "VR started successfully ". But port 3922 is not open. Once I add 
iptables rule to allow 3922, MS is able to program rules.
I'm looking at CLOUDSTACK-8683, but might take a while for me to find the root 
cause.

> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Wilder Rodrigues
>Priority: Blocker
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644273#comment-14644273
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-125572581
  
Hi @kishankavala 

But you said you tested "VR successfully started on shared network. All IPs 
are configured properly."... Based on that, I assumed it was working. I'm now 
building lated master in order to test it as well.

Will you look at the other problem?

Cheers,
Wilder


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Wilder Rodrigues
>Priority: Blocker
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644270#comment-14644270
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user kishankavala commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-125571871
  
Thanks @wilderrodrigues for merging.
Ran into another blocker after VR came up: 
https://issues.apache.org/jira/browse/CLOUDSTACK-8683


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Wilder Rodrigues
>Priority: Blocker
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644264#comment-14644264
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/627


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Wilder Rodrigues
>Priority: Blocker
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644254#comment-14644254
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-125566567
  
Thanks for the PR, @kishankavala !

It LGTM :+1:  and I will also test it

Cheers,
Wilder


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Wilder Rodrigues
>Priority: Blocker
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644251#comment-14644251
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


Github user jayapalu commented on the pull request:

https://github.com/apache/cloudstack/pull/627#issuecomment-125565419
  
LGTM


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Wilder Rodrigues
>Priority: Blocker
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644165#comment-14644165
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:


GitHub user kishankavala opened a pull request:

https://github.com/apache/cloudstack/pull/627

CLOUDSTACK-8668: VR type in shared network is dhcpsrvr. Ips are being 
removed due to this issue

- VR IP config is loaded from /var/cache/cloud/cmdline
- For shared network VR type is "dhcpserver" in /var/cache/cloud/cmdline
- after VR refactor, merge.py is considering VR types "router" and 
"vpcrouter" only
-  Fixed by adding dhcpserver VR type

Testing:
- VR successfully started on shared network. All IPs are configured 
properly.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/kishankavala/cloudstack CLOUDSTACK-8668

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/627.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #627


commit 50a6fa02dabd7df7a78a0541df6e575129e14265
Author: Kishan Kavala 
Date:   2015-07-28T09:45:41Z

VR type in shared network is dhcpsrvr. Ips are being removed due to this 
issue




> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Wilder Rodrigues
>Priority: Blocker
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[Kishan Kavala (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644133#comment-14644133
 ] 

Kishan Kavala commented on CLOUDSTACK-8668:
---

Issue is due to router type in cmdline. For VR in shared network type is 
"dhcpsrvr" and not "router". I'll create a PR for this fix

> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Wilder Rodrigues
>Priority: Blocker
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[Wilder Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643096#comment-14643096
 ] 

Wilder Rodrigues commented on CLOUDSTACK-8668:
--

Few things I got from the logs when creating a VM:

2015-07-27 13:28:20,921 DEBUG [c.c.h.x.r.w.x.CitrixStartCommandWrapper] 
(DirectAgent-28:ctx-b81b9e66) 1. The VM r-4-VM is in Starting state.
2015-07-27 13:28:20,950 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-28:ctx-b81b9e66) Created VM d42abe6d-d225-c738-d905-a303883cb093 
for r-4-VM
2015-07-27 13:28:20,958 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-28:ctx-b81b9e66) PV args are -- quiet 
console=hvc0%template=domP%name=r-4-VM%eth0ip=192.168.22.66%eth0mask=255.255.255.0%gateway=192.168.22.1%domain=cs1cloud%cidrsize=24%dhcprange=192.168.22.1%eth1i
p=169.254.2.146%eth1mask=255.255.0.0%type=dhcpsrvr%disable_rp_filter=true%dns1=8.8.8.8%dns2=8.8.4.4%baremetalnotificationsecuritykey=aon4dbRYnNESI4PY3PDh64PgJKAx6H11OfLVwZAWE-4uJWV-iJrg7fcgdTHDVVjOP81TS0UBxKMmY53r0y88bw%baremetalnotificationapikey=CAC7caUw4uF9wfLNrSObdj-h
VkVSo9MQzEMIjN4rIfSjOAu8TJxVnHaFEU8W5utTWuuDJqHiqtXgTJT7T-Cm4w%host=192.168.22.61%port=8080
2015-07-27 13:28:21,006 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-28:ctx-b81b9e66) VBD 6c7a704f-6043-d09e-ecbb-27e8b6378597 created 
for com.cloud.agent.api.to.DiskTO@ad357be
2015-07-27 13:28:21,024 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-28:ctx-b81b9e66) Creating VIF for r-4-VM on nic 
[Nic:Guest-192.168.22.66-vlan://untagged]
2015-07-27 13:28:21,048 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-28:ctx-b81b9e66) Created a vif 
8db43efe-bac2-8b6e-d20f-b2f25445e6c1 on 0
2015-07-27 13:28:21,048 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-28:ctx-b81b9e66) Creating VIF for r-4-VM on nic 
[Nic:Control-169.254.2.146-null]
2015-07-27 13:28:21,099 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-28:ctx-b81b9e66) already have a vif on dom0 for link local network
2015-07-27 13:28:21,284 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-28:ctx-b81b9e66) Created a vif 
dbe914ad-eed8-c79c-0162-4cb7118ab701 on 1


2015-07-27 13:31:55,197 DEBUG [c.c.c.ClusterManagerImpl] 
(Cluster-Heartbeat-1:ctx-4fe9ccf7) Management server heartbeat takes too long 
to finish. profiler: Done. Duration: 5ms, profilerHeartbeatUpdate: Done. 
Duration: 4ms, profilerPeerScan: Done. Duration: 1ms
2015-07-27 13:31:55,580 ERROR [c.c.u.s.SshHelper] (DirectAgent-28:ctx-b81b9e66) 
Timed out in waiting SSH execution result
2015-07-27 13:31:55,581 DEBUG [c.c.a.m.DirectAgentAttache] 
(DirectAgent-28:ctx-b81b9e66) Seq 1-7644297417507995698: Response Received: 
2015-07-27 13:31:55,583 DEBUG [c.c.a.t.Request] (DirectAgent-28:ctx-b81b9e66) 
Seq 1-7644297417507995698: Processing:  { Ans: , MgmtId: 3232241213, via: 1, 
Ver: v1, Flags: 10, 
[{"com.cloud.agent.api.StartAnswer":{"vm":{"id":4,"name":"r-4-VM","bootloader":"PyGrub","type":"DomainRouter","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":268435456,"maxRam":268435456,"arch":"x86_64","os":"Debian
 GNU/Linux 7(64-bit)","platformEmulator":"Debian Wheezy 7.0 
(64-bit)","bootArgs":" template=domP name=r-4-VM eth0ip=192.168.22.66 
eth0mask=255.255.255.0 gateway=192.168.22.1 domain=cs1cloud cidrsize=24 
dhcprange=192.168.22.1 eth1ip=169.254.2.146 eth1mask=255.255.0.0 type=dhcpsrvr 
disable_rp_filter=true dns1=8.8.8.8 dns2=8.8.4.4 
baremetalnotificationsecuritykey=aon4dbRYnNESI4PY3PDh64PgJKAx6H11OfLVwZAWE-4uJWV-iJrg7fcgdTHDVVjOP81TS0UBxKMmY53r0y88bw
 
baremetalnotificationapikey=CAC7caUw4uF9wfLNrSObdj-hVkVSo9MQzEMIjN4rIfSjOAu8TJxVnHaFEU8W5utTWuuDJqHiqtXgTJT7T-Cm4w
 host=192.168.22.61 
port=8080","enableHA":true,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"oc7KQtWwxoUHoIoNiRPhCA","params":{},"uuid":"309d19d3-cd56-44e2-8119-61afbb914f69","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"b4ce8d0e-e65d-46f2-987b-f297256904f7","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"7016d9c7-3dcd-3128-add6-5910036ef0b4","id":1,"poolType":"NetworkFilesystem","host":"192.168.22.1","path":"/data/storage/primary/MCCT-XEN-1","port":2049,"url":"NetworkFilesystem://192.168.22.1/data/storage/primary/MCCT-XEN-1/?ROLE=Primary&STOREUUID=7016d9c7-3dcd-3128-add6-5910036ef0b4"}},"name":"ROOT-4","size":3145728000,"path":"ccc53598-e9c9-4a22-a711-df836e63152e","volumeId":4,"vmName":"r-4-VM","accountId":1,"format":"VHD","provisioningType":"THIN","id":4,"deviceId":0,"hypervisorType":"XenServer"}},"diskSeq":0,"path":"ccc53598-e9c9-4a22-a711-df836e63152e","type":"ROOT","_details":{"managed":"false","storagePort":"2049","storageHost":"192.168.22.1","volumeSize":"3145728000"}}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"pxeDisable":true,"nicUuid":"83e48526-4ca9-4dfd-9d76-2a9c343f8139","uuid":"b35aec92-a197-4f6a-8a22-693dc1d294e2","ip":"192.168.22.66","netmask

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[Wilder Rodrigues (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643075#comment-14643075
 ] 

Wilder Rodrigues commented on CLOUDSTACK-8668:
--

I'm testing it with 2 xenserver (cluster), shared storage and basic zone

> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Assignee: Wilder Rodrigues
>Priority: Blocker
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[Kishan Kavala (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14640389#comment-14640389
 ] 

Kishan Kavala commented on CLOUDSTACK-8668:
---

VR Config file:
#Apache CloudStack Virtual Router Config File 
1.0


/var/cache/cloud/monitor_service.json
{"config":"[dhcp]:processname=dnsmasq:servicename=dnsmasq:pidfile=/var/run/dnsmasq/dnsmasq.pid:,[ssh]:processname=sshd:servicename=ssh:pidfile=/var/run/sshd.pid:,[webserver]:processname=apache2:servicename=apache2:pidfile=/var/run/apache2.pid:,","type":"monitorservice"}


/opt/cloud/bin/update_config.py monitor_service.json 

/var/log/cloud.log:
2015-07-24 09:29:28,997 Loading data bag type monitorservice
2015-07-24 09:29:28,998 Command of type monitorservice received
2015-07-24 09:29:28,999 Writing data bag type monitorservice
2015-07-24 09:29:28,999 Creating data bag type ips
2015-07-24 09:29:28,999 Loading data bag type cmdline
2015-07-24 09:29:29,000 Executing ip addr show dev eth1
2015-07-24 09:29:29,019 Will remove all configured addresses on device eth1
2015-07-24 09:29:29,019 Removing addresses from device eth1
2015-07-24 09:29:29,036 Removed address 169.254.2.130/16 from device eth1
2015-07-24 09:29:29,056 Removed address 169.254.2.130/16 from device eth1
2015-07-24 09:29:29,057 Executing ip addr show dev eth0
2015-07-24 09:29:29,075 Will remove all configured addresses on device eth0
2015-07-24 09:29:29,076 Removing addresses from device eth0
2015-07-24 09:29:29,093 Removed address 10.220.39.131/19 from device eth0
2015-07-24 09:29:29,112 Removed address 10.220.39.131/19 from device eth


> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Priority: Blocker
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8668) VR does not start in basic zone since ip address are not being configured on it

[Jayapal Reddy (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14640192#comment-14640192
 ] 

Jayapal Reddy commented on CLOUDSTACK-8668:
---

[~wilder.rodrigues]
On VR start ping from MS is success.
On running VR aggregate command,  in the VR interfaces ips are lost. 

If we run manually  '/opt/cloud/bin/update_config.py monitor_service.json'  it 
is removing interface ips.



> VR does not start in basic zone since ip address are not being configured on 
> it
> ---
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.6.0
> Environment: Latest build from ACS master
>Reporter: Sanjeev N
>Priority: Blocker
>
> VR does not start in basic zone since ip address are not being configured on 
> it
> Steps to reproduce:
> 
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==
> VR should come up as part of vm deployment and vm deployment should be 
> successfull
> Actual Result:
> 
> VR creation failed since the IP addresses not are getting assigned to VR's 
> guest and link local interfaces.
> Observations:
> ===
> 1.During vr boot time, cloud-early-config ran successfully and VR console 
> output showed that ping to gateway was successful. However, after VR boot we 
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be 
> assigned and persistent.
> Impact:
> =
> VM deployments will fail since VR remains in stopped state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)