April 2016 - Dev - lists.clearlinux.org

[Dev] swupd bundle remover does not manage dependencies (rev. 7770 and 7820)

by fb.dev.clx

Hi all, swupd seems to remove `kernel-kvm` which was previously automagically installed as a dependency of the `kvm-host` bundle: ``` $ sudo swupd bundle-remove kernel-kvm swupd-client bundle remover 3.5.3 Copyright (C) 2012-2016 Intel Corporation Deleting bundle files... Total deleted files: 5 Untracking bundle from system... Success: Bundle removed ``` and so `kernel-kvm` is not present anymore in the list of installed bundles: ``` $ ls -1 /usr/share/clear/bundles/kernel-kvm ls: cannot access '/usr/share/clear/bundles/kernel-kvm': No such file or directory ``` But, as `kernel-kvm` was installed as a dependency of `kvm-host`, it would be better if it could not be uninstalled while `kvm-host` is still present on the system. Fortunately, `swupd verify --fix` corrects the situation and reinstalls the dependency, so `kernel-kvm` is back again on the system: ``` $ sudo swupd verify --fix [...] $ ls -1 /usr/share/clear/bundles/kernel-kvm /usr/share/clear/bundles/kernel-kvm ``` Regards, -- FB

7 years

2
1
0 0

[Dev] sudoers rights lost when removing kvm-host bundle (rev. 7770)

by fb.dev.clx

Hi all, While removing `kvm-host` and `kernel-kvm` bundles on a bare metal Clear Linux rev. 7160 install upgraded to rev. 7770, I was stuck as a standard user without any option since removing `kvm-host` put me out of the sudoers file. Here are the steps done: At first, ``` $ sudo swupd bundle-remove kvm-host kernel-kvm swupd-client bundle remover 3.5.2 Copyright (c) 2012-2016 Intel Corporation Deleting bundle files... Total deleted files: 230 Untracking bundle from system... Success: Bundle removed ``` Then, ``` sudo swupd verify --fix We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things: #1) Respect the privacy of the others. #2) Think before you type #3) With great power comes great responsibility. Password: clruser is not in the sudoers file. This incident will be reported. ``` After a reboot (log out and then log in again was not sufficient), the system was able to read correctly `/etc/sudoers.d/clruser` in order to behave again as if the standard user originally created at install time was in the sudoers file. This bug is reproducible. -------------------- NOTE: on Sat, 02 Apr 2016, I wrote to the list as swupd verify wanted to delete sudoers.d after adding kvm-host bundle on a new bare metal install (rev. 7160). Maybe there is a relation? -------------------- -- FB

7 years

2
1
0 0

[Dev] swupd bundle remover only manage one bundle at a time (rev. 7770 and 7820)

by fb.dev.clx

Hi all, swupd bundle-remover seems to only manage one bundle at a time but one can pass several bundles to be removed without any warning: ``` # swupd bundle-remove kvm-host kernel-kvm swupd-client bundle remover 3.5.3 Copyright (C) 2012-2016 Intel Corporation Deleting bundle files... Total deleted files: 230 Untracking bundle from system... Success: Bundle removed ``` `kvm-host` bundle was removed, but `kernel-kvm` is still present in the list of installed bundles: ``` $ ls -1 /usr/share/clear/bundles/kernel-kvm /usr/share/clear/bundles/ker nel-kvm ``` Regards, -- FB

7 years

2
1
0 0

Re: [Dev] swupd verify intent to fix missing kernel 4.5.1-159 related files

by fb.dev.clx

