[Touch-packages] [Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation

2019-03-28 Thread Frank Heimes
** Changed in: systemd (Ubuntu)
   Status: New => Invalid

** No longer affects: systemd (Ubuntu)

** Changed in: ubuntu-z-systems
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1821867

Title:
  network interface is down after post-install reboot of a default disco
  installation

Status in Ubuntu on IBM z Systems:
  In Progress
Status in netplan.io package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Minimal installs using netplan to configure the network.

  [Test case]
  1) Install Ubuntu minimal server / cloud image
  2) Edit /etc/netplan/01-netcfg.yaml to configure the network as necessary.
  3) Run 'sudo netplan apply'. Verify that the network comes up correctly.
  4) Reboot.
  5) Verify that the network comes up properly.

  [Regression potential]
  Minimal; this reverts changes in a package that was never released to 
-updates, only available as SRU in -proposed and on the devel release. This 
only applies to the order in which systemd-networkd is enabled when used as a 
renderer for netplan configuration, to start in multi-user.target instead of 
the "correct", but inefficient "network-online.target" as the latter may not be 
depended upon in minimal installs.

  ---

  After doing a default disco installation on s390x using the beta ISO image 
aka daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
  Hence no remote connections are possible.

  The ip cmd shows:
  ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: enc600:  mtu 1500 qdisc noop state DOWN group default 
