Fedora 27 template #3783

marmarek · Apr 3, 2018

Tracking issue for fedora-27 template:

update builder-fedora to build proper src.rpm (needed because of changed rpm macros around debuginfo packages) - #1508
update all packages for above changes
build and upload fc27 packages
prepare and test fc26->fc27 upgrade path
build binary template

Are you planning for this template to be released at the same time as R4.1 (per the milestone assigned), or near to when f26 reaches EOL?

esote · Apr 6, 2018

Are you planning for this template to be released at the same time as R4.1 (per the milestone assigned), or near to when f26 reaches EOL?

Are you planning for this template to be released at the same time as R4.1 (per the milestone assigned), or near to when f26 reaches EOL?

We aim to release it before F26 reaches EOL. However, I don't yet know whether that will be before or after the release of 4.1.

andrewdavidwong · Apr 6, 2018

Are you planning for this template to be released at the same time as R4.1 (per the milestone assigned), or near to when f26 reaches EOL?

We aim to release it before F26 reaches EOL. However, I don't yet know whether that will be before or after the release of 4.1.

We aim to release it before F26 reaches EOL. However, I don't yet know whether that will be before or after the release of 4.1.

Fedora 28 GA release is 2018-05-08 (I am guessing there will be one week slip), means Fedora 26 will be EOL around 2018-06-08.

kushaldas · Apr 11, 2018

We aim to release it before F26 reaches EOL. However, I don't yet know whether that will be before or after the release of 4.1.

Fedora 28 GA release is 2018-05-08 (I am guessing there will be one week slip), means Fedora 26 will be EOL around 2018-06-08.

Fedora 28 was released today, which means that Fedora 26 will reach EOL on 2018-06-01. Therefore, I am upgrading the priority of this issue to critical.

andrewdavidwong · May 2, 2018

Fedora 28 was released today, which means that Fedora 26 will reach EOL on 2018-06-01. Therefore, I am upgrading the priority of this issue to critical.

Ideally, we would announce today that our Fedora 26 TemplateVMs will reach EOL in one month in order to give users plenty of time to upgrade or migrate to a new template (just as we do when Qubes versions reach EOL). However, since we do not have a new template to offer yet, I'm going to postpone that announcement until the information is actionable. We will also make an announcement on 2018-06-01 stating that Fedora 26 has reached EOL, as a final reminder to anyone who hasn't migrated yet that they should do so immediately.

Discussion thread: https://groups.google.com/d/topic/qubes-users/s0qQLzQ1aBw/discussion

andrewdavidwong · May 2, 2018

Ideally, we would announce today that our Fedora 26 TemplateVMs will reach EOL in one month in order to give users plenty of time to upgrade or migrate to a new template (just as we do when Qubes versions reach EOL). However, since we do not have a new template to offer yet, I'm going to postpone that announcement until the information is actionable. We will also make an announcement on 2018-06-01 stating that Fedora 26 has reached EOL, as a final reminder to anyone who hasn't migrated yet that they should do so immediately.

Discussion thread: https://groups.google.com/d/topic/qubes-users/s0qQLzQ1aBw/discussion

As discussed, Fedora 28 builds and works fine in Q4.0 (last PR for appmenus remains). Maybe a doc for upgrading from 26 -> 28 is worth it to be done?

fepitre · May 2, 2018

As discussed, Fedora 28 builds and works fine in Q4.0 (last PR for appmenus remains). Maybe a doc for upgrading from 26 -> 28 is worth it to be done?

Fedora 28 GA happened on 2018-05-01 (without any slip).

kushaldas · May 2, 2018

Fedora 28 GA happened on 2018-05-01 (without any slip).

Once it's up and running on 4.0, we'll need to backport relevant commits to r3.2 too, because we've promised support for at least a year.
In the meantime, all fc27 packages for R4.0 are already uploaded to current-testing repository. fc28 will be later this week. Full templates will be built after migrating those packages to current repository.
@andrewdavidwong can you take care about upgrade instruction? Should be pretty the same as previous versions.

marmarek · May 2, 2018

Once it's up and running on 4.0, we'll need to backport relevant commits to r3.2 too, because we've promised support for at least a year.
In the meantime, all fc27 packages for R4.0 are already uploaded to current-testing repository. fc28 will be later this week. Full templates will be built after migrating those packages to current repository.
@andrewdavidwong can you take care about upgrade instruction? Should be pretty the same as previous versions.

Looks like in-place upgrade 26->27 removes rpmfusion-{free,nonfree}-release packages, if rpmfusion repositories aren't enabled. This is logical, because with those repositories disabled, dnf don't know from where to download fc27 version of them. But it means repository definition will no longer be there, so it wouldn't be possible to enable it with a single step. One will need to download the package manually, verify it and install.
To avoid this, one could temporarily enable rpmfusion repositories for the upgrade time. But this isn't perfect, as one may not wish to use rpmfusion even temporarily in this particular template (but for example only in its clone). The packages we put during template build we manually verify that indeed contains only repository definition, its key and nothing more.
Alternative is to ignore this problem - if one use in-place upgrade for a template where rpmfusion isn't enabled, chances are he/she don't want to have it there. If one use rpmfusion in some templates, he/she can in-place upgrade those templates separately.
@andrewdavidwong any opinion?

marmarek · May 3, 2018

Looks like in-place upgrade 26->27 removes rpmfusion-{free,nonfree}-release packages, if rpmfusion repositories aren't enabled. This is logical, because with those repositories disabled, dnf don't know from where to download fc27 version of them. But it means repository definition will no longer be there, so it wouldn't be possible to enable it with a single step. One will need to download the package manually, verify it and install.
To avoid this, one could temporarily enable rpmfusion repositories for the upgrade time. But this isn't perfect, as one may not wish to use rpmfusion even temporarily in this particular template (but for example only in its clone). The packages we put during template build we manually verify that indeed contains only repository definition, its key and nothing more.
Alternative is to ignore this problem - if one use in-place upgrade for a template where rpmfusion isn't enabled, chances are he/she don't want to have it there. If one use rpmfusion in some templates, he/she can in-place upgrade those templates separately.
@andrewdavidwong any opinion?

Looks like in-place upgrade 26->27 removes rpmfusion-{free,nonfree}-release packages, if rpmfusion repositories aren't enabled. This is logical, because with those repositories disabled, dnf don't know from where to download fc27 version of them. But it means repository definition will no longer be there, so it wouldn't be possible to enable it with a single step. One will need to download the package manually, verify it and install.
To avoid this, one could temporarily enable rpmfusion repositories for the upgrade time. But this isn't perfect, as one may not wish to use rpmfusion even temporarily in this particular template (but for example only in its clone). The packages we put during template build we manually verify that indeed contains only repository definition, its key and nothing more.
Alternative is to ignore this problem - if one use in-place upgrade for a template where rpmfusion isn't enabled, chances are he/she don't want to have it there. If one use rpmfusion in some templates, he/she can in-place upgrade those templates separately.
@andrewdavidwong any opinion?

I think we should just explain this in the upgrade instructions and let the user decide. I'll add it.

andrewdavidwong · May 4, 2018

Looks like in-place upgrade 26->27 removes rpmfusion-{free,nonfree}-release packages, if rpmfusion repositories aren't enabled. This is logical, because with those repositories disabled, dnf don't know from where to download fc27 version of them. But it means repository definition will no longer be there, so it wouldn't be possible to enable it with a single step. One will need to download the package manually, verify it and install.
To avoid this, one could temporarily enable rpmfusion repositories for the upgrade time. But this isn't perfect, as one may not wish to use rpmfusion even temporarily in this particular template (but for example only in its clone). The packages we put during template build we manually verify that indeed contains only repository definition, its key and nothing more.
Alternative is to ignore this problem - if one use in-place upgrade for a template where rpmfusion isn't enabled, chances are he/she don't want to have it there. If one use rpmfusion in some templates, he/she can in-place upgrade those templates separately.
@andrewdavidwong any opinion?

I think we should just explain this in the upgrade instructions and let the user decide. I'll add it.

Automatic tests results for Fedora 27 template - almost ok, the only thing failing is IPv6 forwarding. And few things that looks rather like buggy tests than buggy template.

======================================================================
FAIL: qubes.tests.integ.network/VmIPv6Networking_fedora-27-test/test_510_ipv6_simple_proxyvm
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/qubes/tests/integ/network.py", line 707, in test_510_ipv6_simple_proxyvm
    "Ping by IP from AppVM failed")
AssertionError: 1 != 0 : Ping by IP from AppVM failed

======================================================================
FAIL: qubes.tests.integ.network/VmIPv6Networking_fedora-27-test/test_520_ipv6_simple_proxyvm_nm
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/qubes/tests/__init__.py", line 218, in wrapper
    func(self, *args, **kwargs)
  File "/usr/lib/python3.5/site-packages/qubes/tests/integ/network.py", line 729, in test_520_ipv6_simple_proxyvm_nm
    "Ping by IP failed")
AssertionError: 1 != 0 : Ping by IP failed

======================================================================
FAIL: qubes.tests.integ.network/VmIPv6Networking_fedora-27-test/test_530_ipv6_firewallvm_firewall
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/qubes/tests/integ/network.py", line 810, in test_530_ipv6_firewallvm_firewall
    "Ping by IP failed (should be allowed now)")
AssertionError: 1 != 0 : Ping by IP failed (should be allowed now)

======================================================================
FAIL: qubes.tests.integ.network/VmIPv6Networking_fedora-27-test/test_711_ipv6_custom_ip_proxy
  Custom ProxyVM IP
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/qubes/tests/integ/network.py", line 972, in test_711_ipv6_custom_ip_proxy
    self.assertEqual(self.run_cmd(self.testvm1, self.ping6_ip), 0)
AssertionError: 1 != 0

======================================================================
FAIL: qubes.tests.integ.network/VmIPv6Networking_fedora-27-test/test_712_ipv6_custom_ip_firewall
  Custom VM IP and firewall
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/qubes/tests/integ/network.py", line 1011, in test_712_ipv6_custom_ip_firewall
    "Ping by IP should be allowed")
AssertionError: 1 != 0 : Ping by IP should be allowed

marmarek · May 4, 2018

Automatic tests results for Fedora 27 template - almost ok, the only thing failing is IPv6 forwarding. And few things that looks rather like buggy tests than buggy template.

======================================================================
FAIL: qubes.tests.integ.network/VmIPv6Networking_fedora-27-test/test_510_ipv6_simple_proxyvm
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/qubes/tests/integ/network.py", line 707, in test_510_ipv6_simple_proxyvm
    "Ping by IP from AppVM failed")
AssertionError: 1 != 0 : Ping by IP from AppVM failed

======================================================================
FAIL: qubes.tests.integ.network/VmIPv6Networking_fedora-27-test/test_520_ipv6_simple_proxyvm_nm
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/qubes/tests/__init__.py", line 218, in wrapper
    func(self, *args, **kwargs)
  File "/usr/lib/python3.5/site-packages/qubes/tests/integ/network.py", line 729, in test_520_ipv6_simple_proxyvm_nm
    "Ping by IP failed")
AssertionError: 1 != 0 : Ping by IP failed

======================================================================
FAIL: qubes.tests.integ.network/VmIPv6Networking_fedora-27-test/test_530_ipv6_firewallvm_firewall
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/qubes/tests/integ/network.py", line 810, in test_530_ipv6_firewallvm_firewall
    "Ping by IP failed (should be allowed now)")
AssertionError: 1 != 0 : Ping by IP failed (should be allowed now)

======================================================================
FAIL: qubes.tests.integ.network/VmIPv6Networking_fedora-27-test/test_711_ipv6_custom_ip_proxy
  Custom ProxyVM IP
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/qubes/tests/integ/network.py", line 972, in test_711_ipv6_custom_ip_proxy
    self.assertEqual(self.run_cmd(self.testvm1, self.ping6_ip), 0)
AssertionError: 1 != 0

======================================================================
FAIL: qubes.tests.integ.network/VmIPv6Networking_fedora-27-test/test_712_ipv6_custom_ip_firewall
  Custom VM IP and firewall
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/qubes/tests/integ/network.py", line 1011, in test_712_ipv6_custom_ip_firewall
    "Ping by IP should be allowed")
AssertionError: 1 != 0 : Ping by IP should be allowed

The upgrade instructions are now live:

https://www.qubes-os.org/doc/template/fedora/upgrade-26-to-27/

Please feel free to submit PRs with any corrections or improvements.