Thank you very much Brad for your attention. I'll take the time to test your work-around with a version in which the problem occured and will let you know if that works... but I would certainly prefer a working solution out of the box for this! -- FB On Fri, 2016-04-29 at 20:02 +0000, Peters, Brad T wrote: > It seems pretty likely. > > A work-around you can use to trick CSU into installing the kvm kernel > for you is as follows: > > cd to /usr/lib/kernel > > rm one of the older org.clearlinux.native older kernels > > run 'swupd verify --fix' > > When done you should be able to 'systemctl start boot.mount', ls > /boot, and > see the kvm kernel > > You will have to manually configure that kernel to boot, however, > since CSU is > still going to see newer kernels, which it will think should be > booted > > Enjoy and let me know if that works or not > > Best, > -Brad > > On Fri, Apr 29, 2016 at 7:18 PM, fb.dev.clx <fb.dev.clx(a)gmail.com> > wrote: > > ... could it be the source of the 'virsh cannot find suitable > > emulator > > for x86_64' thing I've encountered many times before? > > > > -- FB > > > > > > On Fri, 2016-04-29 at 17:59 +0000, Peters, Brad T wrote: > > > Here's the problem - You are attempting to install two different > > > kernel types (3 native and 1 kvm); > > > the clr-specialized-updaters (CSU) kernel_updater script was > > codded > > > assuming only 1 kernel type would > > > ever be installed per system. So if you look at your ls output, > > the 3 > > > native kernels (releases 193, 200 and 201) > > > are getting installed, while the kvm kernel (at release 159) is > > > considered older than the other three, > > > and is cleaned up rather than installed. > > > > > > This is an interesting edge case, and since installing different > > > kernel types is indeed something we want to > > > support, we'll look at patching CSU to treat different kernel > > types > > > independently. > > > > > > Thanks for bringing this to our attention > > > > > > Best, > > > -Brad Peters > > > > > > On Fri, Apr 29, 2016 at 9:38 AM, Douglas, William <william.dougla > > s(a)in > > > tel.com> wrote: > > > > On Fri, Apr 29, 2016 at 9:29 AM, fb.dev.clx <fb.dev.clx(a)gmail.c > > om> > > > > wrote: > > > > > Hi all, > > > > > > > > > > Since at least releases 7730 and 7770, `swupd verify --fix` > > > > command > > > > > intents to fix missing kernel 4.5.1-159 related files. > > > > > Each time the command is run, a "Fix successful" message is > > > > displayed > > > > > at the end, but without any real change: > > > > > > > > > > ``` > > > > > $ ls -d /usr/lib/modules/4.5.1-159/ > > > > > ls: cannot access '/usr/lib/modules/4.5.1-159/': No such file > > or > > > > > directory > > > > > ``` > > > > > > > > So it sounds like the kernel update scripts are detecting > > 4.5.1-159 > > > > somehow (something sitting in /boot probably) and attempting to > > > > restore files in /boot but since you don't have the files (in > > > > /usr/lib/kernel btw is where these are pulled from) it doesn't > > > > succeed. > > > > > > > > We could possibly have something going wrong with > > detection/cleanup > > > > here though Brad would know best. > > > > > > > > > > > > > > Can anyone check this? > > > > > > > > > > -- FB > > > > > _______________________________________________ > > > > > Dev mailing list > > > > > Dev(a)lists.clearlinux.org > > > > > https://lists.clearlinux.org/mailman/listinfo/dev > > > > > >

7 years

2
3
0 0

Re: [Dev] swupd verify intent to fix missing kernel 4.5.1-159 related files

by fb.dev.clx

Please, find attached the result of the following commands for Clear Linux 7770: ``` $ ls -lR /boot $ sudo swupd verify --fix ``` -- FB On Fri, 2016-04-29 at 09:38 -0700, Douglas, William wrote: > On Fri, Apr 29, 2016 at 9:29 AM, fb.dev.clx <fb.dev.clx(a)gmail.com> > wrote: > > > > Hi all, > > > > Since at least releases 7730 and 7770, `swupd verify --fix` command > > intents to fix missing kernel 4.5.1-159 related files. > > Each time the command is run, a "Fix successful" message is > > displayed > > at the end, but without any real change: > > > > ``` > > $ ls -d /usr/lib/modules/4.5.1-159/ > > ls: cannot access '/usr/lib/modules/4.5.1-159/': No such file or > > directory > > ``` > So it sounds like the kernel update scripts are detecting 4.5.1-159 > somehow (something sitting in /boot probably) and attempting to > restore files in /boot but since you don't have the files (in > /usr/lib/kernel btw is where these are pulled from) it doesn't > succeed. > > We could possibly have something going wrong with detection/cleanup > here though Brad would know best. > > > > > > > Can anyone check this? > > > > -- FB > > _______________________________________________ > > Dev mailing list > > Dev(a)lists.clearlinux.org > > https://lists.clearlinux.org/mailman/listinfo/dev

