Unable to Access Root User on Worker VM

Available Languages

Download Options

  • PDF     (44.1 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (107.7 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (163.2 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:September 19, 2017
Document ID:212099

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

    Introduction

    This document describes how to use sudo on a worker Virtual Machine (VM).

      

    The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

      

    Problem

    After the launch of a worker VM and access of the console, when you try to become the root user by the execution of the sudo command, you are presented with the message as shown in the image:

    Solution

    As a security mechanism, by default, the cliqruser does not have sudo permissions. You can grant access with the modification of the application profile.

    Documentation page: http://docs.cloudcenter.cisco.com/display/CCD48/Service+Properties

    On the Topology modeler, under Node Initialization & Clean Up is a box that says Sudo Command List. Enter ALL in the box, as shown in the image.

    Alternately, you can specify which specific commands the user can have access to, separate the commands with a semicolon.

    You have to deploy a new application for the new settings to take effect.

    TAC Authored

    Contributed by Cisco Engineers

    • Jesse Lafuenti
      Cisco TAC Engineer

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco

    This Document Applies to These Products