You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using maas3.4.4
Each time a unit enrolls and commissions into MAAS, a random fabric is being created based off the servers USB. We cant delete the fabrics because they are assigned to servers currently enrolled in maas.
We now have to wait until stress testing is completed, delete the machine, then delete the fabrics.
Process
Anytime a unit is enrolled into maas, a random fabric is created from the servers USB. We cant delete the fabrics because they are assigned to servers currently enrolled in maas. We now have to wait until stress testing is completed, delete the machine, then delete the fabrics.
Current and expected result
I can reproduce this issue every time. the issue being we test 100's of machines a week, for every machine that gets into a maas, a random fabric is being created based on the servers USB. We then have to manually delete every single random fabric, so we can even see our correct fabric addresses.
We have tried altering the default script thats causing this issue but maas does not allow us to edit default scripts. the only work around we can find is to run a nightly cron job to delete all of the random fabrics.
Expected results:
this should not be happening, only fabrics we have assigned and created should be showing up.
Screenshot
The text was updated successfully, but these errors were encountered:
Summary
Using maas3.4.4
Each time a unit enrolls and commissions into MAAS, a random fabric is being created based off the servers USB. We cant delete the fabrics because they are assigned to servers currently enrolled in maas.
We now have to wait until stress testing is completed, delete the machine, then delete the fabrics.
Process
Anytime a unit is enrolled into maas, a random fabric is created from the servers USB. We cant delete the fabrics because they are assigned to servers currently enrolled in maas. We now have to wait until stress testing is completed, delete the machine, then delete the fabrics.
Current and expected result
I can reproduce this issue every time. the issue being we test 100's of machines a week, for every machine that gets into a maas, a random fabric is being created based on the servers USB. We then have to manually delete every single random fabric, so we can even see our correct fabric addresses.
We have tried altering the default script thats causing this issue but maas does not allow us to edit default scripts. the only work around we can find is to run a nightly cron job to delete all of the random fabrics.
Expected results:
this should not be happening, only fabrics we have assigned and created should be showing up.
Screenshot
The text was updated successfully, but these errors were encountered: