container console Status: Closed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zun UI |
New
|
Undecided
|
Unassigned |
Bug Description
I work on rocky release when I acces to the console of container on dashboard, its status is closed as shown on screenshot attached
fatis (mohamed-el-amine) wrote : | #1 |
description: | updated |
hongbin (hongbin034) wrote : | #2 |
fatis (mohamed-el-amine) wrote : | #3 |
# cat /etc/zun/zun.conf
[DEFAULT]
#
# From oslo.log
#
transport_url = rabbit:
# If set to true, the logging level will be set to DEBUG instead of the default
# INFO level. (boolean value)
# Note: This option can be changed without restarting.
#debug = false
# The name of a logging configuration file. This file is appended to any
# existing logging configuration files. For details about logging configuration
# files, see the Python logging module documentation. Note that when logging
# configuration files are used then all logging configuration is set in the
# configuration file and other logging configuration options are ignored (for
# example, logging_
# Note: This option can be changed without restarting.
# Deprecated group/name - [DEFAULT]
#log_config_append = <None>
# Defines the format string for %%(asctime)s in log records. Default:
# %(default)s . This option is ignored if log_config_append is set. (string
# value)
#log_date_format = %Y-%m-%d %H:%M:%S
# (Optional) Name of log file to send logging output to. If no default is set,
# logging will go to stderr as defined by use_stderr. This option is ignored if
# log_config_append is set. (string value)
# Deprecated group/name - [DEFAULT]/logfile
#log_file = <None>
# (Optional) The base directory used for relative log_file paths. This option
# is ignored if log_config_append is set. (string value)
# Deprecated group/name - [DEFAULT]/logdir
#log_dir = <None>
# Uses logging handler designed to watch file system. When log file is moved or
# removed this handler will open a new log file with specified path
# instantaneously. It makes sense only if log_file option is specified and
# Linux platform is used. This option is ignored if log_config_append is set.
# (boolean value)
#watch_log_file = false
# Use syslog for logging. Existing syslog format is DEPRECATED and will be
# changed later to honor RFC5424. This option is ignored if log_config_append
# is set. (boolean value)
#use_syslog = false
# Enable journald for logging. If running in a systemd environment you may wish
# to enable journal support. Doing so will use the journal native protocol
# which includes structured metadata in addition to log messages.This option is
# ignored if log_config_append is set. (boolean value)
#use_journal = false
# Syslog facility to receive log lines. This option is ignored if
# log_config_append is set. (string value)
#syslog_
# Use JSON formatting for logging. This option is ignored if log_config_append
# is set. (boolean value)
#use_json = false
# Log output to standard error. This option is ignored if log_config_append is
# set. (boolean value)
#use_stderr = false
# Format string to use for log messages with context. (string value)
#logging_
# Format string to use for log messages when context is undefined. (string
# value)
#logging_
hongbin (hongbin034) wrote : | #4 |
Yes, it looks your `base_url` is not set. As a result, the default url would be:
ws://
which is:
ws://
Depending on the location of your browser, it might not be able to access 192.168.0.1:6784 . You would need to configure `base_url` and using an external accessible IP address (instead of 192.168.0.1).
fatis (mohamed-el-amine) wrote : | #5 |
it set on the compute node zun.conf
base_url = ws://controller
# cat /etc/zun/zun.conf
[DEFAULT]
#
# From oslo.log
#
transport_url = rabbit:
state_path = /var/lib/zun
# If set to true, the logging level will be set to DEBUG instead of the default
# INFO level. (boolean value)
# Note: This option can be changed without restarting.
#debug = false
# The name of a logging configuration file. This file is appended to any
# existing logging configuration files. For details about logging configuration
# files, see the Python logging module documentation. Note that when logging
# configuration files are used then all logging configuration is set in the
# configuration file and other logging configuration options are ignored (for
# example, logging_
# Note: This option can be changed without restarting.
# Deprecated group/name - [DEFAULT]
#log_config_append = <None>
# Defines the format string for %%(asctime)s in log records. Default:
# %(default)s . This option is ignored if log_config_append is set. (string
# value)
#log_date_format = %Y-%m-%d %H:%M:%S
# (Optional) Name of log file to send logging output to. If no default is set,
# logging will go to stderr as defined by use_stderr. This option is ignored if
# log_config_append is set. (string value)
# Deprecated group/name - [DEFAULT]/logfile
#log_file = <None>
# (Optional) The base directory used for relative log_file paths. This option
# is ignored if log_config_append is set. (string value)
# Deprecated group/name - [DEFAULT]/logdir
#log_dir = <None>
# Uses logging handler designed to watch file system. When log file is moved or
# removed this handler will open a new log file with specified path
# instantaneously. It makes sense only if log_file option is specified and
# Linux platform is used. This option is ignored if log_config_append is set.
# (boolean value)
#watch_log_file = false
# Use syslog for logging. Existing syslog format is DEPRECATED and will be
# changed later to honor RFC5424. This option is ignored if log_config_append
# is set. (boolean value)
#use_syslog = false
# Enable journald for logging. If running in a systemd environment you may wish
# to enable journal support. Doing so will use the journal native protocol
# which includes structured metadata in addition to log messages.This option is
# ignored if log_config_append is set. (boolean value)
#use_journal = false
# Syslog facility to receive log lines. This option is ignored if
# log_config_append is set. (string value)
#syslog_
# Use JSON formatting for logging. This option is ignored if log_config_append
# is set. (boolean value)
#use_json = false
# Log output to standard error. This option is ignored if log_config_append is
# set. (boolean value)
#use_stderr = false
# Format string to use for log messages with context. (string value)
#logging_
# Format string to use for log messages when context is undefined. (string
# value)
#logging_
hongbin (hongbin034) wrote : Re: [Bug 1831164] Re: container console Status: Closed | #6 |
On Sat, Jun 1, 2019 at 6:45 PM fatis <email address hidden> wrote:
> it set on the compute node zun.conf
>
I think it should be set in the controller node. Could you give it a try?
>
> base_url = ws://controller
>
> # cat /etc/zun/zun.conf
> [DEFAULT]
>
> #
> # From oslo.log
> #
> transport_url = rabbit:
> state_path = /var/lib/zun
> # If set to true, the logging level will be set to DEBUG instead of the
> default
> # INFO level. (boolean value)
> # Note: This option can be changed without restarting.
> #debug = false
>
> # The name of a logging configuration file. This file is appended to any
> # existing logging configuration files. For details about logging
> configuration
> # files, see the Python logging module documentation. Note that when
> logging
> # configuration files are used then all logging configuration is set in the
> # configuration file and other logging configuration options are ignored
> (for
> # example, logging_
> # Note: This option can be changed without restarting.
> # Deprecated group/name - [DEFAULT]
> #log_config_append = <None>
>
> # Defines the format string for %%(asctime)s in log records. Default:
> # %(default)s . This option is ignored if log_config_append is set. (string
> # value)
> #log_date_format = %Y-%m-%d %H:%M:%S
>
> # (Optional) Name of log file to send logging output to. If no default is
> set,
> # logging will go to stderr as defined by use_stderr. This option is
> ignored if
> # log_config_append is set. (string value)
> # Deprecated group/name - [DEFAULT]/logfile
> #log_file = <None>
>
> # (Optional) The base directory used for relative log_file paths. This
> option
> # is ignored if log_config_append is set. (string value)
> # Deprecated group/name - [DEFAULT]/logdir
> #log_dir = <None>
>
> # Uses logging handler designed to watch file system. When log file is
> moved or
> # removed this handler will open a new log file with specified path
> # instantaneously. It makes sense only if log_file option is specified and
> # Linux platform is used. This option is ignored if log_config_append is
> set.
> # (boolean value)
> #watch_log_file = false
>
> # Use syslog for logging. Existing syslog format is DEPRECATED and will be
> # changed later to honor RFC5424. This option is ignored if
> log_config_append
> # is set. (boolean value)
> #use_syslog = false
>
> # Enable journald for logging. If running in a systemd environment you may
> wish
> # to enable journal support. Doing so will use the journal native protocol
> # which includes structured metadata in addition to log messages.This
> option is
> # ignored if log_config_append is set. (boolean value)
> #use_journal = false
>
> # Syslog facility to receive log lines. This option is ignored if
> # log_config_append is set. (string value)
> #syslog_
>
> # Use JSON formatting for logging. This option is ignored if
> log_config_append
> # is set. (boolean value)
> #use_json = false
>
> # Log output to standard error. This option is ignored if
> log_config_append is
> # set. (boolean value)
> #use_stderr = false
>
> # Format s...
fatis (mohamed-el-amine) wrote : | #7 |
I try but still not résolve
openstack --debug appcontainer exec --interactive container2 /bin/sh
WARNING: Failed to import plugin clustering.
START with options: --debug appcontainer exec --interactive container2 /bin/sh
options: Namespace(
Auth plugin password selected
auth_config_hook(): {'auth_type': 'password', 'beta_command': False, u'image_
samos667 (samos667) wrote : | #8 |
I have exactly the same error, command "openstack appcontainer exec --interactive" works correctly, and "base_url =" is configured on my controller node.
My conf is attached if you want to see it (websocket_proxy section is at the bottom of the file).
I am available for any other information.
hongbin (hongbin034) wrote : | #9 |
@samos667,
A few questions:
* Does this command work for you: "openstack appcontainer run --interactive ubuntu /bin/bash". If not, please paste me the debug output: "openstack --debug appcontainer run --interactive ubuntu /bin/bash"
* Your zun-wsproxy log (journalctl -u zun-wsproxy > zun-wsproxy.log)
samos667 (samos667) wrote : | #10 |
- appcontainer.output Edit (9.2 KiB, text/plain)
The output of "openstack appcontainer run --interactive ubuntu /bin/bash" (I don't have the time to press enter)
samos667 (samos667) wrote : | #11 |
- appcontainer--debug.output Edit (41.8 KiB, text/plain)
The output of "openstack --debug appcontainer run --interactive ubuntu /bin/bash"
samos667 (samos667) wrote : | #12 |
samos667 (samos667) wrote : | #13 |
But when i do "openstack appcontainer exec --interactive delta-14-container /bin/bash" he work.
Bash output:
root@sam:~# openstack appcontainer exec --interactive delta-14-container /bin/bash
connected to delta-14-container, press Enter to continue
type ~. to disconnect
root@4c808c7c78
hongbin (hongbin034) wrote : | #14 |
@samos667,
It seems you were hitting this bug: https:/
Several things to check:
* If you are able to access the console on CLI: zun run --interactive <image> /bin/sh /docs.openstack .org/zun/ latest/ install/ controller- install. html and the following note:
* Your configuration 'base_url' in controller node. See here: https:/
.. note::
This ``base_url`` will be used by end users to access the console of
their containers so make sure this URL is accessible from your
intended users and the port ``6784`` is not blocked by firewall.
If it doesn't help, please paste me your Zun configuration file (/etc/zun.conf) in the *controller* node (with sensitive information removed, such as password).