| mup | Bug #1982484 opened: vcenter.yaml not being created due to possible vcenter_registration metadata bug <MAAS:New> <https://launchpad.net/bugs/1982484> | 12:56 |
|---|---|---|
| mup | Bug #1982484 changed: vcenter.yaml not being created due to possible vcenter_registration metadata bug <MAAS:New> <https://launchpad.net/bugs/1982484> | 12:59 |
| mup | Bug #1982484 opened: vcenter.yaml not being created due to possible vcenter_registration metadata bug <MAAS:New> <https://launchpad.net/bugs/1982484> | 13:02 |
| jeronimo | Failed deployment: Failed to power on node - Power on for the node failed: Failed talking to node's BMC: Failed to power apk3fc. BMC never transitioned from off to on. Weird | 14:56 |
| jeronimo | one juju deployment failed | 14:56 |
| jeronimo | machine deployment | 14:56 |
| jeronimo | 2/3 lxd hosts came online | 15:00 |
| mcint | I'm having trouble getting a deploy working | 20:12 |
| mcint | I submit cloud-init / cloud-config, and don't see the users I want set up. Nor the networking or disk configuration. How does maas do base provisioning (in advance of? and) in addtion to user-provided config? | 20:13 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!