Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

VMs with security groups allowing all egress traffic cannot access the Internet in 4.23.0.0

Open
#14,099 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
java

Research direction

No files, tests, or entry points are identified. First reproduce the 4.23.0.0 case with an egress-only security group allowing 0.0.0.0/0, then compare it with an older working version and trace the security-group egress path. Done means the VM can initiate Internet connections with no ingress rules and the relevant regression is covered by a test.

Written by the indexing model from the issue text.

Description

bug
problem

Description

In CloudStack 4.23.0.0, a VM cannot access the Internet when its security group has egress rules configured, even when the egress rules allow all outbound traffic (0.0.0.0/0).

The same configuration works as expected in older CloudStack versions.

The issue occurs when the security group has egress rules but no ingress rules.

Expected behavior

The VM should be able to initiate outbound connections to the Internet when the security group has an egress rule allowing all traffic.

According to the CloudStack documentation:

If there is no Egress rule in a Security Group, all the outgoing traffic will be allowed.
If there are Egress rules in a Security Group, only the outgoing traffic which match a Egress rule will be allowed.
Only the incoming traffic which match a Ingress rule will be allowed.

Actual behavior

With CloudStack 4.23.0.0:

  • The VM has a security group assigned.
  • The security group has one egress rule allowing ALL outbound traffic.
  • There are no ingress rules.
  • The VM cannot access the Internet.
Image Image
versions

The versions of ACS, hypervisors, storage, network etc..

The steps to reproduce the bug

...

What to do about it?

No response

Dominant language
Java
Stars
3.1k
Forks
1.4k
Avg merge
6d 20h
Merged PRs (30d)
27

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/cloudstack

All issues in apache/cloudstack

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.