aabouelleil-seniorlink commented on issue #26497:
URL: https://github.com/apache/airflow/issues/26497#issuecomment-1318721008
> We started with 1.8.xx, went to 1.9.xx, 1.10.xx, and somehow all of our
FAB tables ended up without sequences set for their IDs, but had the sequences
created. We were seeing similar issues in 2.4.0, and manually ran:
>
> ```sql
> ALTER TABLE "public"."ab_permission_view" ALTER COLUMN "id" SET DEFAULT
nextval('ab_permission_view_id_seq'::regclass);
> ALTER TABLE "public"."ab_permission" ALTER COLUMN "id" SET DEFAULT
nextval('ab_permission_id_seq'::regclass);
> ALTER TABLE "public"."ab_permission_view_role" ALTER COLUMN "id" SET
DEFAULT nextval('ab_permission_view_role_id_seq'::regclass);
> ALTER TABLE "public"."ab_register_user" ALTER COLUMN "id" SET DEFAULT
nextval('ab_register_user_id_seq'::regclass);
> ALTER TABLE "public"."ab_role" ALTER COLUMN "id" SET DEFAULT
nextval('ab_role_id_seq'::regclass);
> ALTER TABLE "public"."ab_user" ALTER COLUMN "id" SET DEFAULT
nextval('ab_user_id_seq'::regclass);
> ALTER TABLE "public"."ab_user_role" ALTER COLUMN "id" SET DEFAULT
nextval('ab_user_role_id_seq'::regclass);
> ALTER TABLE "public"."ab_view_menu" ALTER COLUMN "id" SET DEFAULT
nextval('ab_view_menu_id_seq'::regclass);
> ```
>
> Which resolved our issue.
We ran into this issue upgrading from 2.3.1 to 2.4.1 so it doesn't seem the
issue is fixed yet. These table alterations resolved the problem though.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
