logname: no login name while configuring Glance in microstack

Bug #1868993 reported by redgreenblue
260
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MicroStack
Confirmed
Medium
Unassigned

Bug Description

Hello everyone,

I am using Ubuntu 16.04. I have already installed Microstack.
When I want to initialize it, I receive the following error:

ubuntu@redgreenblue:~$ sudo microstack.init --auto
.
.
.
2020-03-25 13:02:25,695 - microstack_init - INFO - Configuring Glance ...
Waiting for 10.40.40.119:9292
logname: no login name
Traceback (most recent call last):
  File "/snap/microstack/196/bin/microstack_init", line 11, in <module>
    load_entry_point('microstack-init==0.0.1', 'console_scripts', 'microstack_init')()
  File "/snap/microstack/196/lib/python3.6/site-packages/init/main.py", line 122, in main
    question.ask()
  File "/snap/microstack/196/lib/python3.6/site-packages/init/questions/question.py", line 210, in ask
    self.yes(awr)
  File "/snap/microstack/196/lib/python3.6/site-packages/init/questions/__init__.py", line 682, in yes
    user = check_output('logname')
  File "/snap/microstack/196/lib/python3.6/site-packages/init/shell.py", line 81, in check_output
    universal_newlines=True).strip()
  File "/snap/microstack/196/usr/lib/python3.6/subprocess.py", line 356, in check_output
    **kwargs).stdout
  File "/snap/microstack/196/usr/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '('logname',)' returned non-zero exit status 1.

information type: Private Security → Public Security
description: updated
Revision history for this message
Pen Gale (pengale) wrote :

The call that's failing has been factored out in the latest --edge version of the snap. I'm tempted to mark as "fix released", though it might make sense to backport a fix to the classic version of the snap, given that it's taking a while to get to a stable point with the strictly confined snap.

@redgreenblue: is it possible for you to deploy on bionic? Or does it make sense for your workflow to got with the edge snap? (You'll need to install it with both the --edge and --devmode flags, as strict confinement is still a work in progress.)

Changed in microstack:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
redgreenblue (redgreenblue) wrote :

I remove it and install it with --edge and --devmode. Everything works fine now and I even uploaded a new ubuntu image to microstack for future instances.

Thanks.

Revision history for this message
Sabbir Ahmed (sabbir-unioulu) wrote :

Hi, I faced the same issue and then resolved with the same method. But, when tried to create the ubuntu bionic image on openstack(microstack) webGUI, I am facing the undertneath error:

<html> <head><title>413 Request Entity Too Large</title></head> <body bgcolor="white"> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.13.0</center> </body> </html>

Could you please help me on that? Thanks

Rolf Leggewie (r0lf)
summary: - logname: no login name while Configuring Glance in Micrstack
+ logname: no login name while configuring Glance in microstack
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.