Repository navigation
Description
Fleet versions
- Discovered: 4.93.0-rc.2609212342 (rev
71341116b4) - Reproduced:
main(revf87401fec7) on a second instance
Web browser and operating system: Chromium 147.0.7727.15 (Playwright) on macOS 27.0
💥 Actual behavior
Script-only packages whose filenames share a stem but differ in extension (hello.py, hello.sh, hello.ps1) all produce software titles named hello. Nothing in the list views tells them apart:
- Software › Inventory — one row per package, every one named
hello, every one typedScript-only package (macOS & Linux), every Version---. - Controls › Setup experience › Install software — same rows, same name, each with its own checkbox. The checkboxes select different installers, so an admin can pick the wrong interpreter for setup experience with nothing on screen to indicate it and no error.
The title detail page does show the filename in the Library card, so this is limited to list views.
🛠️ Expected behavior
Script-only packages that resolve to the same title name should be tellable apart in list views, at least wherever they can be individually selected.
🧑💻 Steps to reproduce
These steps:
- Have been confirmed to consistently lead to reproduction in multiple Fleet instances.
- Describe the workflow that led to the error, but have not yet been reproduced in multiple Fleet instances.
- Create a fleet.
- Save two script files that share a stem:
hello.pycontaining#!/usr/bin/env python3andprint("hello from python")hello.shcontaining#!/bin/shandecho "hello from sh"
- Go to Software › Add software › Custom package for that fleet and upload
hello.py. Repeat forhello.sh. - Go to Software › Inventory — two rows, both named
hello, same Type, same---Version. - Go to Controls › Setup experience › Install software › macOS — the same two
hellorows, each with its own checkbox.
🕯️ More info
Not specific to .py — .sh and .ps1 collide the same way, so this did not arrive with Python script packages. Any two script-only packages sharing a stem collide.
Script-only titles take the filename minus its extension as the title name (ee/server/service/software_installers.go:2804). That line is already present at the v4.80.0 tag, so this has been reachable for a long time.
Ordinary naming gets you there: install.sh alongside install.ps1 is a common cross-platform pairing.
Found while verifying #49087. No existing issue found — #28108 is closed and covers multiple packages under one title, which is the opposite case.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
Brajim20 commentedon Oct 5, 2026
QA Pass — 9/9 checks on
main(rev2ac91b368e) vsrc-minor-fleet-v4.93.0(revbc215a449f). Same-stem.py/.sh/.ps1packages in Software Inventory and Setup experience (Linux, Windows, macOS), filename search, select + save, custom display names, long names, and non-script packages.hello.py+hello.shin one fleethellorowshello (hello.py),hello (hello.sh)hellorows.pyrow and Savehello.pyis set to install during setup; label persists after reloadhello.pyhello (hello.py); case-insensitive;.pymatches every .py package.ps1with custom display name, Windows tab + InventoryHello WindowsHello Windows (hello.ps1)configure-corporate-vpn-client-settings.sh/.py) in Inventory.deb,.msilabelshellofleet-release commentedon Oct 29, 2026
Packages share a name
filename shows the difference
clarity matters