andrewdavidwong · May 5, 2018

The upgrade instructions are now live:

https://www.qubes-os.org/doc/template/fedora/upgrade-26-to-27/

Please feel free to submit PRs with any corrections or improvements.

Uploaded to current-testing for R3.2 too. Thanks @fepitre !

marmarek · May 7, 2018

Uploaded to current-testing for R3.2 too. Thanks @fepitre !

My fedora-26 to 27 upgrade failed (fedora-27 refuses to run any app 'cannot create qrexec agent for 60 seconds') but I can't delete fedora-27 or fedora-27-dvm

qvm-remove error: Domain is in use 'fedora-27'; details in system log

But qvm-kill shows both are shutdown.

End of guest-fedora-27.log below. Any help appreciated.

Fedora 27 (Twenty Seven)
Kernel 4.14.18-1.pvops.qubes.x86_64 on an x86_64 (hvc0)

localhost login: [   22.011555] kauditd_printk_skb: 6 callbacks suppressed
[   22.011556] audit: type=1131 audit(1526113941.315:33): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   42.136388] audit: type=1131 audit(1526113961.440:34): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   58.115876] audit: type=1130 audit(1526113977.419:35): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   58.123238] audit: type=1130 audit(1526113977.427:36): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

JPL1 · May 12, 2018

My fedora-26 to 27 upgrade failed (fedora-27 refuses to run any app 'cannot create qrexec agent for 60 seconds') but I can't delete fedora-27 or fedora-27-dvm

qvm-remove error: Domain is in use 'fedora-27'; details in system log

But qvm-kill shows both are shutdown.

End of guest-fedora-27.log below. Any help appreciated.

Fedora 27 (Twenty Seven)
Kernel 4.14.18-1.pvops.qubes.x86_64 on an x86_64 (hvc0)

localhost login: [   22.011555] kauditd_printk_skb: 6 callbacks suppressed
[   22.011556] audit: type=1131 audit(1526113941.315:33): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   42.136388] audit: type=1131 audit(1526113961.440:34): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   58.115876] audit: type=1130 audit(1526113977.419:35): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   58.123238] audit: type=1130 audit(1526113977.427:36): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

On Sat, May 12, 2018 at 01:39:09AM -0700, JPL1 wrote: My fedora-26 to 27 upgrade failed (fedora-27 refuses to run any app 'cannot create qrexec agent for 60 seconds')

Do you have log (console output) from the upgrade? I guess some important packages were removed in the process (qubes-core-agent or so). Have you enabled current-testing repository?

`qvm-remove error: Domain is in use 'fedora-27'; details in system log `

This means some other domain use it (for example for its template). See `journalctl -e` in dom0 for full message.

marmarek · May 12, 2018

On Sat, May 12, 2018 at 01:39:09AM -0700, JPL1 wrote: My fedora-26 to 27 upgrade failed (fedora-27 refuses to run any app 'cannot create qrexec agent for 60 seconds')

Do you have log (console output) from the upgrade? I guess some important packages were removed in the process (qubes-core-agent or so). Have you enabled current-testing repository?

`qvm-remove error: Domain is in use 'fedora-27'; details in system log `

This means some other domain use it (for example for its template). See `journalctl -e` in dom0 for full message.

Have you enabled current-testing repository

Ah, I think that was my mistake. Thank you. Once I've deleted the template I'll try again.

Here is the output from journalctl -e
jctl.txt

JPL1 · May 12, 2018

Have you enabled current-testing repository

Ah, I think that was my mistake. Thank you. Once I've deleted the template I'll try again.

Here is the output from journalctl -e
jctl.txt

Not to worry I've sorted it. fedora-27-dvm was set as default dvm. Fixed that and I can delete the template now.

JPL1 · May 12, 2018

Not to worry I've sorted it. fedora-27-dvm was set as default dvm. Fixed that and I can delete the template now.

My fedora-26 to 27 upgrade failed (fedora-27 refuses to run any app 'cannot create qrexec agent for 60 seconds')

I'm still having this problem. Made sure the repo was enabled:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Then followed the instructions here:

https://www.qubes-os.org/doc/template/fedora/upgrade-26-to-27/

Where should I look next? Unfortunately I don't have the output from the Fedora-27 vm and cannot get to a console now.

