Security Group without rules displays a phantom Any/Any rule that is persisted when edited and saved

Open Beginner friendly
  • Is something wrong?
#8,267 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 19 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

The issue identifies Sunstone (FireEdge) Security Groups and explains that missing rules become an undefined entry in both the edit form and details view. Start by locating those form initialization and details rendering paths, then trace how the schema supplies default rule values. Done means a group with no rules shows an empty list and remains empty after editing and saving.

Written by the indexing model from the issue text.

Description

Priority: High Status: Pending

Description
When creating a Security Group without any rules in Sunstone, the details view displays an Any/Any rule even though no rule exists in the template.

Editing and saving this Security Group without adding a rule then persists the automatically generated rule in the template.

To Reproduce

  1. Create a Security Group without adding any rules.
  2. Open its details view.
  3. Observe that an Any/Any rule is displayed despite the template containing no rules.
  4. Edit the Security Group and save it without adding any rules.
  5. Inspect the template: a rule has now been added.

Expected behavior
A Security Group created without rules should display an empty rule list. Editing and saving it should preserve that empty list unless the user explicitly adds a rule.

Details

  • Affected Component: Sunstone (FireEdge), Security Groups
  • Hypervisor: kvm
  • Version: 7.4.1

Additional context
Missing rules are converted into [undefined] when initializing the edit form. Schema casting then populates this entry with default rule values, which are persisted when the form is saved.

The details view also converts a missing rule into a list containing an undefined entry, rendering a phantom row with All/Any values.

Progress Status

  • Code committed
  • Testing - QA
  • Documentation (Release notes - resolved issues, compatibility, known issues)
Dominant language
JavaScript
Stars
1.7k
Forks
534
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 OpenNebula/one

All issues in OpenNebula/one

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.