v1.9.0-beta2 known issues #13

olljanat · 2020-11-21T08:17:46Z

I noticed couple new issues on v1.9.0-beta2 which need to be fixed on release candidate.

I will add those as one issue per comment and other can do same.

olljanat · 2020-11-21T08:21:14Z

Way how I tried optimize Debian console disk usage by removing extra locales on https://github.com/burmilla/os-services/blob/f8f361e8d7fbef94c971dd707f0e2a96ac0bdc88/images/10-debianconsole/Dockerfile#L12-L14 is no very smart and it generates new error messages like this:

rancher@burmilla:~$ locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=en_US.UTF-8

Most probably logic must be that we keep all locales which exist on debian:stable-slim and include en_US.UTF-8 from locales package (or just forgot that optimization).

EDIT: Looks that this is not necessarily new issue but instead of existing one on Rancher OS as it gives similar errors after switching to Debian console and login with SSH to it:

Linux rancher.kotiverkko.local 4.14.138-rancher #1 SMP Sat Aug 10 11:25:46 UTC 2019 x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Nov 21 08:37:04 2020 from 192.168.100.236
-bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
-bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)

olljanat · 2020-11-21T08:25:35Z

Default console still exists even when I tried to make Debian as only console. Most probably I need move files from https://github.com/burmilla/os-services/tree/f8f361e8d7fbef94c971dd707f0e2a96ac0bdc88/images/10-debianconsole to https://github.com/burmilla/os/tree/v1.9.x/images/02-console

Good think on that would be that is simplify also build process as currently I need build console with same version tag first that OS build can include it to ISO file.

olljanat · 2020-11-21T08:28:24Z

ros command currently only list Rancher Labs as only author. "Project Burmilla" should be there too like we have now on readme files.

[rancher@burmilla ~]$ sudo ros
NAME:
   ros - Control and configure BurmillaOS
built: '2020-11-17T21:19:11Z'

USAGE:
   ros [global options] command [command options] [arguments...]
   
VERSION:
   v1.9.0-beta2
   
AUTHOR(S):
   Rancher Labs, Inc.

olljanat · 2020-11-21T08:34:49Z

Not actually new issue but visible because Debian is default console now.

RancherOS default console print line which starts with text "docker-sys" and contains eth0 IP address which is very useful when deploying servers with DHCP and you want to know which IP they got.

olljanat · 2020-11-21T08:47:18Z

Currently user must switch to Debian console before upgrading from RancherOS (like I updated to guidance). Other why it generates a lot of errors.

olljanat · 2020-11-21T09:09:33Z

VMware tools does not work

olljanat · 2020-11-21T09:32:46Z

First boot from ISO and from disk on Proxmox VE gets stuck to this view for one minute:

It does not happen on RancherOS 1.5.6.

Second boot from disk works fine on BurmillaOS too.

tomaswarynyca · 2020-11-21T12:08:10Z

It is not possible to use the iso burmillaos-v1.9.0-beta2 with a docker-machine

docker-machine create -d virtualbox --virtualbox-boot2docker-url https://bit.ly/3lSbRPu burmilla

Running pre-create checks...
Creating machine...
(burmilla) Downloading from https://bit.ly/3lSbRPu...
(burmilla) 0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100%
(burmilla) Creating VirtualBox VM...
(burmilla) Creating SSH key...
(burmilla) Starting the VM...
(burmilla) Check network to re-create if needed...
(burmilla) Waiting for an IP...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Error creating machine: Error detecting OS: OS type not recognized

When I turn off the machine, turn it back on and list the available machines I realize that I get the following error

docker-machine start burmilla
Starting "burmilla"...
(burmilla) Check network to re-create if needed...
(burmilla) Waiting for an IP...
Machine "burmilla" was started.
Waiting for SSH to be available...
Detecting the provisioner...
OS type not recognized

docker-machine ls
 ERRORS Unable to query docker version: Cannot connect to the docker engine endpoint

olljanat · 2020-11-21T13:27:28Z

It is not possible to use the iso burmillaos-v1.9.0-beta2 with a docker-machine

Yes, with quick look of their code. docker-machine reads file /etc/os-release which is generated on:

os/scripts/layout-initrd

Lines 36 to 47 in 5a13f03

    
           cat <<HERE > ${INITRD_DIR}/usr/share/ros/os-release 
        
           NAME="BurmillaOS" 
        
           VERSION=${VERSION} 
        
           ID=burmillaos 
        
           ID_LIKE= 
        
           VERSION_ID=${VERSION} 
        
           PRETTY_NAME="BurmillaOS ${VERSION}" 
        
           HOME_URL="https://burmilla.github.io" 
        
           SUPPORT_URL="https://github.com/burmilla/os/issues" 
        
           BUG_REPORT_URL="https://github.com/burmilla/os/issues" 
        
           BUILD_ID= 
        
           HERE