7 years

3
3
0 0

Re: [Dev] swupd verify intent to fix missing kernel 4.5.1-159 related files

by fb.dev.clx

... could it be the source of the 'virsh cannot find suitable emulator for x86_64' thing I've encountered many times before? -- FB On Fri, 2016-04-29 at 17:59 +0000, Peters, Brad T wrote: > Here's the problem - You are attempting to install two different > kernel types (3 native and 1 kvm); > the clr-specialized-updaters (CSU) kernel_updater script was codded > assuming only 1 kernel type would > ever be installed per system. So if you look at your ls output, the 3 > native kernels (releases 193, 200 and 201) > are getting installed, while the kvm kernel (at release 159) is > considered older than the other three, > and is cleaned up rather than installed. > > This is an interesting edge case, and since installing different > kernel types is indeed something we want to > support, we'll look at patching CSU to treat different kernel types > independently. > > Thanks for bringing this to our attention > > Best, > -Brad Peters > > On Fri, Apr 29, 2016 at 9:38 AM, Douglas, William <william.douglas(a)in > tel.com> wrote: > > On Fri, Apr 29, 2016 at 9:29 AM, fb.dev.clx <fb.dev.clx(a)gmail.com> > > wrote: > > > Hi all, > > > > > > Since at least releases 7730 and 7770, `swupd verify --fix` > > command > > > intents to fix missing kernel 4.5.1-159 related files. > > > Each time the command is run, a "Fix successful" message is > > displayed > > > at the end, but without any real change: > > > > > > ``` > > > $ ls -d /usr/lib/modules/4.5.1-159/ > > > ls: cannot access '/usr/lib/modules/4.5.1-159/': No such file or > > > directory > > > ``` > > > > So it sounds like the kernel update scripts are detecting 4.5.1-159 > > somehow (something sitting in /boot probably) and attempting to > > restore files in /boot but since you don't have the files (in > > /usr/lib/kernel btw is where these are pulled from) it doesn't > > succeed. > > > > We could possibly have something going wrong with detection/cleanup > > here though Brad would know best. > > > > > > > > Can anyone check this? > > > > > > -- FB > > > _______________________________________________ > > > Dev mailing list > > > Dev(a)lists.clearlinux.org > > > https://lists.clearlinux.org/mailman/listinfo/dev > >

7 years

1
0
0 0

[Dev] swupd verify intent to fix missing kernel 4.5.1-159 related files

by fb.dev.clx

Hi all, Since at least releases 7730 and 7770, `swupd verify --fix` command intents to fix missing kernel 4.5.1-159 related files. Each time the command is run, a "Fix successful" message is displayed at the end, but without any real change: ``` $ ls -d /usr/lib/modules/4.5.1-159/ ls: cannot access '/usr/lib/modules/4.5.1-159/': No such file or directory ``` Can anyone check this? -- FB

7 years

2
1
0 0

[Dev] retiring tiff

by Arjan van de Ven

Hi, the "tiff" package has had YetAnother slew of CVEs, and really is now in the "more hole than cheese" category; it's not used much at all, and has a long string of security issues. Because of this we've started to remove tiff from the few places where it was used and we'll retire tiff from the OS. If anyone thinks that tiff is mission critical for them, let us know and we'll reconsider....

7 years

1
0
0 0

Re: [Dev] "virsh could not find capabilities for arch=x86_64"

by fb.dev.clx

Hi Andrew, Please find attached `virsh capabilities` output with Clear Linux 7050 and 7210 respectively. -- FB On Sun, 2016-04-24 at 09:39 -0400, Andrew Cathrow wrote: > what do you get if you run 'virsh capabilities' > > > On Sun, Apr 24, 2016 at 9:21 AM, fb.dev.clx <fb.dev.clx(a)gmail.com> > wrote: > > Hi all, > > > > Back from vacations, I intented to update Clear Linux from 7050 to > > latest 7210 but problem still remains. > > > > The workaround that works on your machine: > > ``` > > systemctl stop > > libvirtd.socket > > systemctl stop libvirtd.service > > systemctl start > > libvirtd.socket > > > > ``` > > > > ...doesn't work here: > > > > ``` > > $ sudo virsh version > > Compiled against library: libvirt 1.3.2 > > Using library: libvirt 1.3.2 > > Using API: QEMU 1.3.2 > > error: failed to get the hypervisor version > > error: internal error: Cannot find suitable emulator for x86_64 > > > > ``` > > > > Right now, I'm still stuck with 7050 latest working version on my > > computer. > > > > Anymore idea? > > > > -- FB > > > > > > On Sat, 2016-04-02 at 18:16 -0700, Arjan van de Ven wrote: > > > On 4/2/2016 5:42 PM, fb.dev.clx wrote: > > > > > > > > Hi all, > > > > > > > > I used `swupd verify --fix -m <version number>` (thank you > > Arjan) > > > > to > > > > determine the version from which the system has stopped working > > > > properly and found out that all went well till Clear Linux rev. > > > > 7050. > > > > > > > ok so I had issues getting virsh version to work, but when I did > > > > > > systemctl stop libvirtd.socket > > > systemctl stop libvirtd.service > > > systemctl start libvirtd.socket > > > > > > it works on my machine. > > > > > > > > _______________________________________________ > > Dev mailing list > > Dev(a)lists.clearlinux.org > > https://lists.clearlinux.org/mailman/listinfo/dev > >

7 years, 1 month

2
2
0 0

[Dev] "virsh could not find capabilities for arch=x86_64"

by fb.dev.clx

Hi all, After updating Clear Linux from 6970 to 7090, I was unable to start KVM VMs (without OpenStack) as virsh gave the following error message: "virsh could not find capabilities for arch=x86_64" I then decided to reinstall Clear Linux with latest (7090) installer but this doesn't solve the problem: $ sudo virsh define VM1000.xml error: Failed to define domain from VM1000.xml error: invalid argument: could not find capabilities for arch=x86_64 Bellow are a few commands with their output: $ cat /usr/share/clear/version 7090 $ sudo swupd check-update swupd-client software update checker 3.3.0 Copyright (C) 2012-2016 Intel Corporation Querying server version. Attempting to download version string to memory There are no updates available $ ls -1 /usr/share/clear/bundles kernel-native kvm-host os-core os-core-update os-utils os-utils-gui $ systemctl status libvirtd * libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; disabled; vendor preset: disabled) Active: active (running) since Thu 2016-03- 31 21:49:44 UTC; 6min ago Docs: man:libvirtd(8) http://li bvirt.org Main PID: 340 (libvirtd) CGroup: /system.slice/libvirtd.service `-340 /usr/bin/libvirtd Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. $ sudo virsh version Compiled against library: livirt 1.3.2 Using library: libvirt 1.3.2 Using API: QEMU 1.3.2 error: failed to get the hypervisor version error: internal error: Cannot find suitable emulator for x86_64 $ sudo virsh capabilities (Output available as an attachement: 'virsh-capabilities.txt') Any suggestions appreciated. -- FB

7 years, 1 month

5
22
0 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

Dev April 2016