Open RachelElysia opened 4 weeks ago
No estimation since it sounded like Product decision if this is a bug or not, our team was under the impression that the host should just expire then.
cc: @noahtalerman
Thanks Rachel. Pulled this bug onto the drafting board to investigate.
Hey @marko-lisica heads up, I passed this bug to you.
Not sure if this is a bug or not. I think up to you.
Hey @marko-lisica heads up, I assigned myself to this bug and #21345 (another bug) so that you can focus on Fleet's app library (#18865).
Ah, @sharon-fdm and @RachelElysia this is a bug. I misunderstood the title (updated it).
I moved this bug back to the release board.
Hey team! Please add your planning poker estimate with Zenhub @lucasmrod @getvictor
Timebox investigation to 3
Was unable to run migration assistant locally using Parallels Desktop or tart
on Apple Silicon hardware, probably due to networking limitations. Will need someone with physical hardware to replicate and diagnose.
Fleet version: <!-- Copy this from the "My account" page in the Fleet UI, or run
fleetctl --version
-->Web browser and operating system:
💥 Actual behavior
@zayhanlon used Migration Assistant from her MacBook Air to this MacBook Pro.
Fleet correctly created two hosts (in reality it's two workstations) but Fleet thinks both hosts are the same MacBookPro (same serial number). Here's the host vitals for both hosts: https://docs.google.com/document/d/1NOyeVqnvb4eIhn47ELRLBZBI6f9x-kksHHlMZavEofY/edit
🧑💻 Steps to reproduce
🕯️ More info (optional)
More context in Slack here.
🛠️ To fix
After Migration Assistant, Fleet has two records for the old and new host. Both hosts display host vitals relevant to them.