I copied the wrong link. The upstream issue is documented here: https://gitlab.isc.org/isc-projects/kea/-/work_items/3792
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Jul 9 2026
Jul 8 2026
Jul 7 2026
sorry, With VPP sFlow enabled but without set system sflow enable-egress, the generated hsflowd config will not contain psample { group=1 }. I cannot edit this task. I think I choose the wrong form type (I should create bug report, not task)
For me, VyOS Stream 2026.03 works on EVE-NG. However, it has security vulnerabilities. It's better to use v1.4.4-S1 or v1.5.0-S1.
I uploaded the report archive, but I do not see it attached/available in the submission view. To make sure the materials are accessible, I also placed the
complete report package here:
Jul 6 2026
Updated to:
Version: VyOS 2026.06.30-0048-rolling
Release train: rolling
Release flavor: generic
That is the test case bug introduced by PR 466
I will create a separate fix to the tests
Jul 5 2026
2026-07-05 triage: keeping open, re-scoped. Since this was filed, most per-repo GHA was retired in favor of central Mergify automation (T8937), which shrank the fork-spam surface — but scheduled/cron workflows (e.g. CodeQL callers) still run on forks where jobs lack an owner guard. Remaining work = a fleet sweep adding if: github.repository_owner == 'vyos' (or the schedule-conditional variant) to jobs in scheduled workflows. Small, bounded; will be scheduled as an owner-guard sweep work item.
Resolving in the 2026-07-05 stale-High triage (operator-confirmed). Overtaken by the 2026-05-30 default-branch rename (rollout 1c: 93 renames + ruleset-condition PATCHes) and the 2026-06-02 frozen current backport-alias restore (40 repos), which together resolved the fleet's branch-reference debt. No remaining actionable content identified on this task (empty description).
Resolving in the 2026-07-05 stale-High triage (operator-confirmed). Delivered: the Mergify conflict check ships fleet-wide via the central baselines (vyos/mergify + VyOS-Networks/mergify, consumed by extends: on ~105 repos) — Label conflicting pull requests rule + conflicts merge-protection gate (T8615/T8935, shipped 2026-05-28).
Resolving in the 2026-07-05 stale-High triage (operator-confirmed). Delivered by later work: the custom/eps1lon conflict-check GHA was retired under T8937 (retirement closed 2026-06-12); conflict detection now runs via the central Mergify Label conflicting pull requests rule (T8615/T8935) plus the committed-marker script path (T8934). Nothing left to disable.
Related: https://vyos.dev/T8940
Why not use already existing prebuild FIPS edition of OpenSSL available in Debian?
According to:
Current kernel config available at:
Just guessing.
I want to have a 2nd opinion on that following this forum post:
Jul 4 2026
Thank you for the clarification.
Jul 3 2026
At least google AI tells me this:
Spent some time trying to chase this down. I managed to set up a VM to build the VyOS image, but I can't figure out how to build the kernel. The docs appear to be outdated?
Fix up as draft PR: https://github.com/vyos/vyos-1x/pull/5310
@natali-rs1985 You're right, looks like it's not being included in the package build! I'll investigate further, thanks!
Smoketests are failing: