Bug 1212530 - [director] No username/password for local console access on instack-deployed overcloud nodes.
Summary: [director] No username/password for local console access on instack-deployed ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: Director
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ga
: 7.0 (Kilo)
Assignee: Dan Macpherson
QA Contact: Radek Bíba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-16 15:02 UTC by Victor Lowther
Modified: 2016-01-25 07:07 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-25 07:07:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Victor Lowther 2015-04-16 15:02:22 UTC
On overcloud nodes deployed by instack, there are no credentials that you can use to log into the local console.  This makes troubleshooting failed nodes in the face of network connectivity failures (where you cannot SSH in to node as heat-admin) needlessly difficult to troubleshoot.  Having a user that can only log in to the local console and that can sudo to root would facilitate troubleshooting.

Comment 2 Salman Khan 2015-06-29 16:04:22 UTC
Any update on it, how we can access the console of overcloud nodes in order to debug things.

Comment 5 chris alfonso 2015-07-01 17:05:17 UTC
Mike, can you please post a lead to the docs for this?

Comment 6 Dan Macpherson 2015-08-04 06:20:07 UTC
The resulting content will be an article on modifying the image with virt-customize tools. mozari has provided me with the necessary info.

Comment 7 Dan Macpherson 2015-08-10 04:25:51 UTC
Article posted here:
https://access.redhat.com/articles/1556833

Victor and Salman,
Does this suit your needs? Any additional information required?

Comment 8 Mike Orazi 2015-09-14 12:54:08 UTC
The included info should cover everything, so removing the need_info.  If there is additional info that would be helpful please feel free to reach out and ask.

Comment 9 Andrew Dahms 2015-11-12 02:17:41 UTC
Assigning Radek as the QA contact.

Radek - could you take a look at the changes for this bug?

Comment 10 Radek Bíba 2015-11-12 09:10:33 UTC
A couple of things that are worth fixing:

"such installing additional components" -> "such as installing additional components"

"Install the libguestfs-tools from" -> "Install the libguestfs-tools package from"

"the contents of the overcloud-full.qcow2." -> "the contents of the overcloud-full.qcow2 image."

The boot options for virt-manager aren't rendered as a list; instead, (literal) * signs are displayed. AFAICT, you need an empty line above the list, too.

In "After installing the necessary packages to customize the image, we now remove our subscriptions", "we/our" is used although the rest of the document speaks directly to the reader. Please consider s/we now// ; s/our/your/.

Other than that, the article looks good to me!

Comment 11 Dan Macpherson 2016-01-25 07:00:34 UTC
Fixes from comment#10 implemented.

adahms, are we good to close this BZ?

Comment 12 Andrew Dahms 2016-01-25 07:07:05 UTC
Hi Dan,

Looks good to me - we should be alright to close this one now.

Thank you for implementing the feedback, and to Radek for the detailed comments!

Kind regards,

Andrew


Note You need to log in before you can comment on or make changes to this bug.