cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei Zhou (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-2319) 2.2.14 to 4.1.0 upgrade: unable to add egress rules
Date Fri, 03 May 2013 11:02:16 GMT


Wei Zhou commented on CLOUDSTACK-2319:


The API authorizeSecurityGroupEgress works well.
There are something wrong with the CloudStack UI. 
I will create a patch for it.
> 2.2.14 to 4.1.0 upgrade: unable to add egress rules
> ---------------------------------------------------
>                 Key: CLOUDSTACK-2319
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: 4.1.0
>            Reporter: Shashi Dahal
>            Priority: Blocker
>              Labels: egress, kvm, security-groups, upgrade
>             Fix For: 4.1.0
> Hi, 
> For VMS that are running when in 2.2.14 and when upgraded to 4.1.0, they are unable to
connect outside. 
> This is because egress rules are introduced with no rules by default.
> This causes the VM to stop connecting to the outside world, and the traffic is one way.
> I can SSH to the VM, and  I can ping the VM , but I cannot ssh or ping from the VM. 
> I am unable to add egress rules and there is not even a single line showing the api calls
or anything related to adding the egress rules in the management log. 
> Notes: 
> Upgrade Environment:  CloudStack 2.2.14, Advance Networking with Security Groups, CentOS
> There were no issues during the upgrade process. All steps completed successfully. 
> The system VMs were upgraded successfully 
> ----------------------------------------------------------------------
> Stopping and starting 1 secondary storage vm(s)...
> Done stopping and starting secondary storage vm(s)
> Stopping and starting 1 console proxy vm(s)...
> Done stopping and starting console proxy vm(s).
> Stopping and starting 1 running routing vm(s)...
> Done restarting router(s).
> ----------------------------------------------------------------------

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message