Description
Summary of Topic
The Super may think it's a worker upon an initial install if you're re-deploying the super onto an existing /data partition. When AO sees that there's an existing partition then they will not run phinitsuper and your VA deployment would think it's a worker immediately.
This usually would be a deployment pit fall if you previously had an installation and mounted the /data partition to the same point as the previous install within the initial configuration of the VA
Steps
To resolve this issue upon installation of a super on top of an existing /data deployment, we would perform the following:
1 - Log into AO through SSH as root user
2 - /opt/phoenix/deployment/jumpbox/phinitsuper
3 - After the system reboots, please follow the related KB article "How to restore the CMDB if I have a backup" to restore the CMDB from a backup.
Additional Information
Version Affected
ALL
phinitsuper will initialize cmdb. If system is new deployment, that’s fine. But, it there is existing system. CMDB backup should be restored.
Better way is umonut /data and remount it with dummy partition. After phinitsuper command, remount original /data.
Related Articles
Technical Note: [Accelops KB] How to restore the CMDB if I have a backup
