aws marketplace AS appliance sudo apt upgrade challenges

Post Reply
bthurber
OpenVpn Newbie
Posts: 5
Joined: Thu May 25, 2017 12:21 pm

aws marketplace AS appliance sudo apt upgrade challenges

Post by bthurber » Thu Jun 01, 2017 2:20 pm

As suggested in the OpenVPN Access Server Appliance AMI quick start guide, I am running 'sudo apt-get update && sudo apt-get upgrade' after install. On the upgrade step I encounter the following questions and I am not sure what the proper answers should be. I'm assuming 'N' for both but wanted to make sure:

Code: Select all

Configuration file '/etc/issue'.............................................................................................................................]
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** issue (Y/I/N/O/D/Z) [default=N] ?
Selecting D shows:

Code: Select all

--- /etc/issue  2016-10-20 17:34:00.238800666 +0000        
+++ /etc/issue.dpkg-new 2017-02-07 23:55:57.000000000 +0000
@@ -1 +1,2 @@                                              
-OpenVPN Access Server Appliance 2.1.4b \n \l              
+Ubuntu 16.04.2 LTS \n \l                                  
+                                                          
Should we select the default of 'N' for /etc/issue?

Same issue for /etc/cloud/cloud.cfg. Selecting 'D' shows:

Code: Select all

--- /etc/cloud/cloud.cfg        2016-10-20 17:31:25.251390547 +0000
+++ /etc/cloud/cloud.cfg.dpkg-new       2017-04-24 15:54:14.000000000 +0000
@@ -12,7 +12,7 @@
 disable_root: true

 # This will cause the set+update hostname module to not operate (if true)
-preserve_hostname: true
+preserve_hostname: false

 # Example datasource config
 # datasource:
@@ -30,6 +30,8 @@
  - write-files
  - growpart
  - resizefs
+ - disk_setup
+ - mounts
  - set_hostname
  - update_hostname
  - update_etc_hosts
@@ -43,8 +45,7 @@
 # Emit the cloud config ready event
 # this can be used by upstart jobs for 'start on cloud-config'.
  - emit_upstart
- - disk_setup
- - mounts
+ - snap_config
  - ssh-import-id
  - locale
  - set-passwords
@@ -87,7 +88,7 @@
    distro: ubuntu
    # Default user name + that default users groups (if added/used)
    default_user:
-     name: openvpnas
+     name: ubuntu
      lock_passwd: True
      gecos: Ubuntu
      groups: [adm, audio, cdrom, dialout, dip, floppy, lxd, netdev, plugdev, sudo, video]
Should we answer 'N' for /etc/cloud/cloud.cfg?

On a separate note. In the spirit of this being an "appliance" would it be possible for the patching of the AWS OS and OpenVPN to be made simpler?

Post Reply