[Bug 1258304] Re: lxc-create fails on IPv6 address
Not sure if this is clear to everyone else so as a hint (I haven't looked at the code for lxc) the IPv6 address shown gives a pretty good indication that something is parsing an IPv6 address and then representing the first 32 bits as an IPv4 address. The specified ip address is 2607:f088:... which we then split up into bytes: 26 07 f0 88 and then represent as base 10: root@cps3:~/lxc# printf %d.%d.%d.%d\n 0x26 0x07 0xf0 0x88 38.7.240.136 anything that looks like address=ip is probably suspect. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1258304 Title: lxc-create fails on IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1258304/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1258304] Re: lxc-create fails on IPv6 address
Not sure if this is clear to everyone else so as a hint (I haven't looked at the code for lxc) the IPv6 address shown gives a pretty good indication that something is parsing an IPv6 address and then representing the first 32 bits as an IPv4 address. The specified ip address is 2607:f088:... which we then split up into bytes: 26 07 f0 88 and then represent as base 10: root@cps3:~/lxc# printf %d.%d.%d.%d\n 0x26 0x07 0xf0 0x88 38.7.240.136 anything that looks like address=ip is probably suspect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1258304 Title: lxc-create fails on IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1258304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1258304] [NEW] lxc-create fails on IPv6 address
Public bug reported:
root@cps3:~/lxc# cat horizon-cps3.net.conf
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br18
lxc.network.name = eth0
lxc.network.hwaddr = 00:16:3e:00:02:70
lxc.network.ipv6 = 2607:f088:0:12::39
lxc.network.mtu = 9000
root@cps3:~/lxc# lxc-create -n horizon-cps3 -f horizon-cps3.net.conf -t ubuntu
-B none
lxc-create: Failed to create backing store type none
lxc-create: Error creating backing store type none for horizon-cps3
lxc-create: Error creating container horizon-cps3
root@cps3:~/lxc# lxc-create -n horizon-cps3 -f horizon-cps3.net.conf -t ubuntu
lxc-create: No such file or directory - invalid ipv6 address: 38.7.240.136
lxc-create: Error creating container horizon-cps3
The same template (different IP/mac) worked on raring.
root@cps3:~/lxc# dpkg -l lxc | awk '/lxc/ {print $3}'
1.0.0~alpha1-0ubuntu14
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1258304
Title:
lxc-create fails on IPv6 address
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1258304/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1258304] Re: lxc-create fails on IPv6 address
Sure thing, by start I assume you mean create since there is nothing created yet. There are only three lines in the debug output, I'll just paste it here: root@cps3:~/lxc# lxc-create -n horizon-cps3 -f horizon-cps3.net.conf -t ubuntu -l debug -o debug lxc-create: No such file or directory - invalid ipv6 address: 38.7.240.136 lxc-create: Error creating container horizon-cps3 root@cps3:~/lxc# cat debug lxc-create 1386289012.783 WARN lxc_log - lxc_log_init called with log already initialized lxc-create 1386289012.784 ERRORlxc_confile - No such file or directory - invalid ipv6 address: 38.7.240.136 lxc-create 1386289012.785 ERRORlxc_create - Error creating container horizon-cps3 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1258304 Title: lxc-create fails on IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1258304/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1258304] [NEW] lxc-create fails on IPv6 address
Public bug reported:
root@cps3:~/lxc# cat horizon-cps3.net.conf
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br18
lxc.network.name = eth0
lxc.network.hwaddr = 00:16:3e:00:02:70
lxc.network.ipv6 = 2607:f088:0:12::39
lxc.network.mtu = 9000
root@cps3:~/lxc# lxc-create -n horizon-cps3 -f horizon-cps3.net.conf -t ubuntu
-B none
lxc-create: Failed to create backing store type none
lxc-create: Error creating backing store type none for horizon-cps3
lxc-create: Error creating container horizon-cps3
root@cps3:~/lxc# lxc-create -n horizon-cps3 -f horizon-cps3.net.conf -t ubuntu
lxc-create: No such file or directory - invalid ipv6 address: 38.7.240.136
lxc-create: Error creating container horizon-cps3
The same template (different IP/mac) worked on raring.
root@cps3:~/lxc# dpkg -l lxc | awk '/lxc/ {print $3}'
1.0.0~alpha1-0ubuntu14
** 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/1258304
Title:
lxc-create fails on IPv6 address
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1258304/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1258304] Re: lxc-create fails on IPv6 address
Sure thing, by start I assume you mean create since there is nothing created yet. There are only three lines in the debug output, I'll just paste it here: root@cps3:~/lxc# lxc-create -n horizon-cps3 -f horizon-cps3.net.conf -t ubuntu -l debug -o debug lxc-create: No such file or directory - invalid ipv6 address: 38.7.240.136 lxc-create: Error creating container horizon-cps3 root@cps3:~/lxc# cat debug lxc-create 1386289012.783 WARN lxc_log - lxc_log_init called with log already initialized lxc-create 1386289012.784 ERRORlxc_confile - No such file or directory - invalid ipv6 address: 38.7.240.136 lxc-create 1386289012.785 ERRORlxc_create - Error creating container horizon-cps3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1258304 Title: lxc-create fails on IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1258304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251352] Re: lxc fails to start on boot but succeeds with a manual boot
Hello Stéphane, I downloaded the packages manually, rebooted the node and the lxc containers seem to have started nominally. Thanks for the info! Serge, Thanks again for the quick fix! Cheers, -Tim ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1251352 Title: lxc fails to start on boot but succeeds with a manual boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1251352/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1251352] Re: lxc fails to start on boot but succeeds with a manual boot
Hello Stéphane, I downloaded the packages manually, rebooted the node and the lxc containers seem to have started nominally. Thanks for the info! Serge, Thanks again for the quick fix! Cheers, -Tim ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251352 Title: lxc fails to start on boot but succeeds with a manual boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1251352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251352] Re: lxc fails to start on boot but succeeds with a manual boot
Thanks for the quick fix! Unfortunately, something else broke when I pulled that package from the trusty repository. The lxc instance is started but nothing runs. Starting it manually vs on boot produces the same behavior and I only see these two lines when I start manually: 4init: console-setup main process (46) terminated with status 1 30systemd-udevd[58]: starting version 204 Furthermore, there are only two processes running, rsyslogd and (after a painful dist-upgrade inside the lxc root) systemd-udevd. Rolling back to 1.0.0~alpha1-0ubuntu13 allows me to start the instance again (albeit manually). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1251352 Title: lxc fails to start on boot but succeeds with a manual boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1251352/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1251352] Re: lxc fails to start on boot but succeeds with a manual boot
Thanks for the quick fix! Unfortunately, something else broke when I pulled that package from the trusty repository. The lxc instance is started but nothing runs. Starting it manually vs on boot produces the same behavior and I only see these two lines when I start manually: 4init: console-setup main process (46) terminated with status 1 30systemd-udevd[58]: starting version 204 Furthermore, there are only two processes running, rsyslogd and (after a painful dist-upgrade inside the lxc root) systemd-udevd. Rolling back to 1.0.0~alpha1-0ubuntu13 allows me to start the instance again (albeit manually). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251352 Title: lxc fails to start on boot but succeeds with a manual boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1251352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251352] [NEW] lxc fails to start on boot but succeeds with a manual boot
Public bug reported:
root@cps2-c1:/var/log/upstart# cat lxc.log
lxc-instance (os-api-cps2) start/running, process 2880
root@cps2-c1:/var/log/upstart# tail -f lxc-instance-os-api-cps2.log
lxc-start: failed to rename veth3ITMNG-eth0 : File exists
lxc-start: failed to setup netdev
lxc-start: failed to setup the network for 'os-api-cps2'
lxc-start: failed to setup the container
lxc-start: invalid sequence number 1. expected 2
lxc-start: failed to spawn 'os-api-cps2'
root@cps2-c1:/var/log/upstart# cat network-interface-veth3ITMNG.log
ifdown: interface veth3ITMNG not configured
root@cps2-c1:/var/log/upstart# cat /etc/lxc/auto/os-api-cps2
# Template used to create this container: ubuntu
# Template script checksum (SHA-1): 6f468a9a658112f6420fb39d2ab90a80fd43cd22
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br18
lxc.network.name = eth0
lxc.network.hwaddr = 00:16:3e:00:02:68
lxc.network.ipv6 = **
lxc.network.mtu = 9000
lxc.rootfs = /var/lib/lxc/os-api-cps2/rootfs
lxc.mount = /var/lib/lxc/os-api-cps2/fstab
lxc.pivotdir = lxc_putold
lxc.devttydir = lxc
lxc.tty = 4
lxc.pts = 1024
lxc.utsname = os-api-cps2
lxc.arch = amd64
lxc.cap.drop = sys_module mac_admin mac_override
# When using LXC with apparmor, uncomment the next line to run unconfined:
#lxc.aa_profile = unconfined
lxc.cgroup.devices.deny = a
# Allow any mknod (but not using the node)
lxc.cgroup.devices.allow = c *:* m
lxc.cgroup.devices.allow = b *:* m
# /dev/null and zero
lxc.cgroup.devices.allow = c 1:3 rwm
lxc.cgroup.devices.allow = c 1:5 rwm
# consoles
lxc.cgroup.devices.allow = c 5:1 rwm
lxc.cgroup.devices.allow = c 5:0 rwm
#lxc.cgroup.devices.allow = c 4:0 rwm
#lxc.cgroup.devices.allow = c 4:1 rwm
# /dev/{,u}random
lxc.cgroup.devices.allow = c 1:9 rwm
lxc.cgroup.devices.allow = c 1:8 rwm
lxc.cgroup.devices.allow = c 136:* rwm
lxc.cgroup.devices.allow = c 5:2 rwm
# rtc
lxc.cgroup.devices.allow = c 254:0 rwm
#fuse
lxc.cgroup.devices.allow = c 10:229 rwm
#tun
lxc.cgroup.devices.allow = c 10:200 rwm
#full
lxc.cgroup.devices.allow = c 1:7 rwm
#hpet
lxc.cgroup.devices.allow = c 10:228 rwm
#kvm
lxc.cgroup.devices.allow = c 10:232 rwm
Running service lxc restart results in the same errors.
Running lxc-start -d -n os-api-cps2 from the command line successfully
starts the instance.
root@cps2-c1:/var/log/upstart# dpkg -l | grep lxc
ii liblxc0 1.0.0~alpha1-0ubuntu13 amd64
Linux Containers userspace tools (library)
ii lxc 1.0.0~alpha1-0ubuntu13 amd64
Linux Containers userspace tools
ii lxc-templates 1.0.0~alpha1-0ubuntu13 all
Linux Containers userspace tools (templates)
ii lxctl 0.3.1+debian-3 all
Utility to manage LXC
ii python3-lxc 1.0.0~alpha1-0ubuntu13 amd64
Linux Containers userspace tools (Python 3.x bindings)
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1251352
Title:
lxc fails to start on boot but succeeds with a manual boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1251352/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1251352] [NEW] lxc fails to start on boot but succeeds with a manual boot
Public bug reported:
root@cps2-c1:/var/log/upstart# cat lxc.log
lxc-instance (os-api-cps2) start/running, process 2880
root@cps2-c1:/var/log/upstart# tail -f lxc-instance-os-api-cps2.log
lxc-start: failed to rename veth3ITMNG-eth0 : File exists
lxc-start: failed to setup netdev
lxc-start: failed to setup the network for 'os-api-cps2'
lxc-start: failed to setup the container
lxc-start: invalid sequence number 1. expected 2
lxc-start: failed to spawn 'os-api-cps2'
root@cps2-c1:/var/log/upstart# cat network-interface-veth3ITMNG.log
ifdown: interface veth3ITMNG not configured
root@cps2-c1:/var/log/upstart# cat /etc/lxc/auto/os-api-cps2
# Template used to create this container: ubuntu
# Template script checksum (SHA-1): 6f468a9a658112f6420fb39d2ab90a80fd43cd22
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br18
lxc.network.name = eth0
lxc.network.hwaddr = 00:16:3e:00:02:68
lxc.network.ipv6 = **
lxc.network.mtu = 9000
lxc.rootfs = /var/lib/lxc/os-api-cps2/rootfs
lxc.mount = /var/lib/lxc/os-api-cps2/fstab
lxc.pivotdir = lxc_putold
lxc.devttydir = lxc
lxc.tty = 4
lxc.pts = 1024
lxc.utsname = os-api-cps2
lxc.arch = amd64
lxc.cap.drop = sys_module mac_admin mac_override
# When using LXC with apparmor, uncomment the next line to run unconfined:
#lxc.aa_profile = unconfined
lxc.cgroup.devices.deny = a
# Allow any mknod (but not using the node)
lxc.cgroup.devices.allow = c *:* m
lxc.cgroup.devices.allow = b *:* m
# /dev/null and zero
lxc.cgroup.devices.allow = c 1:3 rwm
lxc.cgroup.devices.allow = c 1:5 rwm
# consoles
lxc.cgroup.devices.allow = c 5:1 rwm
lxc.cgroup.devices.allow = c 5:0 rwm
#lxc.cgroup.devices.allow = c 4:0 rwm
#lxc.cgroup.devices.allow = c 4:1 rwm
# /dev/{,u}random
lxc.cgroup.devices.allow = c 1:9 rwm
lxc.cgroup.devices.allow = c 1:8 rwm
lxc.cgroup.devices.allow = c 136:* rwm
lxc.cgroup.devices.allow = c 5:2 rwm
# rtc
lxc.cgroup.devices.allow = c 254:0 rwm
#fuse
lxc.cgroup.devices.allow = c 10:229 rwm
#tun
lxc.cgroup.devices.allow = c 10:200 rwm
#full
lxc.cgroup.devices.allow = c 1:7 rwm
#hpet
lxc.cgroup.devices.allow = c 10:228 rwm
#kvm
lxc.cgroup.devices.allow = c 10:232 rwm
Running service lxc restart results in the same errors.
Running lxc-start -d -n os-api-cps2 from the command line successfully
starts the instance.
root@cps2-c1:/var/log/upstart# dpkg -l | grep lxc
ii liblxc0 1.0.0~alpha1-0ubuntu13 amd64
Linux Containers userspace tools (library)
ii lxc 1.0.0~alpha1-0ubuntu13 amd64
Linux Containers userspace tools
ii lxc-templates 1.0.0~alpha1-0ubuntu13 all
Linux Containers userspace tools (templates)
ii lxctl 0.3.1+debian-3 all
Utility to manage LXC
ii python3-lxc 1.0.0~alpha1-0ubuntu13 amd64
Linux Containers userspace tools (Python 3.x bindings)
** 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/1251352
Title:
lxc fails to start on boot but succeeds with a manual boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1251352/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189909] Re: dhcp-agent does always provide IP address for instances with re-cycled IP addresses.
Possibly a new vector, I have IPv6 as well as IPv4 on a network. I see this segment of the (rather large) host file: fa:16:3e:9d:de:21,host-192-168-2-103.openstacklocal,192.168.2.103 fa:16:3e:9d:de:21,host-2607-f088-0-2--1339.openstacklocal,2607:f088:0:2::1339 When I remove the second line, and kill -HUP the daemon, IPv4 starts working. I tried running kill -HUP without removing the line and did not get a response. Hopefully, whatever the problem is will be considered and fixed for both IPv4 and IPv6. I am running dnsmasq from ubuntu packages: 2.66-4ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189909 Title: dhcp-agent does always provide IP address for instances with re-cycled IP addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1189909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170801] [NEW] puppet needs to use ruby1.8
Public bug reported: On a new raring install I have added puppet (which brings in facter) but puppet won't start: # service puppet restart * Restarting puppet agent /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- facter (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/puppet.rb:9:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/puppet/application.rb:272:in `initialize' from /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:60:in `new' from /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:60:in `execute' from /usr/bin/puppet:4:in `main' Looking at facter, it is apparent that it is only available under ruby1.8: % dpkg-query -L facter | grep -c ruby/1.8 83 % dpkg-query -L facter | grep -c ruby/1.9 0 However, /usr/bin/puppet is set to use ruby-1.9.1. Manually changing it to use ruby1.8 allows puppet to start. Additionally, puppet (3.x) is known to only run on ruby 1.9.x. # lsb_release -rd Description:Ubuntu Raring Ringtail (development branch) Release:13.04 # apt-cache policy puppet facter ruby ruby1.8 ruby1.9.1 puppet: Installed: 2.7.18-4ubuntu1 Candidate: 2.7.18-4ubuntu1 Version table: *** 2.7.18-4ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status facter: Installed: 1.6.9-2ubuntu1 Candidate: 1.6.9-2ubuntu1 Version table: *** 1.6.9-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ruby: Installed: 4.9 Candidate: 4.9 Version table: *** 4.9 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ruby1.8: Installed: 1.8.7.358-7ubuntu1 Candidate: 1.8.7.358-7ubuntu1 Version table: *** 1.8.7.358-7ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ruby1.9.1: Installed: 1.9.3.194-8.1ubuntu1 Candidate: 1.9.3.194-8.1ubuntu1 Version table: *** 1.9.3.194-8.1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: puppet (Ubuntu) Importance: Undecided Status: Invalid ** Changed in: puppet (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1170801 Title: puppet needs to use ruby1.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1170801/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1170801] Re: puppet needs to use ruby1.8
Sorry, I realized a few seconds after this went through that puppet was broken by something else in my own environment. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1170801 Title: puppet needs to use ruby1.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1170801/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1170801] [NEW] puppet needs to use ruby1.8
Public bug reported: On a new raring install I have added puppet (which brings in facter) but puppet won't start: # service puppet restart * Restarting puppet agent /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- facter (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/puppet.rb:9:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/puppet/application.rb:272:in `initialize' from /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:60:in `new' from /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:60:in `execute' from /usr/bin/puppet:4:in `main' Looking at facter, it is apparent that it is only available under ruby1.8: % dpkg-query -L facter | grep -c ruby/1.8 83 % dpkg-query -L facter | grep -c ruby/1.9 0 However, /usr/bin/puppet is set to use ruby-1.9.1. Manually changing it to use ruby1.8 allows puppet to start. Additionally, puppet (3.x) is known to only run on ruby 1.9.x. # lsb_release -rd Description:Ubuntu Raring Ringtail (development branch) Release:13.04 # apt-cache policy puppet facter ruby ruby1.8 ruby1.9.1 puppet: Installed: 2.7.18-4ubuntu1 Candidate: 2.7.18-4ubuntu1 Version table: *** 2.7.18-4ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status facter: Installed: 1.6.9-2ubuntu1 Candidate: 1.6.9-2ubuntu1 Version table: *** 1.6.9-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ruby: Installed: 4.9 Candidate: 4.9 Version table: *** 4.9 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ruby1.8: Installed: 1.8.7.358-7ubuntu1 Candidate: 1.8.7.358-7ubuntu1 Version table: *** 1.8.7.358-7ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ruby1.9.1: Installed: 1.9.3.194-8.1ubuntu1 Candidate: 1.9.3.194-8.1ubuntu1 Version table: *** 1.9.3.194-8.1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: puppet (Ubuntu) Importance: Undecided Status: Invalid ** Changed in: puppet (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170801 Title: puppet needs to use ruby1.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1170801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170801] Re: puppet needs to use ruby1.8
Sorry, I realized a few seconds after this went through that puppet was broken by something else in my own environment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170801 Title: puppet needs to use ruby1.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1170801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1125540] Re: openbios-sparc64 missing
Thanks Serge, I tried loading a sparc64 class machine before loading your package with the Debian package still installed and got to the OpenBIOS screen. After I installed it, the same qemu-system-sparc64 invocation just remained a dark black screen. The qemu-system-sparc binary seems to get me to the OpenBIOS screen appropriately though. I tested with qemu version 1.1.2+dfsg-2 and 1.4.0+dfsg-1expubuntu4 with the same results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1125540 Title: openbios-sparc64 missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1125540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1125540] [NEW] openbios-sparc64 missing
Public bug reported: It appears that a broken symlink is shipped instead of the actual openbios image: $ qemu-system-sparc64 phobos.raw qemu: could not load prom 'openbios-sparc64' $ dpkg-query -S openbios-sparc64 qemu-system-sparc: /usr/share/qemu/openbios-sparc64 $ ls -la /usr/share/qemu/openbios-sparc64 lrwxrwxrwx 1 root root 28 Feb 12 22:11 /usr/share/qemu/openbios-sparc64 - ../openbios/openbios-sparc64 $ ls -la /usr/share/openbios ls: cannot access /usr/share/openbios: No such file or directory $ apt-cache policy qemu-system-sparc qemu-system-sparc: Installed: 1.3.0+dfsg-5expubuntu2 Candidate: 1.3.0+dfsg-5expubuntu2 Version table: *** 1.3.0+dfsg-5expubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status $ lsb_release -rd Description:Ubuntu Raring Ringtail (development branch) Release:13.04 ** Affects: qemu (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/1125540 Title: openbios-sparc64 missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1125540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1125540] Re: openbios-sparc64 missing
I should also add that under Debian there is an openbios-sparc package
which contains the actual openbios image:
$ ls -la /usr/share/{qemu,openbios}/openbios-sparc64
-rw-r--r-- 1 root root 737264 Jun 9 2012 /usr/share/openbios/openbios-sparc64
lrwxrwxrwx 1 root root 28 Jan 14 03:37 /usr/share/qemu/openbios-sparc64 -
../openbios/openbios-sparc64
$ dpkg-query -S openbios-sparc64
openbios-sparc: /usr/share/openbios/openbios-sparc64
qemu-system: /usr/share/qemu/openbios-sparc64
This may be a broken dependency as I don't find the same package under
Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1125540
Title:
openbios-sparc64 missing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1125540/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1125540] Re: openbios-sparc64 missing
Aha, interesting. In fact, it would seem that you need cross-compilers in any case since there are no sparc64 buildd nodes, if I am understanding this correctly. ie: under Debian, fixing either one might work but under Ubuntu, cross compiling is the only real solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1125540 Title: openbios-sparc64 missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1125540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