JPL1 · May 12, 2018

My fedora-26 to 27 upgrade failed (fedora-27 refuses to run any app 'cannot create qrexec agent for 60 seconds')

I'm still having this problem. Made sure the repo was enabled:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Then followed the instructions here:

https://www.qubes-os.org/doc/template/fedora/upgrade-26-to-27/

Where should I look next? Unfortunately I don't have the output from the Fedora-27 vm and cannot get to a console now.

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Not dom0. As instruction says, --enablerepo=qubes-vm*current-testing, and that's for dnf in the template (for all dnf calls).

marmarek · May 12, 2018

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Not dom0. As instruction says, --enablerepo=qubes-vm*current-testing, and that's for dnf in the template (for all dnf calls).

Ah OK. It would be helpful if that were made clear in the intro for thickos like me.
[fedora-27] $ sudo dnf update --enablerepo=qubes-vm*current-testing

I'm still having problems though, even after doing that.

On the command:

[user@fedora-27 ~]$ sudo dnf --releasever=27 distro-sync --best --allowerasing

everything appears to be going fine until the end when I get:

  Verifying        : zlib-devel-1.2.11-2.fc26.x86_64                  2820/2821 
  Verifying        : zvbi-0.2.35-2.fc26.x86_64                        2821/2821 
Traceback (most recent call last):
  File "/bin/dnf", line 58, in <module>
    main.user_main(sys.argv[1:], exit_code=True)
  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 179, in user_main
    errcode = main(args)
  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 64, in main
    return _main(base, args, cli_class, option_parser_class)
  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 99, in _main
    return cli_run(cli, base)
  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 123, in cli_run
    ret = resolving(cli, base)
  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 154, in resolving
    base.do_transaction(display=displays)
  File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 238, in do_transaction
    super(BaseCli, self).do_transaction(display)
  File "/usr/lib/python3.6/site-packages/dnf/base.py", line 784, in do_transaction
    self._plugins.run_transaction()
  File "/usr/lib/python3.6/site-packages/dnf/plugin.py", line 96, in fn
    dnf.util.mapall(operator.methodcaller(method), self.plugins)
  File "/usr/lib/python3.6/site-packages/dnf/util.py", line 223, in mapall
    return list(map(fn, *seq))
  File "/usr/lib/python3.6/site-packages/dnf-plugins/qubes-hooks.py", line 45, in transaction
    if config.getboolean('main', 'notify-updates'):
  File "/usr/lib/python3.6/site-packages/iniparse/compat.py", line 146, in getboolean
    v = self.get(section, option)
  File "/usr/lib/python3.6/site-packages/iniparse/compat.py", line 219, in get
    raise NoSectionError(section)
configparser.NoSectionError: No section: 'main'

Then on restart:

qvm-run fedora-27 gnome-terminal

gives

Cannot connect to qrexec agent for 60 seconds....

I have also tried the virtual disk method and get the same thing.

'cannot create qrexec agent for 60 seconds`

guid.fedora-27.log:

Icon size: 128x128
libvchan_is_eof
Icon size: 128x128
domain dead
Failed to connect to gui-agent

qrexec log is empty

guest-fedora-27.log (Qube Manager)

Dom0 Houston we have a problem
Unsupported operation, can't do non-zero end-relative seeks at line 1159
of file user/lib/python3.5/site-packages/qubesmanager/qube_manager.py

Is it some clash between Python versions?

JPL1 · May 12, 2018

Ah OK. It would be helpful if that were made clear in the intro for thickos like me.
[fedora-27] $ sudo dnf update --enablerepo=qubes-vm*current-testing

I'm still having problems though, even after doing that.

On the command:

[user@fedora-27 ~]$ sudo dnf --releasever=27 distro-sync --best --allowerasing

everything appears to be going fine until the end when I get:

  Verifying        : zlib-devel-1.2.11-2.fc26.x86_64                  2820/2821 
  Verifying        : zvbi-0.2.35-2.fc26.x86_64                        2821/2821 
Traceback (most recent call last):
  File "/bin/dnf", line 58, in <module>
    main.user_main(sys.argv[1:], exit_code=True)
  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 179, in user_main
    errcode = main(args)
  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 64, in main
    return _main(base, args, cli_class, option_parser_class)
  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 99, in _main
    return cli_run(cli, base)
  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 123, in cli_run
    ret = resolving(cli, base)
  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 154, in resolving
    base.do_transaction(display=displays)
  File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 238, in do_transaction
    super(BaseCli, self).do_transaction(display)
  File "/usr/lib/python3.6/site-packages/dnf/base.py", line 784, in do_transaction
    self._plugins.run_transaction()
  File "/usr/lib/python3.6/site-packages/dnf/plugin.py", line 96, in fn
    dnf.util.mapall(operator.methodcaller(method), self.plugins)
  File "/usr/lib/python3.6/site-packages/dnf/util.py", line 223, in mapall
    return list(map(fn, *seq))
  File "/usr/lib/python3.6/site-packages/dnf-plugins/qubes-hooks.py", line 45, in transaction
    if config.getboolean('main', 'notify-updates'):
  File "/usr/lib/python3.6/site-packages/iniparse/compat.py", line 146, in getboolean
    v = self.get(section, option)
  File "/usr/lib/python3.6/site-packages/iniparse/compat.py", line 219, in get
    raise NoSectionError(section)
configparser.NoSectionError: No section: 'main'

Then on restart:

qvm-run fedora-27 gnome-terminal

gives

Cannot connect to qrexec agent for 60 seconds....

I have also tried the virtual disk method and get the same thing.

'cannot create qrexec agent for 60 seconds`

guid.fedora-27.log:

Icon size: 128x128
libvchan_is_eof
Icon size: 128x128
domain dead
Failed to connect to gui-agent

qrexec log is empty

guest-fedora-27.log (Qube Manager)

Dom0 Houston we have a problem
Unsupported operation, can't do non-zero end-relative seeks at line 1159
of file user/lib/python3.5/site-packages/qubesmanager/qube_manager.py

Is it some clash between Python versions?

Is there a way to download the fedora-27 or fedora-28 template from scratch yet? I'm trying
[dom0] $ sudo qubes-dom0-update qubes-template-fedora-27 --enablerepo=qubes-dom0-current-testing

But am getting

Error: Unable to find a match

JPL1 · May 13, 2018

Is there a way to download the fedora-27 or fedora-28 template from scratch yet? I'm trying
[dom0] $ sudo qubes-dom0-update qubes-template-fedora-27 --enablerepo=qubes-dom0-current-testing

But am getting

Error: Unable to find a match

On the command:

[user@fedora-27 ~]$ sudo dnf --releasever=27 distro-sync --best --allowerasing

--enablerepo=qubes-vm*current-testing needs to be used whenever you want dnf to use that repository, this includes the distro-sync:

sudo dnf --releasever=27 distro-sync --best --allowerasing --enablerepo=qubes-vm*current-testing

As mentioned by @marmarek, you want to include --enablerepo=qubes-vm*current-testing for all calls to dnf.

pgerber · May 13, 2018

On the command:

[user@fedora-27 ~]$ sudo dnf --releasever=27 distro-sync --best --allowerasing

--enablerepo=qubes-vm*current-testing needs to be used whenever you want dnf to use that repository, this includes the distro-sync:

sudo dnf --releasever=27 distro-sync --best --allowerasing --enablerepo=qubes-vm*current-testing

As mentioned by @marmarek, you want to include --enablerepo=qubes-vm*current-testing for all calls to dnf.

@pgerber yes that worked. Thank you.

JPL1 · May 13, 2018

@pgerber yes that worked. Thank you.

In the docs, the workaround for python2-xcffib upgrade error doesn't work.

Step 1 ("-x") is fine.
Step 2 python2-xcffib using sudo dnf swap python-xcffib python2-xcffib -> Gives dependency hell errors and doesn't upgrade.

Trying to download the Fedora (27/28) template holus bolus as a work-around also doesn't work ("no match found") e.g.

sudo qubes-dom0-update qubes-template-fedora-28 -> no match
sudo qubes-dom0-update qubes-template-fedora-28 --enablerepo=qubes-vm*current-testing -> no match

Above command with unstable, testing or security-testing repos -> no match.

So what is the precise command to download the full template from testing repos, since it is supposedly there?

torjunkie · May 20, 2018

In the docs, the workaround for python2-xcffib upgrade error doesn't work.

Step 1 ("-x") is fine.
Step 2 python2-xcffib using sudo dnf swap python-xcffib python2-xcffib -> Gives dependency hell errors and doesn't upgrade.

Trying to download the Fedora (27/28) template holus bolus as a work-around also doesn't work ("no match found") e.g.

sudo qubes-dom0-update qubes-template-fedora-28 -> no match
sudo qubes-dom0-update qubes-template-fedora-28 --enablerepo=qubes-vm*current-testing -> no match

Above command with unstable, testing or security-testing repos -> no match.

So what is the precise command to download the full template from testing repos, since it is supposedly there?

On Sat, May 19, 2018 at 05:07:54PM -0700, torjunkie wrote: In the docs, the workaround for python2-xcffib upgrade error doesn't work. Step 1 ("-x") is fine. Step 2 python2-xcffib using sudo dnf swap python-xcffib python2-xcffib -> Gives dependency hell errors and doesn't upgrade.

This workaround is needed only if you upgrade to Fedora 28.

So what is the precise command to download the full template from testing repos, since it is supposedly there?

It isn't there, yet.

marmarek · May 20, 2018

On Sat, May 19, 2018 at 05:07:54PM -0700, torjunkie wrote: In the docs, the workaround for python2-xcffib upgrade error doesn't work. Step 1 ("-x") is fine. Step 2 python2-xcffib using sudo dnf swap python-xcffib python2-xcffib -> Gives dependency hell errors and doesn't upgrade.

This workaround is needed only if you upgrade to Fedora 28.

So what is the precise command to download the full template from testing repos, since it is supposedly there?

It isn't there, yet.

@marmarek Any update on the status of this? How long do you estimate until f27 and (preferably) f28 move out of current-testing?

esote · May 23, 2018

@marmarek Any update on the status of this? How long do you estimate until f27 and (preferably) f28 move out of current-testing?

Sorry for lack of update here. It's already done. And also binary template package is available.
@andrewdavidwong I think it's time for the announcement about it. Fedora 28 is available too.

marmarek · May 24, 2018

Sorry for lack of update here. It's already done. And also binary template package is available.
@andrewdavidwong I think it's time for the announcement about it. Fedora 28 is available too.

Sorry for lack of update here. It's already done. And also binary template package is available.
@andrewdavidwong I think it's time for the announcement about it. Fedora 28 is available too.

Done: https://www.qubes-os.org/news/2018/05/23/fedora-26-and-debian-8-approaching-eol/

andrewdavidwong · May 24, 2018

Sorry for lack of update here. It's already done. And also binary template package is available.
@andrewdavidwong I think it's time for the announcement about it. Fedora 28 is available too.

Done: https://www.qubes-os.org/news/2018/05/23/fedora-26-and-debian-8-approaching-eol/

Closing as done.

andrewdavidwong · May 24, 2018

Closing as done.

marmarek added the task label Apr 3, 2018

andrewdavidwong added the C: Fedora label Apr 4, 2018

andrewdavidwong added this to the Release 4.1 milestone Apr 4, 2018

marmarek referenced this issue Apr 5, 2018
Closed
Fedora 28 template #3791
4 of 4 tasks complete

andrewdavidwong added the P: critical label May 2, 2018

andrewdavidwong referenced this issue in QubesOS/qubes-doc May 3, 2018
Merged
Create Fedora 26 to 27 upgrade guide #642

andrewdavidwong closed this May 24, 2018

QubesOS/qubes-issues

Join GitHub today

Fedora 27 template #3783

Comments

marmarek commented Apr 3, 2018 • edited by andrewdavidwong Edited 4 times andrewdavidwong edited May 24, 2018 (most recent) andrewdavidwong edited May 24, 2018 andrewdavidwong edited May 24, 2018 andrewdavidwong edited May 24, 2018

marmarek added the task label Apr 3, 2018

andrewdavidwong added the C: Fedora label Apr 4, 2018

andrewdavidwong added this to the Release 4.1 milestone Apr 4, 2018

marmarek referenced this issue Apr 5, 2018

This comment has been minimized.

esote commented Apr 6, 2018 • edited Edited 3 times esote edited Apr 6, 2018 (most recent) esote edited Apr 6, 2018 esote edited Apr 6, 2018

