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
@@ -159,7 +159,7 @@ This error will disappear after a certain time period from `machine issues`. You
159
159
160
160
#### asn-not-unique
161
161
162
-
This issue was introduced by a bug in earlier versions of metal-stack and was fixed in https://github.com/metal-stack/metal-api/pull/105.
162
+
This issue was introduced by a bug in earlier versions of metal-stack and was fixed in [PR105](https://github.com/metal-stack/metal-api/pull/105.)
163
163
164
164
To resolve the issue, you need to recreate the firewalls that use the same ASN.
165
165
@@ -181,6 +181,18 @@ The [metal-bmc](https://github.com/metal-stack/metal-bmc) is responsible to repo
181
181
182
182
When there is no distinct IP address for the BMC, it can be that an orphaned machine used this IP in the past. In this case, you need to clean up the orphaned machine through `metalctl machine rm --remove-from-database`.
183
183
184
+
#### bmc-info-outdated
185
+
186
+
The [metal-bmc](https://github.com/metal-stack/metal-bmc) is responsible to report bmc details for the machine's [BMC](https://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface#Baseboard_management_controller).
187
+
188
+
When the metal-bmc was not able to fetch the bmc info for longer than 20 minutes, something is wrong with the BMC configuration of the machine. This can be caused by one of the following reasons:
189
+
190
+
- Wrong password for the root user is configured in the BMC
191
+
- ip address of the BMC is either wrong or not present
192
+
- the device on the given ip address is not a machine, maybe a switch or a management component which is not managed by the metal-api
193
+
194
+
In either case, please check the logs for the given machine UUID on the metal-bmc for further details. Also check that the metal-bmc is configured to only consider BMC IPs in the range they are configured from the DHCP server in the partition. This prevents grabbing unrelated BMCs.
195
+
184
196
### A machine has registered with a different UUID after reboot
185
197
186
198
metal-stack heavily relies on steady machine UUIDs as the UUID is the primary key of the machine entity in the metal-api.
@@ -192,8 +204,8 @@ For further reference also see [metal-stack/metal-hammer#52](https://github.com/
192
204
There are some scenarios (can be vendor-specific), which can cause a machine UUID to change over time, e.g.:
193
205
194
206
- When the UUID partly contains of a network card's mac address, it can happen when:
195
-
- Exchanging network cards
196
-
- Disabling network cards through BIOS
207
+
- Exchanging network cards
208
+
- Disabling network cards through BIOS
197
209
- Changing the UUID through vendor-specific CLI tool
0 commit comments