we must restore ID value to rancheros

tomaswarynyca · 2020-11-21T14:39:19Z

If you run the command with the -D argument you will be able to see what happens when the virtual machine is created. We can see that the error is in BUILD_ID

docker-machine -D create -d virtualbox --virtualbox-boot2docker-url https://bit.ly/3lSbRPu burmilla

cat /etc/os-release
SSH cmd err, output: <nil>: NAME="BurmillaOS"
VERSION=v1.9.0-beta2
ID=burmillaos
ID_LIKE=
VERSION_ID=v1.9.0-beta2
PRETTY_NAME="BurmillaOS v1.9.0-beta2"
HOME_URL="https://burmilla.github.io"
SUPPORT_URL="https://github.com/burmilla/os/issues"
BUG_REPORT_URL="https://github.com/burmilla/os/issues"
BUILD_ID=

Couldn't set key BUILD_ID, no corresponding struct field found
Error creating machine: Error detecting OS: OS type not recognized
notifying bugsnag: [Error creating machine: Error detecting OS: OS type not recognized]

olljanat · 2020-11-23T07:40:05Z

@tomaswarynyca BUILD_ID is empty on RancherOS too so I'm quite sure that ID is key thing here. Anyway, can you try with rc1 draft version before I make it public? You should see it when you are logged in.

tomaswarynyca · 2020-11-23T14:17:49Z

@olljanat You are right I was testing the version v1.9.0-rc1 and it works perfectly in docker-machine.

The only thing you can see is that our BurmillaOS \v \n \l at startup. Is it correct that I show that?

olljanat · 2020-11-23T14:42:37Z

@tomaswarynyca hmm. true. RancherOS replace those with some system infos. Need to investigate how we get those in-place.

Anyway, other bugs looks to be fixed so I made rc1 public now.

olljanat · 2020-11-23T18:42:50Z

Let's try finalize v1.9.0 so I will close this one now and separate issue from each problem which still exist/can be found from rc1.

olljanat added the bug Something isn't working label Nov 21, 2020

olljanat added this to the v1.9.0-rc1 milestone Nov 21, 2020

olljanat self-assigned this Nov 21, 2020

olljanat mentioned this issue Nov 21, 2020

Changing default console to Debian and include most common tools to it #9

Closed

olljanat mentioned this issue Nov 22, 2020

How/where you use Rancher OS? Please share your configuration? #6

Closed

olljanat added the version/v1.9.x label Nov 23, 2020

olljanat closed this as completed Nov 23, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

v1.9.0-beta2 known issues #13

v1.9.0-beta2 known issues #13

olljanat commented Nov 21, 2020

olljanat commented Nov 21, 2020 •

edited

Loading

olljanat commented Nov 21, 2020

olljanat commented Nov 21, 2020

olljanat commented Nov 21, 2020

olljanat commented Nov 21, 2020

olljanat commented Nov 21, 2020

olljanat commented Nov 21, 2020 •

edited

Loading

tomaswarynyca commented Nov 21, 2020

olljanat commented Nov 21, 2020

tomaswarynyca commented Nov 21, 2020

olljanat commented Nov 23, 2020

tomaswarynyca commented Nov 23, 2020 •

edited

Loading

olljanat commented Nov 23, 2020

olljanat commented Nov 23, 2020

v1.9.0-beta2 known issues #13

v1.9.0-beta2 known issues #13

Comments

olljanat commented Nov 21, 2020

olljanat commented Nov 21, 2020 • edited Loading

olljanat commented Nov 21, 2020

olljanat commented Nov 21, 2020

olljanat commented Nov 21, 2020

olljanat commented Nov 21, 2020

olljanat commented Nov 21, 2020

olljanat commented Nov 21, 2020 • edited Loading

tomaswarynyca commented Nov 21, 2020

olljanat commented Nov 21, 2020

tomaswarynyca commented Nov 21, 2020

olljanat commented Nov 23, 2020

tomaswarynyca commented Nov 23, 2020 • edited Loading

olljanat commented Nov 23, 2020

olljanat commented Nov 23, 2020

olljanat commented Nov 21, 2020 •

edited

Loading

olljanat commented Nov 21, 2020 •

edited

Loading

tomaswarynyca commented Nov 23, 2020 •

edited

Loading