Module
resource_calendar
Describe the bug
After migrating from Odoo 16 Community to Odoo 17 Community with OpenUpgrade, exactly one resource.calendar record is missing in the target database.
In my case, the screenshot shows the source database on the left (Odoo 16, before migration) and the target database on the right (Odoo 17, after migration). The record exists in the Odoo 16 database, but it is no longer present after the migration.
This appears to be specific to my database, but it clearly indicates that at least one resource.calendar entry was not migrated correctly.
I do not use resource_calendar_leave in my setup, and I do not need it for this migration.
To Reproduce
Affected versions:
- Source: Odoo 16 Community
- Target: Odoo 17 Community
- Migration tool: OpenUpgrade
Steps to reproduce the behavior:
- Migrate an Odoo 16 Community database to Odoo 17 Community using OpenUpgrade.
- Compare the
public.resource_calendar table before and after migration.
- Check whether all
resource.calendar records are still present.
Expected behavior
All resource.calendar records from the source database should still exist after migration.
Actual behavior
Exactly one resource.calendar record is missing after migration.
Additional context
The missing record is visible in the source database before migration, but not in the target database afterward. The issue is based on a direct comparison between both databases.

Module
resource_calendarDescribe the bug
After migrating from Odoo 16 Community to Odoo 17 Community with OpenUpgrade, exactly one
resource.calendarrecord is missing in the target database.In my case, the screenshot shows the source database on the left (Odoo 16, before migration) and the target database on the right (Odoo 17, after migration). The record exists in the Odoo 16 database, but it is no longer present after the migration.
This appears to be specific to my database, but it clearly indicates that at least one
resource.calendarentry was not migrated correctly.I do not use
resource_calendar_leavein my setup, and I do not need it for this migration.To Reproduce
Affected versions:
Steps to reproduce the behavior:
public.resource_calendartable before and after migration.resource.calendarrecords are still present.Expected behavior
All
resource.calendarrecords from the source database should still exist after migration.Actual behavior
Exactly one
resource.calendarrecord is missing after migration.Additional context
The missing record is visible in the source database before migration, but not in the target database afterward. The issue is based on a direct comparison between both databases.