Activity log for bug #1973804

Date Who What changed Old value New value Message
2022-05-17 17:27:49 Loic Houpert bug added bug
2022-05-17 17:27:49 Loic Houpert attachment added Logs https://bugs.launchpad.net/bugs/1973804/+attachment/5590470/+files/maaslogfiles.tar.gz
2022-05-17 17:30:27 Loic Houpert description I am using maas 3.1.0-10901-g.f1f8f1505 and lxd 5.1. I made sure virtualisation was activated in my bios and kvm-ok is returning : >> INFO: /dev/kvm exists >> KVM acceleration can be used I tried to add a VM using the CLI and the MAAS UI. I am trying to create VMs in MAAS following this tutorial https://github.com/antongisli/maas-baremetal-k8s-tutorial/blob/main/maas-setup.sh but I encounter a problem when I run: >> maas admin vm-host compose $VM_HOST_ID cores=8 memory=2048 architecture="amd64/generic" \ storage="main:16(pool1)" hostname="juju-controller" I got the message: "VM host does not support composability." If I try to add a VM manually through the MAAS UI, I have the error message "Error: An architecture is required." To reproduce this behavior, run the commands below in the terminal (from https://github.com/antongisli/maas-baremetal-k8s-tutorial/blob/main/maas-setup.sh): # lxd / maas issue. either upgrade lxd or maas to 3.1 sudo snap install --channel=latest/stable lxd sudo snap refresh --channel=latest/stable lxd sudo snap install jq sudo snap install maas sudo snap install maas-test-db # clone the git repository cd ~ git clone https://github.com/antongisli/maas-baremetal-k8s-tutorial.git # get local interface name (this assumes a single default route is present) export INTERFACE=$(ip route | grep default | cut -d ' ' -f 5) export IP_ADDRESS=$(ip -4 addr show dev $INTERFACE | grep -oP '(?<=inet\s)\d+(\.\d+){3}') sudo sed -i 's/#net.ipv4.ip_forward=1/net.ipv4.ip_forward=1/' /etc/sysctl.conf sudo sysctl -p sudo iptables -t nat -A POSTROUTING -o $INTERFACE -j SNAT --to $IP_ADDRESS # LXD init sudo cat maas-baremetal-k8s-tutorial/lxd.conf | lxd init --preseed # verify LXD network config lxc network show lxdbr0 # Wait for LXD to be ready lxd waitready # Initialise MAAS sudo maas init region+rack --database-uri maas-test-db:/// --maas-url http://${IP_ADDRESS}:5240/MAAS sleep 15 # Create MAAS admin and grab API key sudo maas createadmin --username admin --password admin --email admin export APIKEY=$(sudo maas apikey --username admin) # MAAS admin login maas login admin 'http://localhost:5240/MAAS/' $APIKEY # Configure MAAS networking (set gateways, vlans, DHCP on etc) export SUBNET=10.10.10.0/24 export FABRIC_ID=$(maas admin subnet read "$SUBNET" | jq -r ".vlan.fabric_id") export VLAN_TAG=$(maas admin subnet read "$SUBNET" | jq -r ".vlan.vid") export PRIMARY_RACK=$(maas admin rack-controllers read | jq -r ".[] | .system_id") maas admin subnet update $SUBNET gateway_ip=10.10.10.1 maas admin ipranges create type=dynamic start_ip=10.10.10.200 end_ip=10.10.10.254 maas admin vlan update $FABRIC_ID $VLAN_TAG dhcp_on=True primary_rack=$PRIMARY_RACK maas admin maas set-config name=upstream_dns value=8.8.8.8 # Add LXD as a VM host for MAAS and capture the VM_HOST_ID export VM_HOST_ID=$(maas admin vm-hosts create password=password type=lxd power_address=https://${IP_ADDRESS}:8443 \ project=maas | jq '.id') # allow high CPU oversubscription so all VMs can use all cores maas admin vm-host update $VM_HOST_ID cpu_over_commit_ratio=4 # create tags for MAAS maas admin tags create name=juju-controller comment='This tag should to machines that will be used as juju controllers' maas admin tags create name=metal comment='This tag should to machines that will be used as bare metal' ### creating VMs for Juju controller and our "bare metal" # add a VM for the juju controller with minimal memory maas admin vm-host compose $VM_HOST_ID cores=8 memory=2048 architecture="amd64/generic" \ storage="main:16(pool1)" hostname="juju-controller" # get the system-id and tag the machine with "juju-controller" export JUJU_SYSID=$(maas admin machines read | jq '.[] | select(."hostname"=="juju-controller") | .["system_id"]' | tr -d '"') maas admin tag update-nodes "juju-controller" add=$JUJU_SYSID Is it something I am using maas 3.1.0-10901-g.f1f8f1505 and lxd 5.1. I made sure virtualisation was activated in my bios and kvm-ok is returning : >> INFO: /dev/kvm exists >> KVM acceleration can be used I tried to add a VM using the CLI and the MAAS UI. I am trying to create VMs in MAAS following this tutorial https://github.com/antongisli/maas-baremetal-k8s-tutorial/blob/main/maas-setup.sh but I encounter a problem when I run: >> maas admin vm-host compose $VM_HOST_ID cores=8 memory=2048 architecture="amd64/generic" \  storage="main:16(pool1)" hostname="juju-controller" I got the message: "VM host does not support composability." If I try to add a VM manually through the MAAS UI, I have the error message "Error: An architecture is required." To reproduce this behavior, run the commands below in the terminal (from https://github.com/antongisli/maas-baremetal-k8s-tutorial/blob/main/maas-setup.sh): # lxd / maas issue. either upgrade lxd or maas to 3.1 sudo snap install --channel=latest/stable lxd sudo snap refresh --channel=latest/stable lxd sudo snap install jq sudo snap install maas sudo snap install maas-test-db # clone the git repository cd ~ git clone https://github.com/antongisli/maas-baremetal-k8s-tutorial.git # get local interface name (this assumes a single default route is present) export INTERFACE=$(ip route | grep default | cut -d ' ' -f 5) export IP_ADDRESS=$(ip -4 addr show dev $INTERFACE | grep -oP '(?<=inet\s)\d+(\.\d+){3}') sudo sed -i 's/#net.ipv4.ip_forward=1/net.ipv4.ip_forward=1/' /etc/sysctl.conf sudo sysctl -p sudo iptables -t nat -A POSTROUTING -o $INTERFACE -j SNAT --to $IP_ADDRESS # LXD init sudo cat maas-baremetal-k8s-tutorial/lxd.conf | lxd init --preseed # verify LXD network config lxc network show lxdbr0 # Wait for LXD to be ready lxd waitready # Initialise MAAS sudo maas init region+rack --database-uri maas-test-db:/// --maas-url http://${IP_ADDRESS}:5240/MAAS sleep 15 # Create MAAS admin and grab API key sudo maas createadmin --username admin --password admin --email admin export APIKEY=$(sudo maas apikey --username admin) # MAAS admin login maas login admin 'http://localhost:5240/MAAS/' $APIKEY # Configure MAAS networking (set gateways, vlans, DHCP on etc) export SUBNET=10.10.10.0/24 export FABRIC_ID=$(maas admin subnet read "$SUBNET" | jq -r ".vlan.fabric_id") export VLAN_TAG=$(maas admin subnet read "$SUBNET" | jq -r ".vlan.vid") export PRIMARY_RACK=$(maas admin rack-controllers read | jq -r ".[] | .system_id") maas admin subnet update $SUBNET gateway_ip=10.10.10.1 maas admin ipranges create type=dynamic start_ip=10.10.10.200 end_ip=10.10.10.254 maas admin vlan update $FABRIC_ID $VLAN_TAG dhcp_on=True primary_rack=$PRIMARY_RACK maas admin maas set-config name=upstream_dns value=8.8.8.8 # Add LXD as a VM host for MAAS and capture the VM_HOST_ID export VM_HOST_ID=$(maas admin vm-hosts create password=password type=lxd power_address=https://${IP_ADDRESS}:8443 \  project=maas | jq '.id') # allow high CPU oversubscription so all VMs can use all cores maas admin vm-host update $VM_HOST_ID cpu_over_commit_ratio=4 # create tags for MAAS maas admin tags create name=juju-controller comment='This tag should to machines that will be used as juju controllers' maas admin tags create name=metal comment='This tag should to machines that will be used as bare metal' ### creating VMs for Juju controller and our "bare metal" # add a VM for the juju controller with minimal memory maas admin vm-host compose $VM_HOST_ID cores=8 memory=2048 architecture="amd64/generic" \  storage="main:16(pool1)" hostname="juju-controller" # get the system-id and tag the machine with "juju-controller" export JUJU_SYSID=$(maas admin machines read | jq '.[] | select(."hostname"=="juju-controller") | .["system_id"]' | tr -d '"') maas admin tag update-nodes "juju-controller" add=$JUJU_SYSID
2022-05-17 17:32:00 Loic Houpert attachment added screenshot MAAS UI https://bugs.launchpad.net/maas/+bug/1973804/+attachment/5590472/+files/19f0245303d41bff041c86dd3a4cab349b4f47e9.png
2022-05-18 18:13:51 Bill Wear maas: status New Triaged
2022-05-18 18:13:58 Bill Wear maas: importance Undecided Medium
2022-05-19 08:51:47 Loic Houpert description I am using maas 3.1.0-10901-g.f1f8f1505 and lxd 5.1. I made sure virtualisation was activated in my bios and kvm-ok is returning : >> INFO: /dev/kvm exists >> KVM acceleration can be used I tried to add a VM using the CLI and the MAAS UI. I am trying to create VMs in MAAS following this tutorial https://github.com/antongisli/maas-baremetal-k8s-tutorial/blob/main/maas-setup.sh but I encounter a problem when I run: >> maas admin vm-host compose $VM_HOST_ID cores=8 memory=2048 architecture="amd64/generic" \  storage="main:16(pool1)" hostname="juju-controller" I got the message: "VM host does not support composability." If I try to add a VM manually through the MAAS UI, I have the error message "Error: An architecture is required." To reproduce this behavior, run the commands below in the terminal (from https://github.com/antongisli/maas-baremetal-k8s-tutorial/blob/main/maas-setup.sh): # lxd / maas issue. either upgrade lxd or maas to 3.1 sudo snap install --channel=latest/stable lxd sudo snap refresh --channel=latest/stable lxd sudo snap install jq sudo snap install maas sudo snap install maas-test-db # clone the git repository cd ~ git clone https://github.com/antongisli/maas-baremetal-k8s-tutorial.git # get local interface name (this assumes a single default route is present) export INTERFACE=$(ip route | grep default | cut -d ' ' -f 5) export IP_ADDRESS=$(ip -4 addr show dev $INTERFACE | grep -oP '(?<=inet\s)\d+(\.\d+){3}') sudo sed -i 's/#net.ipv4.ip_forward=1/net.ipv4.ip_forward=1/' /etc/sysctl.conf sudo sysctl -p sudo iptables -t nat -A POSTROUTING -o $INTERFACE -j SNAT --to $IP_ADDRESS # LXD init sudo cat maas-baremetal-k8s-tutorial/lxd.conf | lxd init --preseed # verify LXD network config lxc network show lxdbr0 # Wait for LXD to be ready lxd waitready # Initialise MAAS sudo maas init region+rack --database-uri maas-test-db:/// --maas-url http://${IP_ADDRESS}:5240/MAAS sleep 15 # Create MAAS admin and grab API key sudo maas createadmin --username admin --password admin --email admin export APIKEY=$(sudo maas apikey --username admin) # MAAS admin login maas login admin 'http://localhost:5240/MAAS/' $APIKEY # Configure MAAS networking (set gateways, vlans, DHCP on etc) export SUBNET=10.10.10.0/24 export FABRIC_ID=$(maas admin subnet read "$SUBNET" | jq -r ".vlan.fabric_id") export VLAN_TAG=$(maas admin subnet read "$SUBNET" | jq -r ".vlan.vid") export PRIMARY_RACK=$(maas admin rack-controllers read | jq -r ".[] | .system_id") maas admin subnet update $SUBNET gateway_ip=10.10.10.1 maas admin ipranges create type=dynamic start_ip=10.10.10.200 end_ip=10.10.10.254 maas admin vlan update $FABRIC_ID $VLAN_TAG dhcp_on=True primary_rack=$PRIMARY_RACK maas admin maas set-config name=upstream_dns value=8.8.8.8 # Add LXD as a VM host for MAAS and capture the VM_HOST_ID export VM_HOST_ID=$(maas admin vm-hosts create password=password type=lxd power_address=https://${IP_ADDRESS}:8443 \  project=maas | jq '.id') # allow high CPU oversubscription so all VMs can use all cores maas admin vm-host update $VM_HOST_ID cpu_over_commit_ratio=4 # create tags for MAAS maas admin tags create name=juju-controller comment='This tag should to machines that will be used as juju controllers' maas admin tags create name=metal comment='This tag should to machines that will be used as bare metal' ### creating VMs for Juju controller and our "bare metal" # add a VM for the juju controller with minimal memory maas admin vm-host compose $VM_HOST_ID cores=8 memory=2048 architecture="amd64/generic" \  storage="main:16(pool1)" hostname="juju-controller" # get the system-id and tag the machine with "juju-controller" export JUJU_SYSID=$(maas admin machines read | jq '.[] | select(."hostname"=="juju-controller") | .["system_id"]' | tr -d '"') maas admin tag update-nodes "juju-controller" add=$JUJU_SYSID I am using maas 3.1.0-10901-g.f1f8f1505 and lxd 5.1. I made sure virtualisation was activated in my bios and kvm-ok is returning : >> INFO: /dev/kvm exists >> KVM acceleration can be used I tried to add a VM using the CLI and the MAAS UI. I am trying to create VMs in MAAS following this tutorial https://github.com/antongisli/maas-baremetal-k8s-tutorial/blob/main/maas-setup.sh but I encounter a problem when I run: >> maas admin vm-host compose $VM_HOST_ID cores=8 memory=2048 architecture="amd64/generic" \  storage="main:16(pool1)" hostname="juju-controller" I got the message: "VM host does not support composability." If I try to add a VM manually through the MAAS UI, I have the error message "Error: An architecture is required." (see screenshot attached) To reproduce this behavior, run the commands below in the terminal (from https://github.com/antongisli/maas-baremetal-k8s-tutorial/blob/main/maas-setup.sh): # lxd / maas issue. either upgrade lxd or maas to 3.1 sudo snap install --channel=latest/stable lxd sudo snap refresh --channel=latest/stable lxd sudo snap install jq sudo snap install maas sudo snap install maas-test-db # clone the git repository cd ~ git clone https://github.com/antongisli/maas-baremetal-k8s-tutorial.git # get local interface name (this assumes a single default route is present) export INTERFACE=$(ip route | grep default | cut -d ' ' -f 5) export IP_ADDRESS=$(ip -4 addr show dev $INTERFACE | grep -oP '(?<=inet\s)\d+(\.\d+){3}') sudo sed -i 's/#net.ipv4.ip_forward=1/net.ipv4.ip_forward=1/' /etc/sysctl.conf sudo sysctl -p sudo iptables -t nat -A POSTROUTING -o $INTERFACE -j SNAT --to $IP_ADDRESS # LXD init sudo cat maas-baremetal-k8s-tutorial/lxd.conf | lxd init --preseed # verify LXD network config lxc network show lxdbr0 # Wait for LXD to be ready lxd waitready # Initialise MAAS sudo maas init region+rack --database-uri maas-test-db:/// --maas-url http://${IP_ADDRESS}:5240/MAAS sleep 15 # Create MAAS admin and grab API key sudo maas createadmin --username admin --password admin --email admin export APIKEY=$(sudo maas apikey --username admin) # MAAS admin login maas login admin 'http://localhost:5240/MAAS/' $APIKEY # Configure MAAS networking (set gateways, vlans, DHCP on etc) export SUBNET=10.10.10.0/24 export FABRIC_ID=$(maas admin subnet read "$SUBNET" | jq -r ".vlan.fabric_id") export VLAN_TAG=$(maas admin subnet read "$SUBNET" | jq -r ".vlan.vid") export PRIMARY_RACK=$(maas admin rack-controllers read | jq -r ".[] | .system_id") maas admin subnet update $SUBNET gateway_ip=10.10.10.1 maas admin ipranges create type=dynamic start_ip=10.10.10.200 end_ip=10.10.10.254 maas admin vlan update $FABRIC_ID $VLAN_TAG dhcp_on=True primary_rack=$PRIMARY_RACK maas admin maas set-config name=upstream_dns value=8.8.8.8 # Add LXD as a VM host for MAAS and capture the VM_HOST_ID export VM_HOST_ID=$(maas admin vm-hosts create password=password type=lxd power_address=https://${IP_ADDRESS}:8443 \  project=maas | jq '.id') # allow high CPU oversubscription so all VMs can use all cores maas admin vm-host update $VM_HOST_ID cpu_over_commit_ratio=4 # create tags for MAAS maas admin tags create name=juju-controller comment='This tag should to machines that will be used as juju controllers' maas admin tags create name=metal comment='This tag should to machines that will be used as bare metal' ### creating VMs for Juju controller and our "bare metal" # add a VM for the juju controller with minimal memory maas admin vm-host compose $VM_HOST_ID cores=8 memory=2048 architecture="amd64/generic" \  storage="main:16(pool1)" hostname="juju-controller" # get the system-id and tag the machine with "juju-controller" export JUJU_SYSID=$(maas admin machines read | jq '.[] | select(."hostname"=="juju-controller") | .["system_id"]' | tr -d '"') maas admin tag update-nodes "juju-controller" add=$JUJU_SYSID
2022-09-22 08:45:01 Jerzy Husakowski summary [3.1] Impossible to add virtual machine Impossible to add virtual machine
2022-09-22 08:48:50 Jerzy Husakowski maas: status Triaged Incomplete
2022-09-22 08:48:50 Jerzy Husakowski maas: milestone 3.4.0
2023-01-03 10:51:16 Alberto Donato maas: status Incomplete New
2023-01-03 10:51:18 Alberto Donato maas: status New Incomplete
2023-02-28 12:26:21 Alexander Litvinov attachment added regiond.log https://bugs.launchpad.net/maas/+bug/1973804/+attachment/5650450/+files/regiond.log
2023-02-28 12:26:46 Alexander Litvinov attachment added rackd.log https://bugs.launchpad.net/maas/+bug/1973804/+attachment/5650451/+files/rackd.log
2023-02-28 12:26:50 Alexander Litvinov maas: status Incomplete New
2023-03-02 14:44:59 Bill Wear maas: status New Triaged
2023-03-20 17:55:45 Jeff McConnell bug added subscriber Jeff McConnell
2023-05-17 13:57:13 Gregory Orange bug added subscriber Pawsey Supercomputing Centre
2023-05-17 15:40:48 Gregory Orange attachment added Screenshot from 2023-05-17 11-43-03.png https://bugs.launchpad.net/maas/+bug/1973804/+attachment/5673582/+files/Screenshot%20from%202023-05-17%2011-43-03.png
2023-06-29 08:33:58 Alberto Donato maas: milestone 3.4.0 3.4.x
2024-03-05 14:55:07 Anton Troyanov maas: milestone 3.4.x 3.5.x
2024-03-14 08:00:19 Anton Troyanov nominated for series maas/3.4
2024-03-14 08:00:19 Anton Troyanov bug task added maas/3.4
2024-03-14 08:00:22 Anton Troyanov maas/3.4: status New Won't Fix
2024-03-14 08:00:24 Anton Troyanov maas/3.4: importance Undecided Medium