I would have thought the active MDS, on another node would be satisfying that requirement.
Further, I wonder why the 130 second delay is being ignored. Ignore that, I just read the manual. The delay is for subsequent VMs.
> Startup delay: Defines the interval between this VM start and...
Good question.
Syslog seems to indicate systemd[1]: Mounting /mnt/pve/fs... does not commence mounting the CephFS filesystem until well after the PVE Guests have notionally started booting.
TIA, Piers
non-snipped log outputs
/var/log/syslog -->...
Anyone else having trouble with VMs not automatically starting on host reboots, when relying on CephFS for cloud-config snippet storage?
TASK ERROR: can't open '/mnt/pve/fs/snippets/321-k8s-worker-1-ci-user-k8s-focal.yaml' - No such file or directory
This occurs with both RancherOS and Ubuntu...
UPDATE:
Successfully had the network settings to applied with the latest Ubuntu Bionic 18.04.4 and OVMF (UEFI)
Through some trial and error I can confirm this is not a problem, although the network.yaml is a finicky, and when one changes the BIOS type, the udev rules rename the interface...
am finding something similar with Ubuntu Bionic 18.04.4, although even with i440fx, the network will not come up.
This, is when providing an ENI, Netplan v1 and v2 network config. Each of which plumbed into the configdrive via
qm set 871 --cicustom...
Is this really SOLVED? Reverting to this methodology appears to be a retrograde step
I had a similar issue, wherein I also had
```
iface vmbr87 inet static
bridge_ports bond0.87
```
and regular a vmbr0 interface.
To fix this..
I found the `vmbr0` interface setup had to preceed the others...
I can also confirm qemu-server 6.0-5 works (6.0-9 and 6.0-13 does not load cloud images correctly)
Migrating these VMs, created on downgraded host with qemu-server 6.0-5, to a another host with latest qemu-server 6.0-13, then boot just fine.
NB: the command to downgrade is `apt install...
How to specify DB device (not WAL device) for Bluestore OSD?
The Proxmox documentation of pveceph (pve.proxmox.com/pve-docs/chapter-pveceph.html) clearly shows how to specify a WAL device, but not a DB device.
pveceph createosd /dev/sdn -wal_dev /dev/sdb
Having used this method, within the...
Ah.. I found a misconfigured port on my switching fabric. Proxmox 4.4 must have tolerated it, albeit with many a dropped packet no doubt.
One of the VLANs, on one of the physical interface mappings (out of a pair for bonding) within HPE VirtualConnect was incorrectly tagged. So, I guess, as...
With 4.4, I could assign IP addresses to two bridges, on different VLANs interfaces, on the same bond. Something, possibly the bridge configuration in Debian Stretch, is not happy with my setup.
All machines use bonded NICs with VLANs. In both cases the last bridge to be configured is used for...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.