ql
  en 1000
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff

  The netplan yaml file looks fine:
  cat /etc/netplan/*.yaml
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
    version: 2
    renderer: networkd
    ethernets:
  enc600:
    addresses: ¬ 10.245.236.27/24 |
    gateway4: 10.245.236.1
    nameservers:
    search: ¬ canonical.com |
    addresses:
    - "10.245.236.1"

  Using ip to bring the interface up doesn't help:
  buntu§hwe0007:ß$ sudo ip link set enc600 up
  sudo ip link set enc600 up
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::28:bff:fe00:15/64 scope link
     valid_lft forever preferred_lft forever
  ubuntu§hwe0007:ß$

  But finally executing netplan apply does help:
  sudo netplan apply --dryrun
  sudo netplan apply --dryrun
  ubuntu§hwe0007:ß$ sudo netplan apply
  sudo netplan apply
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff
  inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600
     valid_lft forever preferred_lft forever
  inet6 fe80::28:bff:fe00:15/64 scope link
     valid_lft forever preferred_lft forever
  ubuntu§hwe0007:ß$

  (Sorry for the partly duplicate lines and some strange characters, but
  this is due to the fact that I copied the output from the console that
  requires a 3270 terminal emulation)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821867/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation

2019-03-28 Thread Mathieu Trudel-Lapierre
** Description changed:

+ [Impact]
+ Minimal installs using netplan to configure the network.
+ 
+ [Test case]
+ 1) Install Ubuntu minimal server / cloud image
+ 2) Edit /etc/netplan/01-netcfg.yaml to configure the network as necessary.
+ 3) Run 'sudo netplan apply'. Verify that the network comes up correctly.
+ 4) Reboot.
+ 5) Verify that the network comes up properly.
+ 
+ [Regression potential]
+ Minimal; this reverts changes in a package that was never released to 
-updates, only available as SRU in -proposed and on the devel release. This 
only applies to the order in which systemd-networkd is enabled when used as a 
renderer for netplan configuration, to start in multi-user.target instead of 
the "correct", but inefficient "network-online.target" as the latter may not be 
depended upon in minimal installs.
+ 
+ ---
+ 
  After doing a default disco installation on s390x using the beta ISO image 
aka daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
  Hence no remote connections are possible.
  
  The ip cmd shows:
- ip a  
+ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
- t qlen 1000  
- link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
- inet 127.0.0.1/8 scope host lo  
-valid_lft forever preferred_lft forever  
- inet6 ::1/128 scope host   
-valid_lft forever preferred_lft forever  
+ t qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+    valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host
+    valid_lft forever preferred_lft forever
  2: enc600:  mtu 1500 qdisc noop state DOWN group default 
ql
- en 1000  
- link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
+ en 1000
+ link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff
  
  The netplan yaml file looks fine:
- cat /etc/netplan/*.yaml  
+ cat /etc/netplan/*.yaml
  # This file describes the network interfaces available on your system
- # For more information, see netplan(5).  
- network:  
-   version: 2  
-   renderer: networkd  
-   ethernets:  
- enc600:  
-   addresses: ¬ 10.245.236.27/24 |  
-   gateway4: 10.245.236.1  
-   nameservers:  
-   search: ¬ canonical.com |  
-   addresses:  
-   - "10.245.236.1"  
+ # For more information, see netplan(5).
+ network:
+   version: 2
+   renderer: networkd
+   ethernets:
+ enc600:
+   addresses: ¬ 10.245.236.27/24 |
+   gateway4: 10.245.236.1
+   nameservers:
+   search: ¬ canonical.com |
+   addresses:
+   - "10.245.236.1"
  
  Using ip to bring the interface up doesn't help:
  buntu§hwe0007:ß$ sudo ip link set enc600 up
  sudo ip link set enc600 up
  ubuntu§hwe0007:ß$ ip addr show enc600
- ip addr show enc600  
+ ip addr show enc600
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
- oup default qlen 1000  
- link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
- inet6 fe80::28:bff:fe00:15/64 scope link   
-valid_lft forever preferred_lft forever  
+ oup default qlen 1000
+ link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff
+ inet6 fe80::28:bff:fe00:15/64 scope link
+    valid_lft forever preferred_lft forever
  ubuntu§hwe0007:ß$
  
  But finally executing netplan apply does help:
  sudo netplan apply --dryrun
- sudo netplan apply --dryrun  
+ sudo netplan apply --dryrun
  ubuntu§hwe0007:ß$ sudo netplan apply
- sudo netplan apply  
+ sudo netplan apply
  ubuntu§hwe0007:ß$ ip addr show enc600
- ip addr show enc600  
+ ip addr show enc600
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
- oup default qlen 1000  
- link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
- inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600  
-valid_lft forever preferred_lft forever  
- inet6 fe80::28:bff:fe00:15/64 scope link   
-valid_lft forever preferred_lft forever  
- ubuntu§hwe0007:ß$ 
+ oup default qlen 1000
+ link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff
+ inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600
+    valid_lft forever preferred_lft forever
+ inet6 fe80::28:bff:fe00:15/64 scope link
+    valid_lft forever preferred_lft forever
+ ubuntu§hwe0007:ß$
  
  (Sorry for the partly duplicate lines and some strange characters, but
  this is due to the fact that I copied the output from the console that
  requires a 3270 terminal emulation)

** Changed in: netplan.io (Ubuntu)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1821867

Title:
  network interface is down after post-install reboot of a default disco
  installation

Status in Ubuntu on IBM z Systems:
  Triaged
Status in netplan.io package in Ubuntu:
  In Progress
Status i

[Touch-packages] [Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation

2019-03-28 Thread Frank Heimes
Just as a side note - this also happens (like expected) with LPAR
installations.

I already did some earlier disco daily installations and cannot remember
that I ran into this issue before which wonders me a bit ...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1821867

Title:
  network interface is down after post-install reboot of a default disco
  installation

Status in Ubuntu on IBM z Systems:
  Triaged
Status in netplan.io package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  After doing a default disco installation on s390x using the beta ISO image 
aka daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
  Hence no remote connections are possible.

  The ip cmd shows:
  ip a  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000  
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
  inet 127.0.0.1/8 scope host lo  
 valid_lft forever preferred_lft forever  
  inet6 ::1/128 scope host   
 valid_lft forever preferred_lft forever  
  2: enc600:  mtu 1500 qdisc noop state DOWN group default 
ql
  en 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  

  The netplan yaml file looks fine:
  cat /etc/netplan/*.yaml  
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).  
  network:  
version: 2  
renderer: networkd  
ethernets:  
  enc600:  
addresses: ¬ 10.245.236.27/24 |  
gateway4: 10.245.236.1  
nameservers:  
search: ¬ canonical.com |  
addresses:  
- "10.245.236.1"  

  Using ip to bring the interface up doesn't help:
  buntu§hwe0007:ß$ sudo ip link set enc600 up
  sudo ip link set enc600 up
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$

  But finally executing netplan apply does help:
  sudo netplan apply --dryrun
  sudo netplan apply --dryrun  
  ubuntu§hwe0007:ß$ sudo netplan apply
  sudo netplan apply  
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600  
 valid_lft forever preferred_lft forever  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$ 

  (Sorry for the partly duplicate lines and some strange characters, but
  this is due to the fact that I copied the output from the console that
  requires a 3270 terminal emulation)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821867/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation

2019-03-28 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1821867

Title:
  network interface is down after post-install reboot of a default disco
  installation

Status in Ubuntu on IBM z Systems:
  Triaged
Status in netplan.io package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  After doing a default disco installation on s390x using the beta ISO image 
aka daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
  Hence no remote connections are possible.

  The ip cmd shows:
  ip a  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000  
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
  inet 127.0.0.1/8 scope host lo  
 valid_lft forever preferred_lft forever  
  inet6 ::1/128 scope host   
 valid_lft forever preferred_lft forever  
  2: enc600:  mtu 1500 qdisc noop state DOWN group default 
ql
  en 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  

  The netplan yaml file looks fine:
  cat /etc/netplan/*.yaml  
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).  
  network:  
version: 2  
renderer: networkd  
ethernets:  
  enc600:  
addresses: ¬ 10.245.236.27/24 |  
gateway4: 10.245.236.1  
nameservers:  
search: ¬ canonical.com |  
addresses:  
- "10.245.236.1"  

  Using ip to bring the interface up doesn't help:
  buntu§hwe0007:ß$ sudo ip link set enc600 up
  sudo ip link set enc600 up
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$

  But finally executing netplan apply does help:
  sudo netplan apply --dryrun
  sudo netplan apply --dryrun  
  ubuntu§hwe0007:ß$ sudo netplan apply
  sudo netplan apply  
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600  
 valid_lft forever preferred_lft forever  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$ 

  (Sorry for the partly duplicate lines and some strange characters, but
  this is due to the fact that I copied the output from the console that
  requires a 3270 terminal emulation)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821867/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation

2019-03-28 Thread Mathieu Trudel-Lapierre
This seems quite likely to be an issue with netplan; I've had a similar
report on UC18; where systemd-networkd isn't started.

Turns out netplan moved the enablement of systemd-netwrokd to network-
online.target; but unfortunately there may be no service or target
depending on that. I'll revert the change to put systemd-networkd back
under multi-user.target.

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: netplan.io (Ubuntu)
   Status: New => Triaged

** Changed in: netplan.io (Ubuntu)
   Importance: Undecided => Critical

** Changed in: netplan.io (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1821867

Title:
  network interface is down after post-install reboot of a default disco
  installation

Status in Ubuntu on IBM z Systems:
  New
Status in netplan.io package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  After doing a default disco installation on s390x using the beta ISO image 
aka daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
  Hence no remote connections are possible.

  The ip cmd shows:
  ip a  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000  
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
  inet 127.0.0.1/8 scope host lo  
 valid_lft forever preferred_lft forever  
  inet6 ::1/128 scope host   
 valid_lft forever preferred_lft forever  
  2: enc600:  mtu 1500 qdisc noop state DOWN group default 
ql
  en 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  

  The netplan yaml file looks fine:
  cat /etc/netplan/*.yaml  
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).  
  network:  
version: 2  
renderer: networkd  
ethernets:  
  enc600:  
addresses: ¬ 10.245.236.27/24 |  
gateway4: 10.245.236.1  
nameservers:  
search: ¬ canonical.com |  
addresses:  
- "10.245.236.1"  

  Using ip to bring the interface up doesn't help:
  buntu§hwe0007:ß$ sudo ip link set enc600 up
  sudo ip link set enc600 up
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$

  But finally executing netplan apply does help:
  sudo netplan apply --dryrun
  sudo netplan apply --dryrun  
  ubuntu§hwe0007:ß$ sudo netplan apply
  sudo netplan apply  
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600  
 valid_lft forever preferred_lft forever  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$ 

  (Sorry for the partly duplicate lines and some strange characters, but
  this is due to the fact that I copied the output from the console that
  requires a 3270 terminal emulation)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821867/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation

2019-03-27 Thread Frank Heimes
** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Importance: Undecided => Critical

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1821867

Title:
  network interface is down after post-install reboot of a default disco
  installation

Status in Ubuntu on IBM z Systems:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  After doing a default disco installation on s390x using the beta ISO image 
aka daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
  Hence no remote connections are possible.

  The ip cmd shows:
  ip a  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000  
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
  inet 127.0.0.1/8 scope host lo  
 valid_lft forever preferred_lft forever  
  inet6 ::1/128 scope host   
 valid_lft forever preferred_lft forever  
  2: enc600:  mtu 1500 qdisc noop state DOWN group default 
ql
  en 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  

  The netplan yaml file looks fine:
  cat /etc/netplan/*.yaml  
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).  
  network:  
version: 2  
renderer: networkd  
ethernets:  
  enc600:  
addresses: ¬ 10.245.236.27/24 |  
gateway4: 10.245.236.1  
nameservers:  
search: ¬ canonical.com |  
addresses:  
- "10.245.236.1"  

  Using ip to bring the interface up doesn't help:
  buntu§hwe0007:ß$ sudo ip link set enc600 up
  sudo ip link set enc600 up
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$

  But finally executing netplan apply does help:
  sudo netplan apply --dryrun
  sudo netplan apply --dryrun  
  ubuntu§hwe0007:ß$ sudo netplan apply
  sudo netplan apply  
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600  
 valid_lft forever preferred_lft forever  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$ 

  (Sorry for the partly duplicate lines and some strange characters, but
  this is due to the fact that I copied the output from the console that
  requires a 3270 terminal emulation)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821867/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation

2019-03-27 Thread Frank Heimes
** Attachment added: "journalctl -b"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821867/+attachment/5249682/+files/journalctl-b.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1821867

Title:
  network interface is down after post-install reboot of a default disco
  installation

Status in systemd package in Ubuntu:
  New

Bug description:
  After doing a default disco installation on s390x using the beta ISO image 
aka daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
  Hence no remote connections are possible.

  The ip cmd shows:
  ip a  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000  
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
  inet 127.0.0.1/8 scope host lo  
 valid_lft forever preferred_lft forever  
  inet6 ::1/128 scope host   
 valid_lft forever preferred_lft forever  
  2: enc600:  mtu 1500 qdisc noop state DOWN group default 
ql
  en 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  

  The netplan yaml file looks fine:
  cat /etc/netplan/*.yaml  
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).  
  network:  
version: 2  
renderer: networkd  
ethernets:  
  enc600:  
addresses: ¬ 10.245.236.27/24 |  
gateway4: 10.245.236.1  
nameservers:  
search: ¬ canonical.com |  
addresses:  
- "10.245.236.1"  

  Using ip to bring the interface up doesn't help:
  buntu§hwe0007:ß$ sudo ip link set enc600 up
  sudo ip link set enc600 up
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$

  But finally executing netplan apply does help:
  sudo netplan apply --dryrun
  sudo netplan apply --dryrun  
  ubuntu§hwe0007:ß$ sudo netplan apply
  sudo netplan apply  
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600  
 valid_lft forever preferred_lft forever  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$ 

  (Sorry for the partly duplicate lines and some strange characters, but
  this is due to the fact that I copied the output from the console that
  requires a 3270 terminal emulation)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821867/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation

2019-03-27 Thread Frank Heimes
systemd-networkd.service is not active after reboot:

systemctl status systemd-networkd.service  
 systemd-networkd.service - Network Service ¬m  
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled-runtime
 ¬m  
   Active: inactive (dead) ¬m  
 Docs: man:systemd-networkd.service(8) ¬m  
 ¬7mlines 1-4/4 (END) ¬27m ¬K

attaching journalctl as well ...


** Attachment added: "journalctl.txt"
   
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1821867/+attachment/5249681/+files/journalctl.txt

** Package changed: debian-installer (Ubuntu) => systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1821867

Title:
  network interface is down after post-install reboot of a default disco
  installation

Status in systemd package in Ubuntu:
  New

Bug description:
  After doing a default disco installation on s390x using the beta ISO image 
aka daily from March 26th and the post-install reboot the system restarts aka 
reipls (in z/VM in this case) but the interface is not brought up.
  Hence no remote connections are possible.

  The ip cmd shows:
  ip a  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000  
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
  inet 127.0.0.1/8 scope host lo  
 valid_lft forever preferred_lft forever  
  inet6 ::1/128 scope host   
 valid_lft forever preferred_lft forever  
  2: enc600:  mtu 1500 qdisc noop state DOWN group default 
ql
  en 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  

  The netplan yaml file looks fine:
  cat /etc/netplan/*.yaml  
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).  
  network:  
version: 2  
renderer: networkd  
ethernets:  
  enc600:  
addresses: ¬ 10.245.236.27/24 |  
gateway4: 10.245.236.1  
nameservers:  
search: ¬ canonical.com |  
addresses:  
- "10.245.236.1"  

  Using ip to bring the interface up doesn't help:
  buntu§hwe0007:ß$ sudo ip link set enc600 up
  sudo ip link set enc600 up
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$

  But finally executing netplan apply does help:
  sudo netplan apply --dryrun
  sudo netplan apply --dryrun  
  ubuntu§hwe0007:ß$ sudo netplan apply
  sudo netplan apply  
  ubuntu§hwe0007:ß$ ip addr show enc600
  ip addr show enc600  
  2: enc600:  mtu 1500 qdisc fq_codel state UP 
gr
  oup default qlen 1000  
  link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff  
  inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600  
 valid_lft forever preferred_lft forever  
  inet6 fe80::28:bff:fe00:15/64 scope link   
 valid_lft forever preferred_lft forever  
  ubuntu§hwe0007:ß$ 

  (Sorry for the partly duplicate lines and some strange characters, but
  this is due to the fact that I copied the output from the console that
  requires a 3270 terminal emulation)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821867/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp