lb-afarhadi opened a new issue, #37534:
URL: https://github.com/apache/superset/issues/37534

   ### Bug description
   
   After upgrading from Superset 5.0.0 to 6.0.0, the `ab_action_log` table is 
not created during database initialization (`superset init`), causing the 
Action Logs UI to fail with an empty table display.
   
   ## Environment
   
   - **Superset Version**: 6.0.0
   - **Previous Version**: 5.0.0  
   - **Database**: PostgreSQL
   - **Deployment**: Kubernetes (Helm chart 0.15.0)
   - **Docker Image**: `apache/superset:6.0.0`
   
   ## Steps to Reproduce
   
   1. Upgrade Superset from 5.0.0 to 6.0.0
   2. Run `superset db upgrade` ✅ (completes successfully)
   3. Run `superset init` ✅ (completes successfully, no errors)
   4. Navigate to **Security > Action Log** in the UI
   5. Observe empty table with Superset logo (no data loads)
   
   ## Expected Behavior
   
   - The `ab_action_log` table should be created during `superset init`
   - Action Logs UI should display action log entries
   - Table should be queryable via API endpoint `/api/v1/log/`
   
   ## Actual Behavior
   
   - The `ab_action_log` table is **not created** during initialization
   - Action Logs UI shows empty table (no error message, just no data)
   - Other Flask-AppBuilder tables (`ab_user`, `ab_role`, `ab_permission`, 
etc.) are created successfully
   - Only `logs` and `report_execution_log` tables exist (not `ab_action_log`)
   
   ### Screenshots/recordings
   
   <img width="2112" height="850" alt="Image" 
src="https://github.com/user-attachments/assets/944bfcf9-fa0e-4717-bd33-9ca4ef93e83b";
 />
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   Workaround
   
   Manually create the table using SQL:
   
   ```sql
   CREATE TABLE IF NOT EXISTS ab_action_log (
       id SERIAL PRIMARY KEY,
       user_id INTEGER,
       action VARCHAR(200),
       object_type VARCHAR(200),
       object_id VARCHAR(200),
       referrer VARCHAR(200),
       json TEXT,
       dttm TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
       duration_ms INTEGER,
       slice_id INTEGER,
       dashboard_id INTEGER,
       CONSTRAINT ab_action_log_user_id_fkey FOREIGN KEY (user_id) 
           REFERENCES ab_user(id) ON DELETE CASCADE
   );
   
   CREATE INDEX IF NOT EXISTS idx_ab_action_log_user_id ON 
ab_action_log(user_id);
   CREATE INDEX IF NOT EXISTS idx_ab_action_log_dttm ON ab_action_log(dttm);
   CREATE INDEX IF NOT EXISTS idx_ab_action_log_action ON ab_action_log(action);
   ```
   
   After manual creation, Action Logs UI works correctly.
   
   ### Checklist
   
   - [x] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [x] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [ ] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to