This comment has been minimized.

andrewdavidwong commented Apr 6, 2018

This comment has been minimized.

kushaldas commented Apr 11, 2018

This comment has been minimized.

andrewdavidwong commented May 2, 2018

andrewdavidwong added the P: critical label May 2, 2018

This comment has been minimized.

andrewdavidwong commented May 2, 2018

This comment has been minimized.

fepitre commented May 2, 2018

This comment has been minimized.

kushaldas commented May 2, 2018

This comment has been minimized.

marmarek commented May 2, 2018

andrewdavidwong added a commit to QubesOS/qubes-doc that referenced this issue May 3, 2018

andrewdavidwong referenced this issue in QubesOS/qubes-doc May 3, 2018

This comment has been minimized.

marmarek commented May 3, 2018

This comment has been minimized.

andrewdavidwong commented May 4, 2018

This comment has been minimized.

marmarek commented May 4, 2018

andrewdavidwong added a commit to QubesOS/qubes-doc that referenced this issue May 4, 2018

andrewdavidwong added a commit to QubesOS/qubes-doc that referenced this issue May 4, 2018

andrewdavidwong added a commit to QubesOS/qubes-doc that referenced this issue May 4, 2018

andrewdavidwong added a commit to QubesOS/qubes-doc that referenced this issue May 4, 2018

andrewdavidwong added a commit to QubesOS/qubes-doc that referenced this issue May 5, 2018

This comment has been minimized.

andrewdavidwong commented May 5, 2018

This comment has been minimized.

marmarek commented May 7, 2018

andrewdavidwong added a commit to QubesOS/qubes-doc that referenced this issue May 8, 2018

This comment has been minimized.

JPL1 commented May 12, 2018

This comment has been minimized.

marmarek commented May 12, 2018

This comment has been minimized.

JPL1 commented May 12, 2018

This comment has been minimized.

JPL1 commented May 12, 2018

This comment has been minimized.

JPL1 commented May 12, 2018 • edited Edited 2 times JPL1 edited May 12, 2018 (most recent) JPL1 edited May 12, 2018

This comment has been minimized.

marmarek commented May 12, 2018 • edited Edited 1 time marmarek edited May 12, 2018 (most recent)

This comment has been minimized.

JPL1 commented May 12, 2018

This comment has been minimized.

JPL1 commented May 13, 2018

This comment has been minimized.

pgerber commented May 13, 2018 • edited Edited 1 time pgerber edited May 13, 2018 (most recent)

This comment has been minimized.

JPL1 commented May 13, 2018

This comment has been minimized.

torjunkie commented May 20, 2018

This comment has been minimized.

marmarek commented May 20, 2018

This comment has been minimized.

esote commented May 23, 2018

This comment has been minimized.

marmarek commented May 24, 2018

andrewdavidwong added a commit to QubesOS/qubes-doc that referenced this issue May 24, 2018

andrewdavidwong added a commit to QubesOS/qubes-doc that referenced this issue May 24, 2018

andrewdavidwong added a commit to QubesOS/qubes-posts that referenced this issue May 24, 2018

This comment has been minimized.

andrewdavidwong commented May 24, 2018

andrewdavidwong added a commit to QubesOS/qubes-doc that referenced this issue May 24, 2018

This comment has been minimized.

andrewdavidwong commented May 24, 2018

marmarek commented Apr 3, 2018 •

edited by andrewdavidwong

Edited 4 times

andrewdavidwong edited May 24, 2018 (most recent)

andrewdavidwong edited May 24, 2018

andrewdavidwong edited May 24, 2018

andrewdavidwong edited May 24, 2018

esote commented Apr 6, 2018 •

edited

Edited 3 times

esote edited Apr 6, 2018 (most recent)

esote edited Apr 6, 2018

esote edited Apr 6, 2018

JPL1 commented May 12, 2018 •

edited

Edited 2 times

JPL1 edited May 12, 2018 (most recent)

JPL1 edited May 12, 2018

marmarek commented May 12, 2018 •

edited

Edited 1 time

marmarek edited May 12, 2018 (most recent)

pgerber commented May 13, 2018 •

edited

Edited 1 time

pgerber edited May 13, 2018 (most recent)