ovs-bugtool(8)

✨ ovs-bugtool ✨

okay bestie, welcome to the ovs-bugtool(8) page from the Open VSwitch Manual — yes, section 8, we're in the big leagues 💅 this is the Open vSwitch bug reporting utility and she is here to help you snitch on your system (affectionately).

---

🦋 NAME 🦋

ovs-bugtool — the Open vSwitch bug reporting utility. she collects receipts. that's the whole job. 📸

---

🌸 SYNOPSIS 🌸

ovs-bugtool

that's it. that's the whole thing. no args required, she just goes. ✨

---

💖 DESCRIPTION 💖

so basically ovs-bugtool generates a debug bundle stuffed with useful information about Open vSwitch on this system, and then parks it in /var/log/ovs-bugtool. one command, one bundle, no cap. 🎀

---

🎀 COLLECTION OPTIONS 🎀

these options are the what do we even grab girlies — they influence what categories of data ovs-bugtool collects. 🧚

• --entries=list — collect the capabilities you name in that comma-separated list. picky, but make it fashion.
• --all — collect every single capability available. go big or go home, periodt. 👑
• --ovs — on top of Open vSwitch configuration and status, ovs-bugtool can collect a whole variety of relevant system information. this option says nah, keep it strictly to Open vSwitch-specific categories. lowkey a scope queen. 💅
• --log-days=days — include the logs whose last modification time falls within the previous days days in the debug bundle. heads up bestie: the number of log files included has a big impact on the eventual bundle size 😭 so don't go feral. the default value is 20 days.
• -y, --yestoall — answer yes to all prompts. consent given in advance, we love a decisive icon. ✅
• --capabilities — writes the categories that ovs-bugtool can collect to stdout in XML, then exits. a little peek behind the curtain, then she's gone. ✌️

---

🌈 OUTPUT OPTIONS 🌈

these ones are all about the format and the destination of the output, i.e. where the bundle's going and what it's wearing. 👜

• --output=filetype — generates a debug bundle with the specified file type. the options include tar, tar.gz, tar.bz2, and zip.
• --outfile=file — write output to file. this is mutually exclusive with --outfd — pick one, you can't have both, it's giving monogamy. 🙈
• --outfd=fd — write output to file descriptor fd. this option must be used with --output=tar. they're a package deal, no substitutions. 🫶
• --unlimited — do not exclude files which are too large. also skips checking free disk space. by default, up to 90 percent of the free disk space can be used — so yeah, --unlimited is the unhinged version. 💀
• --debug — print verbose debugging output. main character energy for your terminal. 🔥

---

⭐ OTHER OPTIONS ⭐

• -s, --silent — suppress most output to stdout. she's quiet, she's mysterious, she's still working. 🤫
• --help — print a summary of ovs-bugtool usage to stdout, then exit. the classic "hi, what do you do" move. 💜

---

🍓 EXAMPLES 🍓

here's a collection of some commonly useful options, bestie — copy, paste, slay:

ovs-bugtool -y -s --output=tar.gz --outfile=/var/log/bugtool-report.tgz

---

💀 BUGS 💀

ovs-bugtool makes many assumptions about file locations and the availability of system utilities. it has been tested on Debian and Red Hat and derived distributions. on other distributions it is likely to be less useful. so like… she has a type, and that type is Debian and Red Hat. not me warning you in advance 😭

---

okay that's the whole page, you ate that fr fr 💅 this was ovs-bugtool(8) from the Open VSwitch Manual, and the source/version riding at the bottom of the original is Open vSwitch 3.7.1 — so shoutout to that release, and bye bestie, go file a beautiful bug 🦋✨