[Bug 1699919] Re: lxc copy between hosts preserves original uid/gid
The thing is - it didn't get remapped. Now I have two containers mapping
to the same range, both live:
pshemk@ii:~$ lxc list
+-+-+-+--++---+
| NAME | STATE |IPV4 | IPV6 |TYPE| SNAPSHOTS |
+-+-+-+--++---+
| backend | RUNNING | 10.221.22.92 (eth0) | | PERSISTENT | 0 |
+-+-+-+--++---+
| putils | RUNNING | 10.221.22.91 (eth0) | | PERSISTENT | 1 |
+-+-+-+--++---+
pshemk@ii:~$ lxc config show putils
architecture: x86_64
config:
volatile.base_image:
8fa08537ae51c880966626561987153e72d073cbe19dfe5abc062713d929254d
volatile.eth0.hwaddr: 00:16:3e:e3:20:21
volatile.idmap.base: "0"
volatile.idmap.next:
'[{"Isuid":true,"Isgid":false,"Hostid":10,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":10,"Nsid":0,"Maprange":65536}]'
volatile.last_state.idmap:
'[{"Isuid":true,"Isgid":false,"Hostid":10,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":10,"Nsid":0,"Maprange":65536}]'
volatile.last_state.power: RUNNING
devices:
root:
path: /
type: disk
ephemeral: false
profiles:
- default
stateful: false
pshemk@ii:~$ lxc config show backend
architecture: x86_64
config:
volatile.base_image:
7a7ff654cbd8f5f09bec03aa19d8d7d92649127d18659036a963b1ea63f90d25
volatile.eth0.hwaddr: 00:16:3e:ec:03:84
volatile.idmap.base: "0"
volatile.idmap.next:
'[{"Isuid":true,"Isgid":false,"Hostid":10,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":10,"Nsid":0,"Maprange":65536}]'
volatile.last_state.idmap:
'[{"Isuid":true,"Isgid":false,"Hostid":10,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":10,"Nsid":0,"Maprange":65536}]'
volatile.last_state.power: RUNNING
devices:
root:
path: /
type: disk
ephemeral: false
profiles:
- default
stateful: false
both have the same hostid, and get mapped to the same range.
Should the files on the file system belong to the same uid:gid for 2
different containers?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699919
Title:
lxc copy between hosts preserves original uid/gid
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1699919/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699919] [NEW] lxc copy between hosts preserves original uid/gid
Public bug reported: I tried to copy an lxc container between two hosts. All worked as expected, but when I looked at the underlying filesystem I realised that the container that has been copied onto the new machine retained its original uid/gid (running unprivileged): root@ii:/var/lib/lxd/containers# ls -al total 24 drwx--x--x 1 root root 58 Jun 23 12:01 . drwxr-xr-x 1 root root182 Jun 23 12:04 .. drwxr-xr-x+ 1 10 10 56 Jun 23 10:38 backend -rw-r--r-- 1 root root 4446 Jun 23 12:04 lxc-monitord.log drwxr-xr-x+ 1 10 10 56 Jun 23 12:01 putils (putils has been copied from a different host). I'd expect a new uid/gid to be allocated for the copied host. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699919 Title: lxc copy between hosts preserves original uid/gid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1699919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640350] [NEW] missing depedency liboping0
Public bug reported:
It looks like the package (collected-core) is missing a depedency on
liboping0. That results in ping plugin not loading:
# /usr/sbin/collectd -tT
lt_dlopen ("/usr/lib/collectd/ping.so") failed: file not found. The most common
cause for this problem is missing dependencies. Use ldd(1) to check the
dependencies of the plugin / shared object.
plugin_load: Load plugin "ping" failed with status 1.
Found a configuration for the `ping' plugin, but the plugin isn't loaded or
didn't register a configuration callback.
# ldd /usr/lib/collectd/ping.so
linux-vdso.so.1 => (0x7ffeab82b000)
liboping.so.0 => not found
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f52330f3000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f5232d2c000)
/lib64/ld-linux-x86-64.so.2 (0x559918b5)
after installation of liboping0
# ldd /usr/lib/collectd/ping.so
linux-vdso.so.1 => (0x7ffcfe041000)
liboping.so.0 => /usr/lib/x86_64-linux-gnu/liboping.so.0
(0x7fe45f005000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fe45ecfc000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fe45e935000)
/lib64/ld-linux-x86-64.so.2 (0x55c4dad7f000)
details:
Description:Ubuntu 16.10
Release:16.10
# dpkg -l | grep collectd-core
ii collectd-core 5.5.2-1
amd64statistics collection and monitoring daemon (core system)
** Affects: collectd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640350
Title:
missing depedency liboping0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1640350/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403955] Re: DHCP's "Option interface-mtu 9000" is being ignored on bridge interface br0
The bug is still present in 1.25. The fact that it only manifests itself during the subsequent machine reboots (and not during the initial build) makes it more difficult to troubleshoot - services that worked before reboot do not work after. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1403955 Title: DHCP's "Option interface-mtu 9000" is being ignored on bridge interface br0 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1403955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1513676] [NEW] vxlan tunneling not working correctly
Public bug reported: I have an openstack setup with dedicated network node (using neutron- gateway charm) and a compute-only node (nova-compute charm). With this configuration: nova-cloud-controller: openstack-origin: cloud:trusty-liberty network-manager: Neutron neutron-external-network: "ext-net" console-access-protocol: vnc neutron-api: openstack-origin: cloud:trusty-liberty neutron-external-network: "ext-net" neutron-security-groups: true overlay-network-type: vxlan network-device-mtu: 9000 neutron-gateway: openstack-origin: cloud:trusty-liberty ext-port: eth1 neutron-openvswitch: # enable-local-dhcp-and-metadata: true nova-compute: openstack-origin: cloud:trusty-liberty the ml2_conf.ini on the network node ends up with: [ml2] type_drivers = gre,vxlan,vlan,flat tenant_network_types = gre,vxlan,vlan,flat mechanism_drivers = openvswitch,hyperv,l2population [ml2_type_gre] tunnel_id_ranges = 1:1000 [ml2_type_vxlan] vni_ranges = 1001:2000 [ml2_type_vlan] network_vlan_ranges = physnet1:1000:2000 [ml2_type_flat] flat_networks = [ovs] enable_tunneling = True local_ip = 10.0.0.2 bridge_mappings = physnet1:br-data [agent] tunnel_types = vxlan l2_population = True enable_distributed_routing = False veth_mtu = 9000 [securitygroup] firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver whilst the compute node has: # icehouse ### # [ WARNING ] # Configuration file maintained by Juju. Local changes may be overwritten. ### [ml2] type_drivers = gre,vxlan tenant_network_types = gre,vxlan mechanism_drivers = openvswitch [ml2_type_gre] tunnel_id_ranges = 1:1000 [ml2_type_vxlan] vni_ranges = 1001:2000 [ovs] enable_tunneling = True local_ip = 10.0.0.3 [agent] tunnel_types = gre [securitygroup] enable_security_group = True firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver Which results in inability to spin up any machines (they try to use vxlan which is not available on the compute node). ** Affects: neutron-gateway (Juju Charms Collection) Importance: Undecided Status: New ** Affects: nova-compute (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: nova (Ubuntu) Importance: Undecided Status: New ** Package changed: nova (Ubuntu) => nova-compute (Juju Charms Collection) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1513676 Title: vxlan tunneling not working correctly To manage notifications about this bug go to: https://bugs.launchpad.net/charms/+source/neutron-gateway/+bug/1513676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
